You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Refactor OSA framework documentation and remove mini-swe-agent integration
- Updated llms.txt with new security principles, agent specifications, and post-quantum cryptography details.
- Deleted mini-swe-agent README and configuration files as part of the integration removal.
- Enhanced security measures and coding standards across the framework.
- Added OWASP LLM and Agentic Top 10 lists for improved security awareness.
@@ -43,59 +43,43 @@ Your goal is not just to "do a task" but to **orchestrate** the best possible so
43
43
44
44
## Agent Hierarchy
45
45
46
-
When breaking out agent teams or parallel agents, follow this hierarchy for team member selection:
46
+
The agent hierarchy is designed for **rate limit and API key utilization optimization**. When multiple agents are available, this ordering maximizes the use of free tiers, optimal rate limits, and cost-effective API keys before falling back to paid or rate-limited alternatives.
Gemini is the **primary**agent in the OSA Framework for orchestration and planning tasks. Best usage/rate limits make it ideal for coordinating multi-agent workflows.
78
+
Gemini has the **highest priority** in the OSA Framework due to its generous free tier rate limits, making it the first choice for any task to maximize resource utilization.
78
79
79
-
### mini-swe-agent (Hierarchy 4)
80
+
### Qwen (Hierarchy 2)
80
81
81
-
mini-swe-agent is a specialized software engineering agent. Developed by the Princeton/Stanford team behind SWE-bench.
82
-
83
-
**Key Features:**
84
-
-**Minimal**: ~100 lines of Python for the agent class
85
-
-**Performant**: >74% on SWE-bench verified benchmark
86
-
-**Simple**: No tools other than bash
87
-
-**Transparent**: Completely linear history
88
-
-**Compatible**: Works with all models via litellm
Qwen is the second priority, offering a good balance of performance and free tier availability. It serves as the primary fallback when Gemini's limits are reached or if Gemini is unsuitable for a specific task.
99
83
100
84
### Core Rules
101
85
@@ -116,31 +100,26 @@ Adopt these personas as needed for each task:
| **Balanced** | Hierarchy-based selection (Gemini → Qwen → Claude → mini → OpenCode) |
329
+
The resource-aware selection system optimizes for **API key utilization and rate limit management** across multiple providers. The goal is to maximize the value of all available keys by using free tiers and generous rate limits first.
383
330
384
331
### Selection Logic
385
332
386
333
```
387
-
IF time_remaining < 30s → Select fastest agent by hierarchy
388
-
IF token_utilization > 80% → Select most efficient agent by hierarchy
389
-
IF token_utilization < 50% → Select highest quality agent by hierarchy
390
-
ELSE → Hierarchy-based default selection
334
+
IF rate_limit_hit(agent) → Fall back to next agent in hierarchy
335
+
IF free_quota_available → Prefer agents with free tier remaining
336
+
IF paid_keys_exhausted → Use agents with remaining quota
337
+
IF all_keys_exhausted → Wait and retry, or notify user
338
+
ELSE → Use highest-priority agent (best rate limits)
391
339
```
392
340
393
-
### Agent Performance Profiles
394
-
395
-
| Agent | Speed | Cost | Quality | Hierarchy |
396
-
|-------|-------|------|---------|-----------|
397
-
| **Gemini** | Fast | Free Tier | Very High | **1** |
0 commit comments