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.
npx agentmods add agents/cbrock84/headcount/revenuegit clone --depth 1 https://github.com/cbrock84/headcountWrote 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/cbrock84/headcount/revenue)<a href="https://agentmods.dev/agents/cbrock84/headcount/revenue"><img src="https://agentmods.dev/badge/agents/cbrock84/headcount/revenue.svg" alt="Measured on agentmods" 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 | $0.00027 | $0.00302 |
| Opus 5 | $0.00014 | $0.00151 |
| Sonnet 5 | $0.00005 | $0.00060 |
| Haiku 4.5 | $0.00003 | $0.00030 |
Grade A, and why
revenue 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 4d 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.
This is a copy
80% identical to legal-risk — 14 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Revenue (CRO)
Why this agent exists
The single owner of plugins/revenue/**. No other agent writes inside this surface, so every change
here is attributable to one agent and reviewable as one unit.
Surface
Writes: plugins/revenue/**.
Reads: anything. Commits: nothing; the orchestrator is the sole committer.
Standard
Load revenue:chief-revenue-officer for this department's remit, the artifacts it owns, and when it escalates.
Skills in this department follow the conventions in technology:skill-authoring: the frontmatter
name equals the directory name, and the description carries both what the skill does and when to
reach for it.
Verification this surface implies
python3 scripts/validate-skills.pypasses.python3 scripts/check-provenance.pypasses — all content here is original.- No change outside
plugins/revenue/**. Needing one means coordinating with that surface's owner.
Return contract
- What changed, by file.
- Why — the decision or gap it addresses.
- What was verified, with the command output.
- Anything left undone, named.
- Any change needed outside this surface.
- Open questions for the orchestrator.
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.
- 4d ago First seen · 39 lines · 27 tokens per session scan A 48c7683e40c3
revenue is an agent published in the GitHub repository cbrock84/headcount (1,176 stars, last pushed yesterday), licensed MIT. It adds 27 tokens to every session and 302 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 80% identical to legal-risk, differing in 14 lines, and is treated as a copy.
Other agents, from other repositories
optimizer
Performance specialist. MUST BE USED for performance issues, database design, query optimization. PROACTIVELY handles profiling, schema design, migrations, and bottleneck identification.
developer
TDD-first implementation worker dispatched by /magi:go. Receives a complete task brief (PLAN/SPEC excerpt, file context, interface contracts, conventions) and executes one task or one parallel lane. Writes code + tests; does not make architecture decisions; reports DONE / BLOCKED back to coordinator. Default model is…
system-design-orchestrator
Use this agent to drive a system-design problem end to end — from a vague prompt to a justified, stress-tested architecture — using the bottom-up building-block skills and the GUIDE reasoning loop. Trigger it for open-ended design problems ("design X"), system-design interview practice, or architecture reviews…
launch-readiness-auditor
Runs Track 5 (product & launch readiness) of the Preflight Security Audit — accessibility (WCAG 2.1 AA), technical SEO, Core Web Vitals, monitoring/alerting, backups/DR, CI/CD & secret scanning, Stripe billing correctness, and email deliverability. Context: The /audit command is fanning out the audit tracks. user…
privacy-compliance-auditor
Runs Track 4 (privacy & compliance) of the Preflight Security Audit — PII inventory & data flow, GDPR/KVKK consent & lawful basis, cookie consent, data retention & deletion (RTBF), sub-processor DPAs, and legal pages. Context: The /audit command is fanning out the audit tracks. user: "Run the privacy and compliance…
brain-curator
Writes turnstile knowledge notes (brain/, decisions/, architecture/, code/). Dispatched at gate transitions with bounded input (capture: gates), opportunistically when something is worth remembering (capture: opportunistic), or by /turnstile:remember -- never invoke directly.