security-audit

A recurring security review command that runs a scripted four-part checklist against the repository's files. For confirmed problems, it creates GitHub issues, which are tracked tasks in GitHub.

In plain words
What is it for?
Use it for periodic security checks of repository files and for creating follow-up issues for verified findings.
Why use it?
It helps identify security weaknesses in the repository and record confirmed findings so they can be addressed.

Command

Part of the ForgeDock plugin — 5 skills, 46 commands shipped together

Install

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.

agentmods
npx agentmods add commands/rapiercraftstudios/forgedock/security-audit
Clone the repo
git clone --depth 1 https://github.com/RapierCraftStudios/ForgeDock

Or install ForgeDock, the plugin that ships this one along with the rest of its 5 skills, 46 commands.

Per session 27 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 7,211 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin unknown No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00027 $0.07211
Opus 5 $0.00014 $0.03606
Sonnet 5 $0.00005 $0.01442
Haiku 4.5 $0.00003 $0.00721

Measured 3d ago against content hash 1c6f9a336a5a, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

security-audit 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 3d 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.

commands/security-audit.md · 602 lines

The source is not reproduced here

Licensed AGPL-3.0

The repository is licensed AGPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.

Read it on GitHub

Changes

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.

  1. 3d ago First seen · 602 lines · 27 tokens per session scan A 1c6f9a336a5a

Subscribe to this mod's changes

security-audit is a command published in the GitHub repository RapierCraftStudios/ForgeDock (118 stars, last pushed 23d ago), licensed AGPL-3.0. It adds 27 tokens to every session and 7,211 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.