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/mlunato47/claude-grc-plugin/conmon-guidegit 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/conmon-guide)<a href="https://agentmods.dev/commands/mlunato47/claude-grc-plugin/conmon-guide"><img src="https://agentmods.dev/badge/commands/mlunato47/claude-grc-plugin/conmon-guide.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 | $0.00005 | $0.00577 |
| Opus 5 | $0.00003 | $0.00289 |
| Sonnet 5 | $0.00001 | $0.00115 |
| Haiku 4.5 | $0.00001 | $0.00058 |
Grade A, and why
conmon-guide 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 5d 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:
- conmon-guide — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/grc:conmon-guide
Continuous monitoring guidance by topic.
Usage
/grc:conmon-guide [topic]
Arguments
- topic: The ConMon topic area. Accepts:
monthly— Monthly deliverables and activitiesannual— Annual deliverables and activitiespoam— POA&M management and lifecyclescanning— Vulnerability scanning requirements and processesmetrics— ConMon metrics and reportinglifecycle— Full ISCM lifecycle overviewtooling— Automated tooling categories and requirements
Examples
/grc:conmon-guide monthly
/grc:conmon-guide poam
/grc:conmon-guide scanning
/grc:conmon-guide lifecycle
Behavior
When invoked:
-
Identify the topic from the argument.
-
Read the appropriate reference file(s):
monthly→conmon/monthly-deliverables.mdannual→conmon/annual-deliverables.mdpoam→conmon/poam-management.mdscanning→conmon/automated-tooling.md+conmon/monthly-deliverables.mdmetrics→conmon/iscm-lifecycle.md+conmon/monthly-deliverables.mdlifecycle→conmon/iscm-lifecycle.mdtooling→tooling/grc-tooling-categories.md+conmon/automated-tooling.md
-
Present guidance structured by:
- What activities are required
- Who is responsible (roles)
- When / how frequently
- What deliverables are produced
- Framework-specific requirements (FedRAMP, FISMA)
- Common pitfalls and best practices
- Automation opportunities
-
If no topic provided, show a summary of all ConMon areas with brief descriptions and ask which to dive into.
Output Format
## Continuous Monitoring: [Topic]
### Overview
[Brief description of this ConMon area]
### Activities
| Activity | Frequency | Responsible Role | Deliverable |
|----------|-----------|-----------------|-------------|
### Requirements
[Framework-specific requirements — FedRAMP, FISMA, etc.]
### Best Practices
- [Practice 1]
- [Practice 2]
### Common Pitfalls
- [Pitfall 1]
- [Pitfall 2]
### Automation Opportunities
- [Opportunity 1]
- [Opportunity 2]
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.
- 5d ago First seen · 88 lines · 5 tokens per session scan A a58a5e35de20
conmon-guide is a command published in the GitHub repository mlunato47/claude-grc-plugin (181 stars, last pushed 1mo ago), licensed MIT. It adds 5 tokens to every session and 577 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
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.