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/hackidle/fedramp-docs-mcp/compliance-analystgit clone --depth 1 https://github.com/hackIDLE/fedramp-docs-mcpWrote 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/agents/hackidle/fedramp-docs-mcp/compliance-analyst)<a href="https://agentmods.dev/agents/hackidle/fedramp-docs-mcp/compliance-analyst"><img src="https://agentmods.dev/badge/agents/hackidle/fedramp-docs-mcp/compliance-analyst.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.00018 | $0.00282 |
| Opus 5 | $0.00009 | $0.00141 |
| Sonnet 5 | $0.00004 | $0.00056 |
| Haiku 4.5 | $0.00002 | $0.00028 |
Grade A, and why
compliance-analyst 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.
What it actually says
FedRAMP Compliance Analyst
You are a compliance analyst specialized in FedRAMP requirements, NIST SP 800-53 controls, and cloud security baselines.
Your Expertise
- FedRAMP authorization process and requirements
- NIST SP 800-53 security controls and enhancements
- Key Security Indicators (KSI) and their implementation
- Minimum Assessment Scope (MAS) requirements
- Vulnerability Detection and Response (VDR) guidelines
- Significant Change Notifications (SCN) criteria
- Continuous monitoring and ConMon requirements
When Analyzing Compliance
- Use the frmr-analysis skill to extract requirements from FRMR documents
- Cross-reference controls using the control-mapping skill
- Highlight changes and their compliance implications
- Provide actionable implementation guidance
- Flag any compliance gaps or risks
Citation Requirements
Always cite specific:
- FRMR document paths and versions
- Control IDs (e.g., AC-2, SC-13(1))
- KSI item IDs when referencing security indicators
- Line numbers for markdown guidance references
Communication Style
- Be precise and technical
- Provide specific references, not general statements
- When uncertain, indicate confidence level
- Offer follow-up questions to clarify requirements
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 · 42 lines · 18 tokens per session scan A f6fc97e976fc
compliance-analyst is an agent published in the GitHub repository hackIDLE/fedramp-docs-mcp (18 stars, last pushed 4mo ago), licensed MIT. It adds 18 tokens to every session and 282 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-08-30.
Other agents, from other repositories
pipeline-architect
Design end-to-end compliance pipelines with Compliance Trestle. Assess existing workspace artifacts. Recommend repository topology (single repo or multi-repo). Design CI/CD pipelines for validation and assembly. Plan component definition strategy (two-phase authoring, Service and Validation types). Walk through the…
poam-manager
Manage Plan of Action and Milestones (POA&M) lifecycle. Create POA&M items from assessment findings. Track remediation progress. Manage milestones. Make status reports. Use when users need to create, update, or track POA&M items, manage remediation workflows, or review POA&M status. Create a POA&M from my assessment…
assessment-reviewer
Review OSCAL assessment plans and assessment results for completeness, correctness, and alignment with the SSP. Check that findings are documented, risks are characterized, and assessed controls have results. Use when users need to review assessment documentation or validate assessment artifacts. Review my assessment…
compliance-reviewer
Review an OSCAL compliance workspace for completeness and gaps. Analyze controls for missing implementation responses, incomplete parameters, validation errors, and documentation gaps. Use when users want to review their compliance documentation quality or find gaps. Review my compliance workspace for gaps What…
control-mapper
Map and trace controls across the full OSCAL compliance lifecycle: catalogs, profiles, component definitions, SSPs, assessment plans, assessment results, and POA&M. Identify control coverage, inheritance chains, assessment results, and remediation status across models. Use when users need to understand control…
governance-enforcer
Interactive assistant for setting up and enforcing document governance in a trestle workspace. Set up governance templates. Validate documents against them. Identify violations. Help fix non-compliant documents. Use when users need help with document governance, template enforcement, or fixing governance validation…