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 plugins/djadmin/fort/marketplace/plugin marketplace add djadmin/fortgit clone --depth 1 https://github.com/djadmin/fortGrade A, and why
fort 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 yesterday.
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
{
"name": "fort",
"owner": {
"name": "Dheeraj Joshi",
"url": "https://github.com/djadmin"
},
"metadata": {
"description": "Audit your Mac's security in one command from Claude Code, understand every finding in plain language, and fix what's safe. Drives the fort CLI over your shell.",
"version": "0.3.0"
},
"plugins": [
{
"name": "fort",
"source": "./plugin",
"description": "Audit your Mac's security posture, understand what each finding means and why it matters, then fix what's safe, all from Claude Code. Wraps the fort CLI over your shell. Read-only by default; never applies a fix without your explicit go-ahead. Findings also map to SOC 2 / ISO 27001 / NIST / CIS if you need audit evidence.",
"version": "0.3.0",
"license": "MIT",
"homepage": "https://djadmin.github.io/fort",
"keywords": ["security", "macos", "compliance", "soc2", "iso27001", "endpoint", "hardening"]
}
]
}
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.
- yesterday First seen · 23 lines scan A 2f2532c01b16
fort is a plugin published in the GitHub repository djadmin/fort (78 stars, last pushed 1mo ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
air-blackbox
Plugin marketplace listing 1 plugin: air-blackbox.
air-blackbox
EU AI Act compliance scanner and trust infrastructure for Python AI projects.
prowler-plugins
Prowler Cloud Security for Claude Code.
xberg
Local document extraction: text, tables, metadata, images from 106 formats with optional OCR.
section-508
Expert Section 508 compliance advisor for US federal ICT accessibility — VPAT/ACR completion, WCAG 2.0 AA audits, remediation planning, PDF accessibility, procurement language, keyboard and screen reader testing, undue burden assessments, and agency compliance workflows.
gonzo
Set up and use Gonzo, the open-source terminal log analysis tool. Detects deployment platforms (Vercel, Supabase, K8s, Docker, AWS, Cloudflare, Fly, Render, Railway, Netlify), generates the right pipe command with platform-specific normalizers, and configures AI analysis. Use when the user wants to tail, watch, stream.