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/saolalab/clawforce/vulnerability-managementnpx skills add saolalab/clawforce --skill vulnerability-managementgit clone --depth 1 https://github.com/saolalab/clawforceWrote 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/saolalab/clawforce/vulnerability-management)<a href="https://agentmods.dev/skills/saolalab/clawforce/vulnerability-management"><img src="https://agentmods.dev/badge/skills/saolalab/clawforce/vulnerability-management.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.00023 | $0.00722 |
| Opus 5 | $0.00012 | $0.00361 |
| Sonnet 5 | $0.00005 | $0.00144 |
| Haiku 4.5 | $0.00002 | $0.00072 |
Grade A, and why
vulnerability-management 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.
How it starts
The opening of the file, as written. The whole thing — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Vulnerability Management
Vulnerability Lifecycle
Discovery → Assessment → Prioritization → Remediation → Verification → Closure
CVSS Scoring Guide
Severity Levels
| CVSS Score | Severity | Remediation SLA |
|---|---|---|
| 9.0 - 10.0 | Critical | 24-72 hours |
| 7.0 - 8.9 | High | 7 days |
| 4.0 - 6.9 | Medium | 30 days |
| 0.1 - 3.9 | Low | 90 days |
Key CVSS Factors
- Attack Vector — Network, Adjacent, Local, Physical
- Attack Complexity — Low, High
- Privileges Required — None, Low, High
- User Interaction — None, Required
- Scope — Unchanged, Changed
- Impact — Confidentiality, Integrity, Availability
Vulnerability Report Template
## Vulnerability Report
### Summary
- **ID**: [CVE-XXXX-XXXXX or internal ID]
- **Title**: [Brief description]
- **Severity**: [Critical/High/Medium/Low]
- **CVSS**: [Score and vector]
- **Status**: [Open/In Progress/Remediated/Verified]
### Affected Assets
- [List affected systems, applications, versions]
### Technical Details
- **Vulnerability Type**: [SQLi, XSS, RCE, etc.]
- **Root Cause**: [Technical explanation]
- **Proof of Concept**: [Steps to reproduce]
### Impact Analysis
- **Confidentiality**: [Impact description]
- **Integrity**: [Impact description]
- **Availability**: [Impact description]
- **Business Impact**: [Business context]
### Remediation
- **Recommended Fix**: [Technical solution]
- **Workaround**: [Temporary mitigation if available]
- **Owner**: [Person responsible]
- **Due Date**: [Based on severity SLA]
### References
- [CVE link, vendor advisory, etc.]
Scanning Cadence
| Scan Type | Frequency | Scope |
|---|---|---|
| External | Weekly | Internet-facing assets |
| Internal | Bi-weekly | Internal network |
| Container | On build | All container images |
| Dependencies | On commit | All code repos |
| Web App | Monthly | Production apps |
Prioritization Matrix
Consider these factors beyond CVSS:
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 · 98 lines · 23 tokens per session scan A 7d473555a376
vulnerability-management is a skill published in the GitHub repository saolalab/clawforce (38 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 23 tokens to every session and 722 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 skills, from other repositories
nemoclaw-contributor-implement-issue
Implement an accepted NemoClaw GitHub issue in the current checkout. Use when a user asks to pick up an issue for implementation, implement or fix a named issue, or add the issue's tests. Confirm accepted scope, deliver the smallest independently valuable capability slice, and record validation and remaining gates…
tmux
Remote-control tmux sessions for interactive CLIs by sending keystrokes and scraping pane output.
summarize
Summarize or extract text/transcripts from URLs, podcasts, and local files (great fallback for “transcribe this YouTube/video”).
add-matrix
Add Matrix channel integration via Chat SDK. Works with any Matrix homeserver.
add-resend
Add Resend (email) channel integration via Chat SDK.
add-macos-statusbar
Add a macOS menu bar status indicator for NanoClaw. Shows a bolt icon with a green/red dot indicating whether NanoClaw is running, with Start, Stop, and Restart controls. macOS only.