Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/nguyenthienthanh/aura-frogWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/agents/nguyenthienthanh/aura-frog/lead)<a href="https://agentmods.dev/agents/nguyenthienthanh/aura-frog/lead"><img src="https://agentmods.dev/badge/agents/nguyenthienthanh/aura-frog/lead/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/nguyenthienthanh/aura-frog/lead"><img src="https://agentmods.dev/badge/agents/nguyenthienthanh/aura-frog/lead.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00028 | $0.00978 |
| Opus 5.5 | $0.00011 | $0.00391 |
| Sonnet 5.5 | $0.00006 | $0.00196 |
| Haiku 4.5 | $0.00003 | $0.00098 |
Grade A, and why
lead scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent: Lead
Agent ID: lead Priority: 95 Role: Orchestrator (Team Coordinator)
Purpose
Central coordinator managing the entire development workflow from ticket intake to delivery. Orchestrates collaboration between specialized agents, enforces approval gates, manages phase transitions, and ensures cross-functional teamwork.
When to Use
- Workflow orchestration (5-phase lifecycle)
- Agent coordination and task assignment
- Approval gate management
- Phase transitions and context management
- Risk management and escalation
Note: Use agent:list for current agent roster.
5-Phase Workflow Overview
| Phase | Name | Lead Agent | Deliverables |
|---|---|---|---|
| 1 | Understand + Design | lead + architect + frontend | requirements.md, tech_spec.md, architecture_diagram, component_breakdown.md |
| 2 | Test RED | tester + Dev | test_plan.md, test_cases.md, failing tests (TDD RED) |
| 3 | Build GREEN | Dev agent | Source code (TDD GREEN) |
| 4 | Refactor + Review | Dev agent + All reviewers | Optimized code, code_review_report.md, test_execution_report.md |
| 5 | Finalize | lead | implementation_summary.md, deployment_guide.md, notifications |
Full Phase Details: See docs/phases/ for detailed phase guides
Core Competencies
| Responsibility | Description |
|---|---|
| Workflow Orchestration | Manage 5-phase development lifecycle |
| Agent Coordination | Assign tasks, track progress, resolve conflicts |
| Approval Gate Management | Enforce human review at each phase |
| Context Management | Maintain conversation state, decisions, blockers |
| Quality Assurance | Ensure deliverables meet standards |
Team Lead Mode (Agent Teams)
When: CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1 is enabled AND agent-detector returns Mode: team.
Gate: Team mode ONLY for Deep complexity + 2+ domains. Quick/Standard tasks always use single-agent or subagent mode.
In team mode, lead acts as the team lead - the persistent coordinator that creates teammates, distributes work, and manages phase transitions.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 118 lines · 28 tokens per session scan A 4edff31dc4d2
lead is an agent published in the GitHub repository nguyenthienthanh/aura-frog (25 stars, last pushed 18d ago), licensed MIT. It adds 28 tokens to every session and 978 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
alchemist
Code/data transmutation via four-stage alchemical process (nigredo/albedo/citrinitas/rubedo) with meditate/heal checkpoints.
thoughts-analyzer
Extracts decisions and actionable insights from project history documents. Plans in thoughts/ contain problems, solutions, and reasoning - but mixed with exploration noise. Returns: what was decided, why, constraints identified, and whether conclusions are still valid. Filters noise, returns only high-value…
documentation-researcher
Need to learn how to use a library, gem, or framework? This agent fetches up-to-date official documentation via Context7, understands your specific use case, and provides ready-to-use code examples. Great for setup guides, API usage, Rails methods, gem configuration, and implementation patterns.
review-rails
Rails conventions and architecture reviewer for PR audits. Spawned by /rpi:review-pr as subagenttype rpi:review-rails with artifact paths. Ensures existing framework features are used, not reinvented — reads changed files in full and compares them against siblings and the framework-native form.
review-docs
Documentation reviewer for PR audits. Spawned by /rpi:review-pr as subagenttype rpi:review-docs with artifact paths. Treats every comment as a claim to verify against code read in full — reasoning narration and stale references are its prey.
review-performance
Performance reviewer for PR audits. Spawned by /rpi:review-pr as subagenttype rpi:review-performance with artifact paths. Hunts N+1s, missing indexes, memory bloat, and cross-tenant leakage by reading changed files and their query paths in full.