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 skills/hackidle/fedramp-docs-mcp/frmr-analysisnpx skills add hackIDLE/fedramp-docs-mcp --skill frmr-analysisgit 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/skills/hackidle/fedramp-docs-mcp/frmr-analysis)<a href="https://agentmods.dev/skills/hackidle/fedramp-docs-mcp/frmr-analysis"><img src="https://agentmods.dev/badge/skills/hackidle/fedramp-docs-mcp/frmr-analysis.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.1 | $0.00051 | $0.00235 |
| Opus 5 | $0.00026 | $0.00118 |
| Sonnet 5 | $0.00010 | $0.00047 |
| Haiku 4.5 | $0.00005 | $0.00023 |
Grade A, and why
frmr-analysis 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.
What it actually says
When analyzing FRMR documents:
- Identify the document type (KSI, MAS, VDR, SCN, FRD, ADS, CCM, FSI, ICP, PVA, SCG, UCM)
- Extract control mappings between NIST SP 800-53 and FedRAMP requirements
- Identify Key Security Indicators (KSI) when relevant
- Highlight significant changes between document versions
- Map controls to specific compliance requirements
- Provide citations to specific FRMR sections and item IDs
Use the fedramp-docs MCP server tools:
list_frmr_documentsto enumerate available documentsget_frmr_documentto retrieve full document contentlist_ksito filter KSI requirementslist_controlsto get control mappingsdiff_frmrto compare document versions
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 · 21 lines · 51 tokens per session scan A 627cbf0440f9
frmr-analysis is a skill published in the GitHub repository hackIDLE/fedramp-docs-mcp (18 stars, last pushed 4mo ago), licensed MIT. It adds 51 tokens to every session and 235 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-30.
Other skills, from other repositories
trestle-compliance-pipeline
Use this skill for end-to-end compliance pipelines with Compliance Trestle. Topics include GRC personas, artifact ownership, multi-repository coordination, two-phase component definition authoring, CI/CD pipeline integration, and the Compliance-to-Policy (C2P) bridge. Use it for compliance pipelines, personas…
trestle-control-implementation
Use this skill to write control implementation responses, rules, parameters, and component-level responses. Use it for inheritance and leveraged SSPs in Compliance Trestle. Use it for control responses, implementation status, rules, parameters, component definitions, SSP implementation details, or compliance…
trestle-task-system
Use this skill for the Compliance Trestle task system for data conversion and transformation. Use it for CSV import, XLSX import, XCCDF results, Tanium results, and CIS benchmarks. Use it for config.ini task configuration, trestle tasks, or conversion of scan results to assessment results.
trestle-validation
Use this skill for Compliance Trestle validation, common errors, and troubleshooting. Use it for validation errors, trestle validate failures, and OSCAL schema checks. Use it to fix compliance document issues or to troubleshoot trestle problems.
trestle-authoring-workflow
Use this skill for the Compliance Trestle authoring workflow. The workflow is the generate-edit-assemble cycle that converts OSCAL documents to markdown and back. Use it for authoring catalogs, profiles, SSPs, or component definitions. Use it for editing control markdown, YAML headers, or the roundtrip workflow…
trestle-governance
Use this skill for the Compliance Trestle document governance system. The system checks document structure and YAML headers. Use it for document governance, header checks, template validation, governed headings, and governed folders. Use it for trestle author docs, headers, folders, template setup, or CI/CD document…