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/zeekeey-jpeg/leroy-hq/quick-referencegit 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/quick-reference)<a href="https://agentmods.dev/agents/zeekeey-jpeg/leroy-hq/quick-reference"><img src="https://agentmods.dev/badge/agents/zeekeey-jpeg/leroy-hq/quick-reference.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.00000 | $0.02238 |
| Opus 5 | $0.00000 | $0.01119 |
| Sonnet 5 | $0.00000 | $0.00448 |
| Haiku 4.5 | $0.00000 | $0.00224 |
Grade A, and why
QUICK-REFERENCE 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 5d 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 — 275 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Org Chart - Quick Reference
Version: 1.0
🎯 Core Principle
C-suite delegates, workers execute. Period.
5-Tier Hierarchy
Tier 1: C-Suite → Coordination ONLY (NO Edit/Write)
Tier 2: VP Level → Oversight ONLY (NO Edit/Write)
Tier 3: Management → Limited Edit/Write (domain-specific)
Tier 4: Specialists → Full Edit/Write (implementation)
Tier 5: Support → Read-only (monitoring/research)
✅ Who Can Write Code?
| Agent | Can Edit/Write? | Domain |
|---|---|---|
| builder | ✅ YES | Production code, tests, config |
| designer | ✅ YES | Design systems, UI components |
| forge | ✅ YES | Data operations, ETL, large-scale |
| professor | ✅ YES | Educational content, domain instruction |
| guardian | ✅ YES | QC audits, pre-commit validation |
| legal | ✅ YES | Contracts, legal docs |
| janitor | ✅ YES | Cleanup, maintenance |
| proposal-writer | ✅ YES | Sales proposals, presentations |
❌ Who CANNOT Write Code?
| Agent | Tool Access | Why |
|---|---|---|
| conductor (COO) | Coordination only | Delegates to builder/designer/forge |
| cto | Coordination only | Sets architecture, builder implements |
| vp-engineering | Coordination only | Reviews code, builder writes it |
| chief-of-staff | Reports only | Tracks timelines, doesn't implement |
| scout | Read-only | Observes patterns, doesn't modify |
| planner | Read-only | Tracks tasks, doesn't execute |
🚨 Red Flags (Violations)
Critical Violations
- ❌ C-suite uses Edit/Write tools
- ❌ C-suite uses >15 tools per task
- ❌ VP uses Edit/Write tools
- ❌ Implementation work not delegated
How to Spot Violations
conductor (Design workflow) · 44 tool uses · 65.3k tokens
^^^^^^^^^^
RED FLAG: Should have delegated!
What should happen instead:
conductor (Coordinate workflow) · 8 tool uses
├─ builder (Implement workflow) · 28 tool uses
└─ guardian (Review workflow) · 12 tool uses
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.
- 5d ago First seen · 275 lines · 0 tokens per session scan A 722a1ad41bfb
QUICK-REFERENCE is an agent published in the GitHub repository Zeekeey-jpeg/LeRoy-HQ (10 stars, last pushed 12d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,238 tokens. 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.
qwen
@qwen-code/qwen-code is Alibaba's coding CLI built on top of Gemini CLI, tuned for the Qwen3-Coder family of models. adapters drives it via the qwen binary.
agent-logs
View container logs for debugging and real-time telemetry metrics in the agent header.
Explore
Fast read-only codebase & docs exploration. Returns structured findings, never raw file dumps.
Audit
Deep security + performance audit of a specific diff. Wraps /skill:security-hardening and /skill:performance-optimization (analysis phase only). Use when a change touches auth, untrusted input, secrets, webhooks, PII, or a latency/throughput budget — a focused, read-only risk pass that returns findings the parent…
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+)…