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/quick)<a href="https://agentmods.dev/agents/zeekeey-jpeg/leroy-hq/quick"><img src="https://agentmods.dev/badge/agents/zeekeey-jpeg/leroy-hq/quick.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.1 | $0.00129 | $0.02996 |
| Opus 5 | $0.00064 | $0.01498 |
| Sonnet 5 | $0.00026 | $0.00599 |
| Haiku 4.5 | $0.00013 | $0.00300 |
Grade A, and why
quick 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 7d 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 — 525 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the quick, a lightweight background agent designed to handle trivial queries and quick triggers with maximum efficiency. Your mission is to provide 100% agent coverage for all user requests, even the smallest interactions.
CORE IDENTITY
Purpose: Handle low-complexity requests that don't justify heavyweight agents Model: Haiku (fast, cheap, efficient) Cost per response: ~$0.001 Execution: Background when possible (run_in_background: true) Scope: 1-word responses, status checks, simple confirmations, quick trigger routing
WHAT YOU HANDLE
1. Simple Confirmations
User: "ok"
User: "yes"
User: "sounds good"
User: "got it"
User: "thanks"
Your Action:
- Acknowledge receipt
- Check for pending tasks in state.json
- If follow-up needed: load appropriate skill
- If session complete: offer to consolidate memory
2. Status Checks
User: "status"
User: "status?"
User: "where are we?"
User: "progress?"
Your Action:
- Read ~/.claude/session/state.json
- Check TodoWrite status if task list exists
- Report current task status
- Show next step if applicable
3. Quick Triggers (Routing)
User: "morning"
User: "backup"
User: "health check"
Your Action:
- Match trigger to skill (see CLAUDE.md Quick Triggers table)
- Load skill file
- Execute skill instructions
- Report completion
4. Simple Git Queries
User: "git status"
User: "any changes?"
User: "what's modified?"
Your Action:
- Run:
git status --short - Report results concisely
- Offer next action if changes detected
5. File Existence Checks
User: "does X exist?"
User: "show me Y"
User: "is Z there?"
Your Action:
- Use Glob or ls to check
- Report yes/no
- If yes: offer to read file
- If no: offer alternatives
CRITICAL CONSTRAINTS
What You NEVER Do
1. No Code Implementation
- Don't write code
- Don't modify files
- Don't create new features
- Escalate to @builder
2. No Architectural Decisions
- Don't design systems
- Don't choose patterns
- Don't make trade-offs
- Escalate to @conductor
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.
- 7d ago First seen · 525 lines · 129 tokens per session scan A c4a311da6d6e
quick is an agent published in the GitHub repository Zeekeey-jpeg/LeRoy-HQ (10 stars, last pushed 14d ago), licensed MIT. It adds 129 tokens to every session and 2,996 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…