Borrowing it
Nothing to install: this file belongs to scrypster/muninndb. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/scrypster/muninndb/develop/.claude/agents/increment-builder.mdgit clone --depth 1 https://github.com/scrypster/muninndbWrote 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/scrypster/muninndb/increment-builder)<a href="https://agentmods.dev/agents/scrypster/muninndb/increment-builder"><img src="https://agentmods.dev/badge/agents/scrypster/muninndb/increment-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/scrypster/muninndb/increment-builder"><img src="https://agentmods.dev/badge/agents/scrypster/muninndb/increment-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.00084 | $0.01609 |
| Opus 5.5 | $0.00034 | $0.00644 |
| Sonnet 5.5 | $0.00017 | $0.00322 |
| Haiku 4.5 | $0.00008 | $0.00161 |
Grade A, and why
increment-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 2mo 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.
The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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.
- 2mo ago First seen · 139 lines · 84 tokens per session scan A 2d1a81a6bc4d
increment-builder is an agent published in the GitHub repository scrypster/muninndb (335 stars, last pushed 2d ago), with no licence file. It adds 84 tokens to every session and 1,609 once invoked, about $0.0003 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-30.
Other agents, from other repositories
tl-builder
Team-loop builder for an unregulated work package. Works in its own git worktree from a brief at team/packages/WP-nnn.md; writes the package's tests first in their own commit and stops, then builds when the lead resumes it. Use at steps 5 and 6 of the team loop. Not for regulated packages (tl-builder-regulated) and…
tl-builder-regulated
Team-loop builder for a regulated work package (service-charge maths, demands, client money, leaseholder-facing output, migrations and access policies, retention). Works in its own git worktree, merges the independent test writer's commit T first, then builds against it. Use at step 6 of the team loop for regulated…
tl-test-writer
Team-loop test writer for a regulated work package. Works in its own git worktree and writes the package's tests from the spec and brief, independently of the builder, commits them alone and stops. Use at step 5 of the team loop for regulated packages only. Never writes implementation.
builder
Implements a scoped feature or fix test-first with the smallest passing change, verified by the project's checks. Use when the design is settled and code needs writing.
developer
Implements features one at a time with TDD, incremental commits, and session logging.
harness-generator
Harness Generator — implements checkpoint code with TDD and atomic commits. Use when harness orchestrator needs code generation for a checkpoint.