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/mlunato47/claude-grc-pluginWrote 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/mlunato47/claude-grc-plugin/compliance-calendar)<a href="https://agentmods.dev/commands/mlunato47/claude-grc-plugin/compliance-calendar"><img src="https://agentmods.dev/badge/commands/mlunato47/claude-grc-plugin/compliance-calendar/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/mlunato47/claude-grc-plugin/compliance-calendar"><img src="https://agentmods.dev/badge/commands/mlunato47/claude-grc-plugin/compliance-calendar.svg" alt="Reviewed on agentmods" width="80" 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.00008 | $0.01050 |
| Opus 5 | $0.00004 | $0.00525 |
| Sonnet 5 | $0.00002 | $0.00210 |
| Haiku 4.5 | $0.00001 | $0.00105 |
Grade A, and why
compliance-calendar 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 10d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- compliance-calendar — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 145 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/grc:compliance-calendar
Generate a recurring compliance activity calendar by framework.
Usage
/grc:compliance-calendar [frameworks] [format?]
Arguments
- frameworks: One or more frameworks, comma-separated. Accepts:
fedramp,nist,fisma,soc2,iso27001,pci,hipaa,cmmc,all - format (optional):
monthly(default): Month-by-month calendar viewfrequency: Grouped by frequency (daily, weekly, monthly, quarterly, annual)controls: Activities mapped to control IDs
Examples
/grc:compliance-calendar fedramp
/grc:compliance-calendar fedramp,soc2
/grc:compliance-calendar fedramp monthly
/grc:compliance-calendar pci frequency
/grc:compliance-calendar fedramp,soc2,pci controls
Behavior
When invoked:
-
No redaction reminder needed — this is a pure reference command generating calendars from framework knowledge. No user content is processed.
-
Read the appropriate reference files:
skills/grc-knowledge/conmon/compliance-calendar.mdfor consolidated calendar dataskills/grc-knowledge/conmon/monthly-deliverables.mdfor monthly detailskills/grc-knowledge/conmon/annual-deliverables.mdfor annual detailskills/grc-knowledge/conmon/iscm-lifecycle.mdfor lifecycle context
-
Generate the calendar:
For
monthlyformat:- Present a 12-month calendar template
- Monthly recurring activities appear every month
- Quarterly activities placed in Q1-Q4 months
- Annual activities distributed across the year with recommended scheduling
- If multiple frameworks: consolidate overlapping activities, note the strictest frequency
For
frequencyformat:- Group all activities by frequency: Daily, Weekly, Monthly, Quarterly, Semi-Annual, Annual, Event-Driven
- Include responsible role, deliverable, and control reference for each
- If multiple frameworks: show which framework(s) require each activity
For
controlsformat:- Map each recurring activity to its control ID(s)
- Include frequency, responsible role, and deliverable
- Useful for verifying control implementation completeness
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.
- 10d ago First seen · 145 lines · 8 tokens per session scan A 356a0526d33d
compliance-calendar is a command published in the GitHub repository mlunato47/claude-grc-plugin (181 stars, last pushed 1mo ago), licensed MIT. It adds 8 tokens to every session and 1,050 once invoked, about $0.0000 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.
Other commands, from other repositories
deps-audit
Audit project dependencies for vulnerabilities, outdated packages, license conflicts, and supply chain risks — then provide actionable remediation strategies.
review-epo-claims
Analyze patent claims for EPO Art. 84 EPC compliance - clarity, conciseness, support by description.
voice-compliance
Voice/telephony compliance check — invokes voice-ai-reviewer to produce TM-voice-{slug}.md with TCPA, STIR/SHAKEN, state recording-consent, EU AI Act Art. 50, and synth-voice deepfake-law gaps.
at-dsgvo
You are helping an enterprise architect generate an Austrian Data Protection Assessment — the Austrian-specific GDPR layer applied by the Datenschutzbehörde (DSB) under the Datenschutzgesetz (DSG 2018, BGBl. I Nr. 165/1999 as amended). Run this after /arckit:eu-rgpd to add Austrian obligations that go beyond the EU…
au-pspf
You are an enterprise architect generating a Protective Security Policy Framework (PSPF) compliance assessment for an Australian Government entity or contractor handling government information.
compliance-audit
Full regulatory compliance audit for GDPR, HIPAA, SOC2, PCI-DSS, ISO 27001, and other frameworks with gap analysis, remediation planning, and evidence collection.