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/navox-labs/agentsWrote 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/commands/navox-labs/agents/agency-run)<a href="https://agentmods.dev/commands/navox-labs/agents/agency-run"><img src="https://agentmods.dev/badge/commands/navox-labs/agents/agency-run/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/commands/navox-labs/agents/agency-run"><img src="https://agentmods.dev/badge/commands/navox-labs/agents/agency-run.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.00055 | $0.03802 |
| Opus 5 | $0.00028 | $0.01901 |
| Sonnet 5 | $0.00011 | $0.00760 |
| Haiku 4.5 | $0.00006 | $0.00380 |
Grade B, and why
agency-run scanned grade B with 1 finding 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 11d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
cat .claude/project-memory.md 2>/dev/null || echo "No project memory yet" How it starts
The opening of the file, as written. The whole thing — 396 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the engineering team orchestrator for this project. Your job is to assemble the right agents from .claude/agents/ and run them in the correct handoff sequence to complete the task. You are guided by the three principles in ETHOS.md — read it first.
Your task
$ARGUMENTS
The Team
These are the people you're coordinating. Use their names, not their role titles.
| Name | Role | Agent ID |
|---|---|---|
| Raya Patel | Strategist | _strategist |
| Marcus Chen | Spec Writer | _spec-writer |
| Dmitri Volkov | Architect | _architect |
| Lena Ishida | UX Designer | _ux |
| Beatriz Oyelaran | Plan Critic | _critic |
| Jordan Rivera | Full Stack Engineer | _fullstack |
| Tomás Ferreira | Mobile Engineer | _mobile |
| Sam Okafor | Investigator | _investigator |
| Ava Lindström | Code Reviewer | _reviewer |
| Priya Sharma | QA Engineer | _qa |
| Kai Nakamura | Security Engineer | _security |
| Dr. Ines Haddad | Privacy Engineer | _privacy |
| Omar Hassan | DevOps Engineer | _devops |
| Elena Torres | Release Engineer | _shipper |
| James Wright | Retro Facilitator | _retro |
| Nina Kowalski | Context Manager | _context-manager |
Sprint Mode Selection
Before starting, determine the sprint mode. If the builder specifies a mode (e.g. /agency-run HOTFIX fix login bug, or
/agency-run mobile "M2: shift log"), use exactly that mode. The mode
argument is not a hint — a builder who names a mode has already decided. Never
silently fall back to a different mode; if the named mode is unknown, stop and
say so rather than improvising. Otherwise, select based on the task:
FULL Sprint
Use for: new features, major changes, anything that touches auth or data models.
THINK: Raya — DIAGNOSE (validate the idea)
PLAN: Marcus — WRITE (create spec) → Dmitri — DESIGN (system design)
parallel: Lena — DESIGN + Kai — DESIGN-REVIEW
BUILD: Jordan — BUILD → local-review — HUMAN CHECKPOINT
REVIEW: Ava — REVIEW (full review army)
TEST: parallel: Priya — TEST-RUN + Kai — CODE-AUDIT
SHIP: Elena — SHIP (tests → changelog → PR)
REFLECT: James — RETRO (capture learnings)
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.
- 11d ago First seen · 396 lines · 55 tokens per session scan B e5d65402dcb1
agency-run is a command published in the GitHub repository navox-labs/agents (14 stars, last pushed 12d ago), licensed MIT. It adds 55 tokens to every session and 3,802 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
cleanup
Sweep closed issues for stale labels, missing workflow state, and Project board gaps — plus prune worktrees, branches, and milestones.
milestone
Create, manage, and ship milestones — the top-level planning layer for feature development.
signal-planner
Closed-loop autonomy — convert a production/analytics/incident signal into a dependency-ordered issue DAG, execute via /orchestrate, then verify the originating signal is resolved. Event-driven companion to /autopilot.
adopt
Bootstrap an existing repo for ForgeDock — triage open issues, apply labels, suggest a starter milestone, and identify first /work-on candidates.
work-on-monolithic
Command "work-on-monolithic" from RapierCraftStudios/ForgeDock, covering /work-on-monolithic — full issue pipeline (single prompt), compaction resilience, pipeline rules, project configuration and phase 0: resolve issue & load context.
pipeline-status
Pipeline-wide situational awareness — groups open issues by workflow state, shows active PRs, flags stale items, and reports milestone progress.