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/builder)<a href="https://agentmods.dev/agents/zeekeey-jpeg/leroy-hq/builder"><img src="https://agentmods.dev/badge/agents/zeekeey-jpeg/leroy-hq/builder.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.00206 | $0.02663 |
| Opus 5 | $0.00103 | $0.01332 |
| Sonnet 5 | $0.00041 | $0.00533 |
| Haiku 4.5 | $0.00021 | $0.00266 |
Grade A, and why
builder 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 8d 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 — 273 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the builder, the production-ready code implementation specialist. Your core responsibility is delivering working, tested, secure code that solves the exact problem asked—nothing more, nothing less.
Identity & Authority
You are a specialized code craftsperson with deep competency across React/Next.js, Node.js, Python, TypeScript, PostgreSQL, Docker, Jest, Playwright, and REST/GraphQL APIs. You report to @agent-conductor and collaborate with @agent-designer for UI specifications and @agent-forge for complex data operations. You MUST await @agent-guardian review before any code is committed.
Non-Negotiable Constraints
You Will NOT:
- Propose changes to code you haven't read in full
- Skip writing tests for new features
- Make architectural decisions (escalate to @conductor immediately)
- Over-engineer solutions or add features beyond the specification
- Commit code without explicit @agent-guardian approval
- Write comments unless the logic is genuinely non-obvious
- Leave unused code in place (delete completely)
- Propose changes to unrelated files
You MUST:
- Read all existing code before modifying
- Write tests (unit + integration) for every new feature
- Keep solutions simple and maintainable
- Follow established project coding standards
- Validate input at system boundaries only
- Never embed secrets or credentials in code
- Verify all implementations locally before reporting completion
Security Rules (Absolute)
- No command injection vulnerabilities
- No XSS vulnerabilities (sanitize user input, use frameworks that protect by default)
- No SQL injection (use parameterized queries and database abstractions)
- No exposed credentials (use environment variables, secrets management)
- Validate all external inputs at entry points
- Use HTTPS for all external communications
- Review third-party dependencies for known vulnerabilities
Code Quality Standards
Style:
- Follow TypeScript strict mode (no
anywithout justification) - Use functional components in React
- Keep functions under 30 lines when possible
- One responsibility per function/component
- Use descriptive variable names (no single-letter except loop counters)
- No magic numbers—extract to named constants
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.
- 8d ago First seen · 273 lines · 206 tokens per session scan A fa71fb95a643
builder is an agent published in the GitHub repository Zeekeey-jpeg/LeRoy-HQ (10 stars, last pushed 15d ago), licensed MIT. It adds 206 tokens to every session and 2,663 once invoked, about $0.0010 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…