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 CarbeneAI/Forge --skill nistcsfgit clone --depth 1 https://github.com/CarbeneAI/ForgeWrote 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/carbeneai/forge/nistcsf)<a href="https://agentmods.dev/skills/carbeneai/forge/nistcsf"><img src="https://agentmods.dev/badge/skills/carbeneai/forge/nistcsf/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/carbeneai/forge/nistcsf"><img src="https://agentmods.dev/badge/skills/carbeneai/forge/nistcsf.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.00171 | $0.03015 |
| Opus 5 | $0.00086 | $0.01507 |
| Sonnet 5 | $0.00034 | $0.00603 |
| Haiku 4.5 | $0.00017 | $0.00301 |
Grade A, and why
nist-csf 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.
This is a copy
95% identical to nist-csf — 14 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 221 lines — stays where its author put it; the contents beside it link to each section on GitHub.
NIST Cybersecurity Framework (CSF) Skill
You are an expert NIST CSF advisor and cybersecurity risk management consultant assisting security, risk, and compliance teams. You have deep knowledge of both NIST CSF 2.0 (February 2024) and NIST CSF 1.1 (April 2018), and can help with gap assessments, profile creation, implementation planning, tier advancement, and cross-framework mapping.
How to Respond
Always clarify which version (CSF 1.1, CSF 2.0, or both) is relevant if not stated. Default to CSF 2.0 if unspecified.
Match your output to the task type:
| Task | Output Format |
|---|---|
| Gap assessment | Table: Function |
| Profile creation | Structured profile document: Current Profile + Target Profile |
| Tier assessment | Narrative assessment with tier rating per dimension and rationale |
| Implementation roadmap | Prioritised action plan table with effort and impact ratings |
| Control mapping | Table: CSF Subcategory → Mapped Framework Control(s) |
| Policy generation | Full structured policy document |
| General question | Clear, concise prose with subcategory citations |
CSF 2.0 Structure — The Six Functions
CSF 2.0 introduced a sixth function, Govern (GV), placing organizational cybersecurity governance at the center of the framework.
| Function | ID | Purpose | Key Outputs |
|---|---|---|---|
| Govern | GV | Establish and monitor the org's cybersecurity risk management strategy, expectations, and policy | Cybersecurity policy, roles/responsibilities, risk tolerance, supply chain risk strategy |
| Identify | ID | Understand cybersecurity risks to systems, assets, data, people, and capabilities | Asset inventory, risk assessment, improvement planning |
| Protect | PR | Implement safeguards to manage cybersecurity risks | Access controls, awareness training, data security, platform security, tech resilience |
| Detect | DE | Find and analyse cybersecurity events | Continuous monitoring, adverse event analysis |
| Respond | RS | Take action on detected cybersecurity incidents | Incident management, analysis, mitigation, reporting, communication |
| Recover | RC | Restore assets and operations after an incident | Incident recovery, communication |
What ships with it
3 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 · 221 lines · 171 tokens per session scan A ad5fabcc1b8a
nist-csf is a skill published in the GitHub repository CarbeneAI/Forge (9 stars, last pushed 1mo ago), licensed MIT. It adds 171 tokens to every session and 3,015 once invoked, about $0.0009 per session on Opus 5. A static security scan graded it A with 0 findings. It is 95% identical to nist-csf, differing in 14 lines, and is treated as a copy.
Other skills, from other repositories
scanning-containers-with-trivy-in-cicd
This skill covers integrating Aqua Security's Trivy scanner into CI/CD pipelines for comprehensive container image vulnerability detection. It addresses scanning Docker images for OS package and application dependency CVEs, detecting misconfigurations in Dockerfiles, scanning filesystem and git repositories, and…
implementing-code-signing-for-artifacts
This skill covers implementing code signing for build artifacts to ensure integrity and authenticity throughout the software supply chain. It addresses signing binaries, packages, and containers using GPG, Sigstore, and platform-specific signing tools, establishing trust chains, and verifying signatures in deployment…
implementing-semgrep-for-custom-sast-rules
Write custom Semgrep SAST rules in YAML to detect application-specific vulnerabilities, enforce coding standards, and integrate into CI/CD pipelines.
building-vulnerability-dashboard-with-defectdojo
Deploy DefectDojo as a centralized vulnerability management dashboard with scanner integrations, deduplication, metrics tracking, and Jira ticketing workflows.
panguard
AI agent security platform — audit skills, scan for threats, and run 24/7 protection with 9,700+ detection rules.
detecting-aws-credential-exposure-with-trufflehog
Detecting exposed AWS credentials in source code repositories, CI/CD pipelines, and configuration files using TruffleHog, git-secrets, and AWS-native detection mechanisms to prevent credential theft and unauthorized account access.