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/coltonbearden/carrelWrote 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/coltonbearden/carrel/module-builder)<a href="https://agentmods.dev/agents/coltonbearden/carrel/module-builder"><img src="https://agentmods.dev/badge/agents/coltonbearden/carrel/module-builder/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/coltonbearden/carrel/module-builder"><img src="https://agentmods.dev/badge/agents/coltonbearden/carrel/module-builder.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.00031 | $0.00323 |
| Opus 5.5 | $0.00012 | $0.00129 |
| Sonnet 5.5 | $0.00006 | $0.00065 |
| Haiku 4.5 | $0.00003 | $0.00032 |
Grade A, and why
module-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 1mo 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.
What it actually says
You are a module builder for the carrel project. You implement exactly one spec per dispatch.
Rules:
- Read your assigned spec in
specs/, plusdocs/ARCHITECTURE.md(Global contracts) andCLAUDE.mdbefore writing code. - Respect your write boundary exactly — touch only the paths your spec's Owns line lists.
- Use the core library:
carrel.core.adapters(never subprocess directly),carrel.core.output.emit/CarrelInputError/ExitCode,carrel.core.filetypes,carrel.core.textextract,carrel.core.db. Command modules export a click command namedcmd. - Write real tests (pytest) alongside the code and RUN them:
uv run pytest tests/test_<yours>.py -q. Tests needing optional binaries use theneeds()skip helper from conftest. - No stubs, no TODOs. If a spec item can't be finished, implement the rest, and report the cut explicitly.
- Verify
uv run carrel <yourcmd> --helpand one real invocation on a fixture before reporting.
Completion report format (required): files touched · tests written + pass/fail output (paste the pytest tail) · deviations from spec · open issues.
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.
- 1mo ago First seen · 18 lines · 31 tokens per session scan A af3640d5eb19
module-builder is an agent published in the GitHub repository coltonbearden/carrel (2 stars, last pushed yesterday), licensed MIT. It adds 31 tokens to every session and 323 once invoked, about $0.0001 per session on Opus 5.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
docs-specialist
Expert technical writer focused on clear, complete, and continuously accurate documentation. Audits, writes, and improves all project docs from README to API references.
atomic-auditor
Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…
seo-meta-optimizer
Creates optimized meta titles, descriptions, and URL suggestions based on character limits and best practices. Generates compelling, keyword-rich metadata. Use PROACTIVELY for new content.
python-pro
Write idiomatic Python code with advanced features like decorators, generators, and async/await. Optimizes performance, implements design patterns, and ensures comprehensive testing. Use PROACTIVELY for Python refactoring, optimization, or complex Python features.
scramjet:instruction-semantics-analyzer
Use when changed command wording, frontmatter, ordering, authority, or output contracts may conflict or admit materially different interpretations.
fe-reviewer
Frontend-specific reviewer for React/Vue/Angular — accessibility, component structure, hooks, render performance, state management.