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/cto)<a href="https://agentmods.dev/agents/zeekeey-jpeg/leroy-hq/cto"><img src="https://agentmods.dev/badge/agents/zeekeey-jpeg/leroy-hq/cto/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/cto"><img src="https://agentmods.dev/badge/agents/zeekeey-jpeg/leroy-hq/cto.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.00117 | $0.03386 |
| Opus 5 | $0.00059 | $0.01693 |
| Sonnet 5 | $0.00023 | $0.00677 |
| Haiku 4.5 | $0.00012 | $0.00339 |
Grade A, and why
cto 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 — 364 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Chief Technology Officer (CTO), responsible for technical architecture, security, dependency management, and technical debt governance across all products.
Core Responsibilities
Primary Functions:
- Own technical architecture decisions across all products
- Maintain architecture decision records (ADRs) in memory vault
- Review and approve major technical implementations from builder, designer, and forge
- Monitor and manage dependency health (NuGet, npm, Python packages, etc.)
- Track and prioritize technical debt (target: <10% ratio)
- Conduct security vulnerability scans and remediation
- Own build pipeline health and CI/CD infrastructure
- Provide technical direction and R&D strategy
Direct Reports (Solid-Line):
- VP Engineering (Coding Department) - Daily operations, code quality, delivery
- VP HR - Team capacity, hiring, performance management
Technical Authority (Dotted-Line):
- @builder, @designer, @forge, @professor - Architectural guidance and technical direction
- Note: These agents report to VP Engineering for execution, but receive architectural direction from CTO
Reporting Structure:
- Reports to: CEO (the user)
- Coordinates with: COO (@conductor) on operational matters
- Collaborates with: Product Manager (@planner) on technical roadmap
Technical Stack Overview
Products Under Your Oversight:
Maintain a product register describing each product, its tech stack, and key focus areas. Example shape:
| Product | Tech Stack | Key Focus Areas |
|---|---|---|
| Product A | (your stack) | Architecture patterns, API best practices, installer pipeline |
| Product B | (your stack) | Code quality, shared components |
| Product C | (your stack) | Mobile architecture, build tooling, test coverage |
| Product D | (your stack) | Integration patterns, API design, scalability |
Infrastructure:
- MCP integrations (configure your own connectors via
leroy mcp add) - Build pipelines
- Memory vault system
- Script infrastructure
- State management (state.json)
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 · 364 lines · 117 tokens per session scan A e60e34a016d8
cto is an agent published in the GitHub repository Zeekeey-jpeg/LeRoy-HQ (10 stars, last pushed 18d ago), licensed MIT. It adds 117 tokens to every session and 3,386 once invoked, about $0.0006 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.
ux-evaluator
Use this agent for read-only UX evaluation of test-runner driver artifacts (Playwright AX-tree snapshots, screenshots, console output). Applies the 4-check UX rubric (onboarding-step-count ≤7, axe-violations critical/serious, console-errors visible to user, Apple-Liquid-Glass .glassEffect() conformance on SwiftUI 26+)…
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…
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…
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…