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/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/plugins/grcengclub/claude-grc-engineering/grc-diagrams)<a href="https://agentmods.dev/plugins/grcengclub/claude-grc-engineering/grc-diagrams"><img src="https://agentmods.dev/badge/plugins/grcengclub/claude-grc-engineering/grc-diagrams.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
grc-diagrams 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.
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.
- yesterday First seen · 20 lines scan A e7aad25f1f80
grc-diagrams is a plugin published in the GitHub repository GRCEngClub/claude-grc-engineering (398 stars, last pushed 2d ago), with no licence file. 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-09-07.
Other plugins, from other repositories
eu-ai-act
EU AI Act (Regulation (EU) 2024/1689) compliance advisor — risk classification across all four tiers, all 9 prohibited practices (Art. 5), Annex III high-risk use cases, provider and deployer obligations (Arts. 9–17, 26), GPAI model obligations and systemic risk (Arts. 51–55, enforcement Aug 2, 2026), conformity…
swift-csp
SWIFT CSP / CSCF v2026 expert covering all 32 controls (25 mandatory + 7 advisory), including Control 2.4 now mandatory (back-office data flow security). Architecture types A1–A4/B, KYC-SA attestation (window July 1–Dec 31, 2026), independent assessment, gap analysis, fraud prevention, and cross-framework mapping.
ism
Expert Australian Information Security Manual (ISM) advisor for Australian government entities, contractors and supply chains. Gap analysis, system authorisation, IRAP preparation, control scoping, and ASD compliance guidance.
cocounsel-legal
CoCounsel Legal delivers comprehensive Westlaw Deep Research reports with inline, linked citations to Westlaw and Practical Law sources.
sail
Apply the SAIL V2 (Secure AI Lifecycle) framework by Pillar Security to secure AI applications and agents — gap analyses, security roadmaps, maturity assessments, compliance checklists, control prioritization, and vendor RFPs. Grounded in the full 91-risk SAIL catalog.
gdpr-compliance
GDPR compliance assistant — code and system audits, privacy notice drafting, DPAs, DPIAs, data flow reviews, and authoritative article-cited Q&A.