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/hackidle/fedramp-docs-mcp/get-requirementgit 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/commands/hackidle/fedramp-docs-mcp/get-requirement)<a href="https://agentmods.dev/commands/hackidle/fedramp-docs-mcp/get-requirement"><img src="https://agentmods.dev/badge/commands/hackidle/fedramp-docs-mcp/get-requirement.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.00008 | $0.00091 |
| Opus 5 | $0.00004 | $0.00046 |
| Sonnet 5 | $0.00002 | $0.00018 |
| Haiku 4.5 | $0.00001 | $0.00009 |
Grade A, and why
get-requirement 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
Get Requirement by ID
Get FedRAMP requirement details for: "$ARGUMENTS"
Example IDs: KSI-IAM-01, FRR-MAS-01, FRD-001
Use the fedramp-docs MCP server's get_requirement_by_id tool to retrieve the full requirement details including title, statement, description, theme, impact levels, and control mappings.
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 · 12 lines · 8 tokens per session scan A 3a1e0636adfa
get-requirement is a command published in the GitHub repository hackIDLE/fedramp-docs-mcp (18 stars, last pushed 4mo ago), licensed MIT. It adds 8 tokens to every session and 91 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
Ingest Legacy SSP
Run the end-to-end legacy SSP import process: extract source material, create source traceability, bootstrap a Trestle workspace, map content, validate OSCAL, and report unmapped items.
Fetch OSCAL Baseline
Download the NIST SP 800-53 Rev 5 catalog and a FedRAMP Rev 5 baseline profile, then import both into a Compliance Trestle workspace for real-baseline SSP drafting.
KSI Coverage Report
Compare an OSCAL SSP to the FedRAMP 20x Key Security Indicators from the 2026 Consolidated Rules and report documentation coverage.
Update SSP From Evidence
Use new evidence, findings, or POA&M information to update an existing OSCAL SSP while preserving traceability.
Draft SSP From Extraction
Draft a schema-valid OSCAL SSP from extracted legacy sections, optionally importing a real FedRAMP baseline profile.
Validate OSCAL Package
Validate an OSCAL file or Trestle package with available validators and write a validation summary.