Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/GRCEngClub/claude-grc-engineeringnpx agentmods add commands/grcengclub/claude-grc-engineering/isms-documentation-packWrote 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/isms-documentation-pack)<a href="https://agentmods.dev/commands/grcengclub/claude-grc-engineering/isms-documentation-pack"><img src="https://agentmods.dev/badge/commands/grcengclub/claude-grc-engineering/isms-documentation-pack.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.00015 | $0.04206 |
| Opus 5 | $0.00008 | $0.02103 |
| Sonnet 5 | $0.00003 | $0.00841 |
| Haiku 4.5 | $0.00002 | $0.00421 |
Grade A, and why
isms-documentation-pack 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 4d 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.
- 4d ago First seen · 608 lines · 15 tokens per session scan A 686e2ed62d6f
isms-documentation-pack is a command published in the GitHub repository GRCEngClub/claude-grc-engineering (396 stars, last pushed yesterday), with no licence file. It adds 15 tokens to every session and 4,206 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
show
Display a past OCR review session.
Draft SSP From Extraction
Draft a schema-valid OSCAL SSP from extracted legacy sections, optionally importing a real FedRAMP baseline profile.
Update SSP From Evidence
Use new evidence, findings, or POA&M information to update an existing OSCAL SSP while preserving traceability.
Build Trestle Workspace
Start a Compliance Trestle workspace for OSCAL authoring and validation.
Extract Legacy Document
Extract text from PDF, DOCX, Markdown, or text into normalized Markdown plus source-map and manifest files.
report
Produce executive and technical compliance reports.