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 agentmods add commands/goldziher/basemind/hardengit 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/harden)<a href="https://agentmods.dev/commands/goldziher/basemind/harden"><img src="https://agentmods.dev/badge/commands/goldziher/basemind/harden.svg" alt="Measured on agentmods" 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 | $0.00015 | $0.00269 |
| Opus 5 | $0.00008 | $0.00134 |
| Sonnet 5 | $0.00003 | $0.00054 |
| Haiku 4.5 | $0.00002 | $0.00027 |
Grade A, and why
harden 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
Harden
Run the harden harness (real-OSS clones + tool sweep + canaries) and summarize.
-
Run:
BASEMIND_HARDEN_NO_BUILD=1 \ cargo test --release --test harden -- --ignored --nocapture \ 2>&1 | tee /tmp/basemind-harden-$(date +%s).log -
Parse the result via the
harness-interpreteragent (or inline if trivial). -
Report:
- Pass count:
N/8 greenand the names of any failed repos. - Canary status: tokio
spawn, djangoget, reactuseState, ripgrep-shallow truncation. - Any per-repo scan-time delta > 20% vs the documented baseline (
typescript ~23 s eager-L2-on,tokio < 2 s,django < 3 s).
- Pass count:
-
Exit with the harness exit code.
If the user runs /harden full, drop BASEMIND_HARDEN_NO_BUILD=1 and rebuild release first.
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 · 28 lines · 15 tokens per session scan A 5c8bb3a02918
harden is a command published in the GitHub repository Goldziher/basemind (98 stars, last pushed 2d ago), licensed MIT. It adds 15 tokens to every session and 269 once invoked, about $0.0001 per session on Opus 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
index
Index a folder of documents for semantic search.
agent-brain-index
Index documents for semantic search.
agent
Add an AI agent / RAG backend (@convex-dev/agent) to the Convex app.
codesage-reindex
Force an incremental codesage re-index (use when git hooks didn't fire). Auto-cleans orphan vec tables if the config model has changed.
crisis
긴급 상황 대응. 서비스 중단, 봇 다운, 크리티컬 버그, 장애 대응 프로세스. '긴급', '장애 대응', 'crisis', '봇이 죽었어', '서비스 멈췄어' 요청 시 사용.
review-plan-for-task
Please run reviewer subagents to analyse this plan, focussing on.