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 joao-aires/agent-skills-public --skill vulnerability-managementgit clone --depth 1 https://github.com/joao-aires/agent-skills-publicWrote 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/joao-aires/agent-skills-public/vulnerability-management)<a href="https://agentmods.dev/skills/joao-aires/agent-skills-public/vulnerability-management"><img src="https://agentmods.dev/badge/skills/joao-aires/agent-skills-public/vulnerability-management/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/joao-aires/agent-skills-public/vulnerability-management"><img src="https://agentmods.dev/badge/skills/joao-aires/agent-skills-public/vulnerability-management.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.00033 | $0.00967 |
| Opus 5.5 | $0.00013 | $0.00387 |
| Sonnet 5.5 | $0.00007 | $0.00193 |
| Haiku 4.5 | $0.00003 | $0.00097 |
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 yesterday.
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 — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Vulnerability management
Read composition guidance for optional expertise, fallback and scope.
Connect each finding to the component and version the application actually resolves, the artifact that contains it, and the environments running that artifact. Establish whether the reported condition applies and how it is exposed before selecting the priority and fix.
Track the remedy through that same chain. A source update can resolve the development dependency while an older image or supported release still contains the vulnerable component. Closure needs evidence for every affected target or an explicit accountable disposition for the remaining exposure.
Execution modes and standards
- In interactive work, explain prioritized risks and resolve remediation tradeoffs.
- For setup establish asset/software inventory, scanner coverage, ownership, patch policy and automation.
- During feature work assess introduced dependencies, base images, runtimes and infrastructure.
- In recurring runs reconcile current findings with previous records, prioritize exploitation/exposure, prepare compatible patches, and retain original deadlines.
Execute rollout/status/risk mutations only within the job's explicit authority; never auto-accept risk to clear a dashboard.
Consult references/patch-management.md for NIST-grounded preventive patch management and scanner-agnostic verification for deeper implementation details when needed.
Scope and policy
Discover application/infrastructure ownership, deployed versions, scanners, dependency update automation, supported release lines, and applicable remediation policy. Obtain severity/exposure deadlines and exception authority locally; do not import another project's deadline table.
Use available scanner/API/CLI exports. Record data timestamp, scanned revision, and pagination/coverage limits. A stale development scan does not establish production risk.
Triage
- Aggregate relevant SCA, code, container, infrastructure, and manually reported findings. Keep routine version updates distinguishable from vulnerability fixes.
- Deduplicate the same component/version/vulnerability while preserving every affected service and deployed environment.
- Assign an accountable owner. Record first discovery, exposure, severity, affected deployed artifacts, deadline source, fix availability, and evidence.
- Prioritize using applicable policy plus exploitation evidence (including CISA KEV), reachability, exposure, privileges, compensating controls and business impact. Severity alone is insufficient. Low visibility or a failed scan is not evidence of no risk.
- Preserve the original deadline when work rolls into the next cycle or ticket.
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.
- yesterday Changed · +12 lines 3d01d1a7cab3
- 2d ago Changed · +2 lines 7b5f249c7f7c
- 7d ago First seen · 65 lines · 33 tokens per session scan A 409e6bfbd9ba
vulnerability-management is a skill published in the GitHub repository joao-aires/agent-skills-public (2 stars, last pushed yesterday), licensed MIT. It adds 33 tokens to every session and 967 once invoked, about $0.0001 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-15.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…