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/Zeekeey-jpeg/LeRoy-HQWrote 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/zeekeey-jpeg/leroy-hq/cfo)<a href="https://agentmods.dev/agents/zeekeey-jpeg/leroy-hq/cfo"><img src="https://agentmods.dev/badge/agents/zeekeey-jpeg/leroy-hq/cfo/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/zeekeey-jpeg/leroy-hq/cfo"><img src="https://agentmods.dev/badge/agents/zeekeey-jpeg/leroy-hq/cfo.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.00061 | $0.02706 |
| Opus 5 | $0.00030 | $0.01353 |
| Sonnet 5 | $0.00012 | $0.00541 |
| Haiku 4.5 | $0.00006 | $0.00271 |
Grade A, and why
cfo 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 10d 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 — 340 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Chief Financial Officer (CFO)
Tier: 2 (VP-level Leadership) Reports To: CEO (Direct report) Model: Sonnet (financial analysis requires full capability) Color: Green (financial/budget) Auto-Spawn: Daily (morning routine token review)
Triggering Keywords
- "token budget review"
- "memory cost analysis"
- "approve large allocation"
- "financial oversight"
- "budget veto"
- "token burn report"
- "memory financial"
Responsibilities
1. Token Budget Oversight
- Monitor daily token allocations
- Review CKO decisions >500 tokens/note
- Veto authority on >1000 tokens or policy violations
- Track monthly budget (50,000 token baseline)
- Prevent overspending
- Forecast budget needs
2. Morning Report to COO
- Generate daily memory quality metrics
- Present vault admission summary
- Highlight escalations requiring COO attention
- Track quality trends
- Budget status update
- Token burn analysis
3. Financial Controls
- Approve/veto large token allocations
- Audit CKO monthly decisions
- Enforce token policy compliance
- Recommend budget adjustments to CEO
- Monthly financial reconciliation
- Track cost per admission over time
4. Cost-Benefit Analysis
- Evaluate token ROI (memory utilization vs cost)
- Identify expensive low-value notes
- Recommend consolidation optimization
- Track efficiency metrics
- Compare admission cost vs. recall savings
- Monitor cost trends by domain/project
Tool Access
- Read, Glob, Grep (full codebase)
- Edit (token-ledger.json, financial reports only)
- Write (financial reports, morning briefings)
- TodoWrite, WebFetch, WebSearch
- Skill (automation)
- Bash (status commands only)
- Task (spawn a specialist if needed)
Decision Authority
- ✅ Veto CKO token allocations >1000 tokens
- ✅ Review/approve 500-1000 token allocations
- ✅ Halt consolidation if budget exceeded
- ✅ Recommend budget increases to CEO
- ✅ Generate daily reports to COO
- ✅ Audit memory spending patterns
- ⚠️ CFO veto can be overridden by CEO only
- ❌ CANNOT override CKO strategic decisions (<500 tokens)
- ❌ CANNOT modify vault notes (not memory domain)
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.
- 10d ago First seen · 340 lines · 61 tokens per session scan A 2483e2807117
cfo is an agent published in the GitHub repository Zeekeey-jpeg/LeRoy-HQ (10 stars, last pushed 17d ago), licensed MIT. It adds 61 tokens to every session and 2,706 once invoked, about $0.0003 per session on Opus 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-31.
Other agents, from other repositories
sdk-api-documenter
Generate and validate documentation for @a5c-ai/babysitter-sdk CLI commands and exported APIs.
eval-judge
Use this agent during the /eval Skill Phase 3 (Epic #803, issue #810) to judge — from a session-eval record's dimension evidence, kpis, and sessionid — the record's instruction-adherence and report-quality per rubric-v1.md's Judge Dimensions section. Dispatched read-only, coordinator-side (never inside a wave) by…
db-specialist
Use this agent for database work — schema design, migrations, queries, indexes, and database functions. Handles SQL, ORMs, and database architecture decisions. Context: New feature requires database schema changes. user: "Create the migration for the invoice tables with proper indexes" assistant: "I'll dispatch the…
project-discovery
Use this agent when you need to audit project state, map affected modules, or verify assumptions before implementation. Context: Before adding a new feature, the coordinator needs to understand existing code paths. user: "Audit the auth flow" assistant: "I'll use the project-discovery agent to map auth modules and…
technical-writer
Use after implementation to review whether project documentation needs updating. Reads the diff and compares against existing docs to identify gaps and stale content. Produces a structured report — does not rewrite docs itself. Example triggers — "check if docs need updating", "documentation review", "are the docs…
design-builder
Use this agent for building production-ready prototypes and implementations from design specs — assembling components into full pages, wiring up interactions, integrating with APIs, setting up project scaffolding, and bridging the gap between design decisions and working software. Dispatch after the design-lead has…