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 skills add adhocteam/activate-framework --skill nist-control-mappinggit clone --depth 1 https://github.com/adhocteam/activate-frameworkWrote 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/adhocteam/activate-framework/nist-control-mapping)<a href="https://agentmods.dev/skills/adhocteam/activate-framework/nist-control-mapping"><img src="https://agentmods.dev/badge/skills/adhocteam/activate-framework/nist-control-mapping/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/skills/adhocteam/activate-framework/nist-control-mapping"><img src="https://agentmods.dev/badge/skills/adhocteam/activate-framework/nist-control-mapping.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.00058 | $0.02457 |
| Opus 5.5 | $0.00023 | $0.00983 |
| Sonnet 5.5 | $0.00012 | $0.00491 |
| Haiku 4.5 | $0.00006 | $0.00246 |
Grade A, and why
nist-control-mapping 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 6d 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.
How it starts
The opening of the file, as written. The whole thing — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
Create consistent, reviewable links between technical implementation and specific NIST SP 800-53 controls. Aggregate those links into traceability artifacts that can inform an SSP or other ATO documentation. Keep the workflow usable across programming languages, Terraform and other infrastructure-as-code, configuration files, and documentation.
Inputs
- Scope: Files, directories, changes, or system boundary to annotate or roll up.
- Control baseline: Applicable NIST SP 800-53 revision, impact baseline, tailoring, and overlays, if known. The organization must supply these decisions.
- Output artifacts: Requested outputs, such as a traceability matrix, OSCAL Component Definition, implementation statements, or evidence register.
Outputs
- Annotations: Inline source annotations or sidecar mappings with control references and implementation context.
- Control matrix: Control-to-artifact mappings with coverage statements and evidence references.
- Evidence register: Inventory of supporting implementation artifacts and validation status.
- Limitations: Unconfirmed applicability, missing evidence, and review required before ATO use.
Preconditions
- The user identifies the system or artifact scope.
- Use the organization's specified NIST catalog revision, impact baseline, tailoring decisions, and overlays when available.
- If the control baseline or applicability is unknown, ask for it. You may produce a clearly labeled provisional inventory, but do not select a baseline or claim applicability on the organization's behalf.
Annotation Format
Use the same field names in comments across file types. Adapt the comment prefix to the language (#, //, /* */, or the file format's supported comment syntax) and place the block immediately before the smallest meaningful code or configuration section. Keep the control citation canonical, including the catalog revision and enhancement notation.
# compliance-control: NIST SP 800-53 Rev. 5 AC-6(1)
# compliance-coverage: partial
# compliance-rationale: The deployment role is limited to the actions required by this service.
# compliance-evidence: tests/security/test_deployment_role.py::test_role_has_scoped_actions
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 6d ago First seen · 124 lines · 58 tokens per session scan A 19efca6ecbe9
nist-control-mapping is a skill published in the GitHub repository adhocteam/activate-framework (6 stars, last pushed 6d ago), licensed MIT. It adds 58 tokens to every session and 2,457 once invoked, about $0.0002 per session on Opus 5.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-10-29.
Other skills, from other repositories
fto-triage
Freedom-to-operate triage — a structured first look at potentially blocking patents, not an FTO opinion. Use when a product, process, or feature is being evaluated for blocking patents, when asked whether anything stops a launch, or to build a claim-chart first pass against the most plausible patents before patent…
legal-hold
Issue, refresh, release, or report on legal holds — drafts the hold notice as .docx, updates legalhold fields in log.yaml, and calendars the next refresh. Use when the user says "issue a hold", "refresh hold", "release hold", or asks for a portfolio-wide hold status report.
specification-writing
A workflow for writing complete patent specifications from patent claims and an invention disclosure. It adapts the document to a chosen jurisdiction, such as the US, Europe, or China.
terms-of-service
Draft terms of service and a companion privacy notice matched to the product's form and feature modules, not legal advice, delivered as a Word document.
x-scorecard
OpenSSF Scorecard for assessing open source project security. Check security best practices and compliance. Dependency: This is an x-cmd module. Install x-cmd first (see x-cmd skill for installation options). see x-cmd skill for installation.
ai-risk-management
Apply the NIST AI Risk Management Framework (AI RMF 1.0) and adjacent guidance to AI / ML systems — model lifecycle governance, fairness and bias evaluation, robustness, transparency, accountability, third-party model risk, monitoring for drift, and AI incident response. Broader than prompt-injection (which is the…