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/grcengclub/claude-grc-engineering/testing-plangit clone --depth 1 https://github.com/GRCEngClub/claude-grc-engineeringWrote 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/grcengclub/claude-grc-engineering/testing-plan)<a href="https://agentmods.dev/commands/grcengclub/claude-grc-engineering/testing-plan"><img src="https://agentmods.dev/badge/commands/grcengclub/claude-grc-engineering/testing-plan.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.1 | $0.00010 | $0.04125 |
| Opus 5 | $0.00005 | $0.02063 |
| Sonnet 5 | $0.00002 | $0.00825 |
| Haiku 4.5 | $0.00001 | $0.00413 |
Grade A, and why
testing-plan 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 2d 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.
The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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.
- 2d ago First seen · 854 lines · 10 tokens per session scan A feac88476ab6
testing-plan is a command published in the GitHub repository GRCEngClub/claude-grc-engineering (395 stars, last pushed 6d ago), with no licence file. It adds 10 tokens to every session and 4,125 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-09-03.
Other commands, from other repositories
comply
SAIL V2 compliance checklist — ISO/IEC 42001, EU AI Act, OWASP LLM/Agentic, DASF, AIUC-1. All five frameworks by default, or only those named.
ai-act-scan
Scan a codebase for EU AI Act compliance evidence and gaps. Produces a dimension-scored report with per-file findings, architecture graph, and prioritized recommendations.
ai-act-scan-fix
Scan a codebase, then propose concrete remediation (code edits, new files, tests) for the top compliance gaps. Does NOT auto-apply — always shows the plan first.
report
Produce executive and technical compliance reports.
roadmap
7-phase SAIL V2 security roadmap plus per-phase maturity profile, built from the current repo and conversation context.
legal-audit-de-update
Aktualisiert das legal-audit-de Plugin selbst (neue Plugin-Version vom Marketplace ziehen) UND refreshed die KB gegen Primärquellen. All-in-One-Update.