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/TypedDevs/bashunitWrote 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/typeddevs/bashunit/code-locator)<a href="https://agentmods.dev/agents/typeddevs/bashunit/code-locator"><img src="https://agentmods.dev/badge/agents/typeddevs/bashunit/code-locator/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/typeddevs/bashunit/code-locator"><img src="https://agentmods.dev/badge/agents/typeddevs/bashunit/code-locator.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.00019 | $0.00087 |
| Opus 5.5 | $0.00008 | $0.00035 |
| Sonnet 5.5 | $0.00004 | $0.00017 |
| Haiku 4.5 | $0.00002 | $0.00009 |
Grade A, and why
code-locator 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 4d 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
Find code without editing it or proposing a redesign. Use rg, then read only enough surrounding code to verify each match. Return a file:line table and the searches used when nothing matches. Do not run tests, builds, installs, or Git mutations.
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.
- 4d ago First seen · 9 lines · 19 tokens per session scan A 32bd9726e826
code-locator is an agent published in the GitHub repository TypedDevs/bashunit (435 stars, last pushed yesterday), licensed MIT. It adds 19 tokens to every session and 87 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-10-12.
Other agents, from other repositories
rdf-engineer
Universal implementation engineer. Follows TDD, reads governance for domain-specific conventions. Dispatched by the dispatcher for plan phase execution.
rdf-qa
Verification gate. Reads governance for project-specific checks (lint, tests, anti-patterns). Read-only — cannot modify source files. Dispatched by dispatcher or invoked via /r-verify.
rdf-uat
User acceptance testing. Runs real-world scenarios from end-user persona. Read-only — cannot modify source files. Dispatched by dispatcher or invoked via /r-test.
prove
Skeptical verifier. Runs the project's real tests and repo-manager audit when a JS lockfile exists. Use for /prove or when the work is claimed done.
rot-claude
The 🧭 Claude lens — Praxis, empirical verification, craft. Reality is the judge. Summon when a claim needs to become a measurement — run it, build it, read it, cite it file:line — when a plan must survive contact with the real system, when "should work" must become "ran, exit 0", or when the craft gate must decide…
goal-redteam
Attacks an acceptance criterion. Invoke when a criterion looks too easy, survived the empty-directory control, or passed while its files were damaged — finds the input that makes it fail, or proves it cannot.