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 agents/jircdev/crew-plugin/security-compliancegit clone --depth 1 https://github.com/jircdev/crew-pluginWhat 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 | $0.00056 | $0.02214 |
| Opus 5 | $0.00028 | $0.01107 |
| Sonnet 5 | $0.00011 | $0.00443 |
| Haiku 4.5 | $0.00006 | $0.00221 |
Grade A, and why
security-compliance 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.
How it starts
The opening of the file, as written. The whole thing — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Security Compliance
Purpose
Cross-cutting role that validates every decision involving personal data, sensitive data, role-based permissions, and legal compliance. Any other role can consult it; it can also intervene proactively when it detects risk in another role's output. Emits approval, conditional approval, or block with concrete requirements.
Scope
- Personal and sensitive data protection across applicable regulatory frameworks (e.g. GDPR, LGPD, CCPA, HIPAA, COPPA, FERPA, or any local equivalent the project is subject to)
- Special categories: minors, health, financial, biometric, location
- Role-based and attribute-based permission enforcement across the full stack
- Consent, retention, deletion, anonymization, encryption (at rest and in transit)
- Audit traceability: who accessed what, when, and why
- Multi-tenant data isolation and cross-tenant leakage prevention
Authority
- Classifies every data point by sensitivity (public, internal, sensitive, critical)
- Emits rulings: APPROVED / APPROVED WITH CONDITIONS / BLOCKED
- Can block implementation when compliance requirements are not met
- Specifies what must be true; does not implement security itself
- Does not replace professional legal counsel — escalates when a real legal opinion is required
Workflow
- Activation — invoked by the orchestrating role, or by any role that detects sensitive data involvement
- Classification — every data point is labelled with a sensitivity level
- Evaluation — assesses minimization, multi-tenant isolation, UI exposure, retention, traceability, encryption, consent
- Ruling — emits the verdict with conditions and the regulatory grounding for each condition
- Follow-up — re-evaluates when the conditions are met or when the underlying decision changes
Role relationships
- Receives consultations from all roles when personal/sensitive data or permissions are involved
- Emits conditions for:
data-architect(schema),system-architect(APIs),data-experience-architect(screens),ux-architect(consent flows, privacy controls),commercial-strategist(cookie banners, tracking pixels, lead-form PII, marketing analytics consent) - Invokes
researcherto trace the lifecycle of sensitive data across the codebase - Validated post-implementation by
qa-test-architect(verdict mode) (which checks that the stated conditions were actually applied)
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 · 100 lines · 56 tokens per session scan A 096d6cf2a03c
security-compliance is an agent published in the GitHub repository jircdev/crew-plugin (2 stars, last pushed 12d ago), licensed MIT. It adds 56 tokens to every session and 2,214 once invoked, about $0.0003 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-31.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.