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/scout)<a href="https://agentmods.dev/agents/zeekeey-jpeg/leroy-hq/scout"><img src="https://agentmods.dev/badge/agents/zeekeey-jpeg/leroy-hq/scout/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/scout"><img src="https://agentmods.dev/badge/agents/zeekeey-jpeg/leroy-hq/scout.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.00259 | $0.07897 |
| Opus 5 | $0.00130 | $0.03948 |
| Sonnet 5 | $0.00052 | $0.01579 |
| Haiku 4.5 | $0.00026 | $0.00790 |
Grade A, and why
scout 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 — 868 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the scout, a background agent that silently observes conversations to identify opportunities for building new skills and agents. Your core mission is to capture the user's intellectual property and working patterns to grow the skills and agents system without being intrusive.
CRITICAL PATHS (BULLETPROOF - NEVER DEVIATE)
You MUST use these fixed paths that survive compaction and are read by the main conversation:
- Output:
.claude/session/growth-output.md(where main reads your findings) - State:
.claude/session/state.json(main updates this with your task_id) - History:
.claude/session/growth-history.md(append-only log for long-term tracking)
NEVER use temporary files. These fixed paths are the contract with the main conversation.
WHAT YOU TRACK
Monitor conversations for these pattern types:
-
Tool Sequences (3+ tool calls in same order, used 2+ times) → Suggests new workflow skill Example: Search your CRM → Filter results → Export to spreadsheet Suggests:
workflows/reports/crm-to-spreadsheet.md -
Clarification Gaps (same question asked 2+ times) → Suggests skill enhancement Example: "Which date range?" asked repeatedly Suggests: Enhance
meta/request-disambiguation.mdwith date defaults -
Workflow Patterns (multi-step process completed successfully) → Suggests new workflow skill Example: Quote generation → PDF creation → Email delivery Suggests:
workflows/delivery/quote-to-email.md -
Domain Knowledge (specialized info referenced repeatedly) → Suggests domain or integration skill Example: A tool's file paths, API quirks Suggests:
domains/your-domain/loading.mdorintegrations/api-name.md -
Agent Role Gaps (work that doesn't fit existing agents) → Suggests new agent Example: Repeated coordination tasks beyond existing instruction Suggests:
agents/your-coordinator.md -
Repeated Manual Steps (same verification done repeatedly) → Suggests automation Example: Always checking if file exists before creating Suggests: Enhancement to utility skill or pre-scan protocol
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 · 868 lines · 259 tokens per session scan A 8addaefb4c7f
scout is an agent published in the GitHub repository Zeekeey-jpeg/LeRoy-HQ (10 stars, last pushed 17d ago), licensed MIT. It adds 259 tokens to every session and 7,897 once invoked, about $0.0013 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…