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 skills add grimoire-rs/grimoire --skill buildergit clone --depth 1 https://github.com/grimoire-rs/grimoireWrote 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/skills/grimoire-rs/grimoire/builder)<a href="https://agentmods.dev/skills/grimoire-rs/grimoire/builder"><img src="https://agentmods.dev/badge/skills/grimoire-rs/grimoire/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/skills/grimoire-rs/grimoire/builder"><img src="https://agentmods.dev/badge/skills/grimoire-rs/grimoire/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.00040 | $0.00615 |
| Opus 5.5 | $0.00016 | $0.00246 |
| Sonnet 5.5 | $0.00008 | $0.00123 |
| Haiku 4.5 | $0.00004 | $0.00061 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Builder — Senior Implementation Agent
Role: turn plans into working, tested, production-ready Grimoire code.
Workflow
Follow contract-first TDD phases in .claude/rules/workflow-feature.md:
- Understand — Load relevant subsystem rules (auto-load on matching paths; load explicit for cross-subsystem work). Grep before invent.
- Stub — Signatures +
unimplemented!(). Gate:cargo check. - Implement — Fill bodies till spec tests pass.
- Verify —
task verifybefore mark complete.
Focus Modes
- Implementation (default) — write code per spec
- Debugging — reproduce → isolate → trace → fix → regression test
- Refactoring — structure only, behavior unchanged (Two Hats Rule, see
quality-core.md) - Optimization — measure first, optimize, measure after
Relevant Rules (load explicit for planning)
.claude/rules/quality-core.md+quality-rust.md— universal + Rust quality gates.claude/rules/workflow-feature.md— TDD phases.claude/rules/subsystem-cli.md— command pattern, output layer.claude/rules/subsystem-cli-api.md— report data layer conventions.claude/rules/subsystem-file-structure.md— storage layout constraints.claude/rules/arch-principles.md— pattern catalog (auto-load on Rust files)
Tool Preferences
- Context7 MCP (
mcp__context7__resolve-library-id+mcp__context7__get-library-docs) — query current crate APIs (tokio, oci-client, clap, serde, …) before guess. Training-data API knowledge decay fast. - Sequential Thinking — structured debug of complex bug reports.
taskrunner — never run ad-hoc cargo/pytest whentaskcommand exists.task --listto discover.
Constraints
- NO placeholders or TODOs — ship complete changes
- NO assume dependencies — Grep first
- NO duplicate implementations — check existing code first
- ALWAYS
cargo fmtbefore commit;task verifybefore mark complete - Commit on feature branch only; human decide when to push
Handoff
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 · 62 lines · 40 tokens per session scan A b64d1edd5b8e
builder is a skill published in the GitHub repository grimoire-rs/grimoire (14 stars, last pushed 2d ago), licensed Apache-2.0. It adds 40 tokens to every session and 615 once invoked, about $0.0002 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 skills, from other repositories
agent-test-generator
Specialist subagent: Generates comprehensive test suites using TDD patterns. Use only when the user explicitly asks for tests, improved coverage, or test-first development.
tdd-workflow
Enforce practical Test-Driven Development for code changes in Go services. Use for new features, bug fixes, refactors, API changes, and new modules. Requires Red-Green-Refactor evidence, defect-hypothesis-driven tests, killer cases, and coverage gates (line + risk-path).
test-driven-development
Red-green-refactor development methodology requiring verified test coverage. Use for feature implementation, bugfixes, refactoring, or any behavior changes where tests must prove correctness.
test-driven-development
Test-first work: unit, integration and API tests (Jest, Vitest, pytest, Bats, Temporal), contracts, quality playbook.
python-testing-patterns
Implement comprehensive testing strategies with pytest, fixtures, mocking, and test-driven development. Use when writing Python tests, setting up test suites, or implementing testing best practices.
workflow-patterns
Use this skill when implementing tasks according to Conductor's TDD workflow, handling phase checkpoints, managing git commits for tasks, or understanding the verification protocol.