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/Goldziher/basemindWrote 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/commands/goldziher/basemind/check)<a href="https://agentmods.dev/commands/goldziher/basemind/check"><img src="https://agentmods.dev/badge/commands/goldziher/basemind/check/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/commands/goldziher/basemind/check"><img src="https://agentmods.dev/badge/commands/goldziher/basemind/check.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.00010 | $0.00207 |
| Opus 5.5 | $0.00004 | $0.00083 |
| Sonnet 5.5 | $0.00002 | $0.00041 |
| Haiku 4.5 | $0.00001 | $0.00021 |
Grade A, and why
check 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 6d 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
Check
Run the commit triad. Use this before every commit.
cargo fmtcargo clippy --workspace --all-targets --tests -- -D warningscargo test --workspacepoly lint .
Each step gates the next. On failure:
cargo fmt— re-stage formatted files.- clippy — fix or justify with a one-line
// allow because…comment. - tests — diagnose the failure; never
#[ignore]to bypass. - poly — fix per the
poly-and-release-workflowskill.
After this passes, run /harden before pushing if the change touches the scanner / extract / index path.
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.
- 6d ago Changed · +7 lines c350b736c1eb
- 1mo ago First seen · 25 lines · 10 tokens per session scan A a45f69e58070
check is a command published in the GitHub repository Goldziher/basemind (112 stars, last pushed today), licensed MIT. It adds 10 tokens to every session and 207 once invoked, about $0.0000 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 commands, from other repositories
pr-enhance
Command "pr-enhance" from ruvnet/ruflo, covering pr-enhance, usage, options, examples and enhance pr.
audio-pass
Functional audio review for implementation, mix coverage, clarity, and player feedback.
proofrag
Evaluate a RAG/LLM app — generate a golden set, judge it, and produce a scorecard.
claude-loop
Use a fresh headless Claude session (Fable by default) as an independent reviewer of the whole repo, area by area (or of one branch's diff with --base), fix every real finding with regression tests, and loop until each area comes back clean twice in a row. The /codex-loop pattern on Anthropic usage. Runs autonomously.
security-sast
Static Application Security Testing (SAST) for code vulnerability analysis across multiple languages and frameworks.
ipd-tr
A command that runs a staged technical review process involving quality, testing, architecture, and requirements checks before a release decision. IPD-OMO is the process named in the add-on; its specialized role names are not explained further in the input.