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/gfargo/skillsWrote 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/plugins/gfargo/skills/security)<a href="https://agentmods.dev/plugins/gfargo/skills/security"><img src="https://agentmods.dev/badge/plugins/gfargo/skills/security/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/plugins/gfargo/skills/security"><img src="https://agentmods.dev/badge/plugins/gfargo/skills/security.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
security 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 1mo 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
{
"name": "security",
"description": "Web application firewall management as code with Doorman: create rules, block IPs, rate limit, protect against bots, and deploy WAF configs to Vercel and Cloudflare.",
"version": "1.0.7",
"author": {
"name": "Griffen Fargo",
"email": "[email protected]"
},
"homepage": "https://github.com/gfargo/doorman",
"keywords": [
"security",
"firewall",
"waf",
"vercel",
"cloudflare",
"doorman",
"iac",
"rules",
"ip-blocking",
"rate-limiting",
"bot-protection"
]
}
What it installs
The manifest is a name and a version. 1 skill travel with it, and installing the plugin installs all of them — 73 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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.
- 1mo ago First seen · 24 lines scan A 6f7d19c83b2f
security is a plugin published in the GitHub repository gfargo/skills (2 stars, last pushed today), 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-31.
Other plugins, from other repositories
cloud-inference-skills
Cloud AI inference, training, conversion, and GPU workflows.
cloud-deployment-skills
Cloud deployment routing and provider integration workflows.
hn-brief
Personalized Hacker News brief. Ranks today's stories against a stored interest profile, surfaces a few new topics each run, and learns from which links you click.
sshepherd
Server operations over SSH — health checks, container/service control, log tailing, config edits, Postgres introspection, and declarative deploys — driven through a single compiled CLI that never lets the agent see a password, private key, host, user, or port.
hcloud-skills marketplace
Hetzner Cloud CLI plugin for Claude Code — skills, commands, and safety hooks.
hcloud
Hetzner Cloud CLI skills, commands, and safety hooks for Claude Code.