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/djadmin/fort/fort-hardengit clone --depth 1 https://github.com/djadmin/fortWrote 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/djadmin/fort/fort-harden)<a href="https://agentmods.dev/commands/djadmin/fort/fort-harden"><img src="https://agentmods.dev/badge/commands/djadmin/fort/fort-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.00016 | $0.00371 |
| Opus 5 | $0.00008 | $0.00186 |
| Sonnet 5 | $0.00003 | $0.00074 |
| Haiku 4.5 | $0.00002 | $0.00037 |
Grade A, and why
fort-harden scanned grade A with 1 finding 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 5d 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.
Asks for rootlowPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
`fort --only <approved-ids> --fix` (sudo may prompt for a password — that's expected). Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
What it actually says
Audit this Mac and guide the user through fixing what's safe — with explicit approval before any change. This command can modify system settings, so move carefully.
- Audit first:
fort --json(orfort --only $ARGUMENTS --jsonif IDs were given). - Identify the fixable failing checks (
fixable: true,status: fail). Present them as a short list, each with a one-line reason it matters and what fixing it would affect. Leave judgment-call items (admin rights, antivirus, OS upgrade) out of the fix list — explain those and let the user decide. - For each fix the user is interested in, run
fort --only <id> --dry-runand show the exact command fort would run. Let them see it before it happens. - Get an explicit yes for the specific checks. Then apply exactly those:
fort --only <approved-ids> --fix(sudo may prompt for a password — that's expected). Never expand beyond what they approved, and never fix everything implicitly. - Re-run
fort --only <ids> --jsonto confirm each change took effect, and report what changed. - Respect the user's setup: if they say they use SSH, need an admin account, etc., do not push to change it. Their workflow wins over a generic checklist.
Use reference/checks.md from the fort skill for the trade-offs of each fix.
$ARGUMENTS
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.
- 5d ago First seen · 29 lines · 16 tokens per session scan A 51644b9c9048
fort-harden is a command published in the GitHub repository djadmin/fort (78 stars, last pushed 1mo ago), licensed MIT. It adds 16 tokens to every session and 371 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
onboard-interactive
Interactive customer onboarding with Step 0 independent verification (dialog-based, 17 stagegates).
Update SSP From Evidence
Use new evidence, findings, or POA&M information to update an existing OSCAL SSP while preserving traceability.
ai-act-ask
Answer an EU AI Act question grounded in the bundled knowledge base — verbatim statute text, obligation paraphrases, and the compound-risk taxonomy. Offline and deterministic by default; cites the articles it relies on.
annex-a-deep-dive
Deep dive analysis of ISO 27001 Annex A control domains with implementation guidance.
report
Produce executive and technical compliance reports.
iso-mapping
Map controls to ISO 27001/27017/27018 standards.