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 UnboundCompute/security-agent-skills --skill adjudicating-dependency-cve-reachabilitygit clone --depth 1 https://github.com/UnboundCompute/security-agent-skillsWrote 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/unboundcompute/security-agent-skills/adjudicating-dependency-cve-reachability)<a href="https://agentmods.dev/skills/unboundcompute/security-agent-skills/adjudicating-dependency-cve-reachability"><img src="https://agentmods.dev/badge/skills/unboundcompute/security-agent-skills/adjudicating-dependency-cve-reachability/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/unboundcompute/security-agent-skills/adjudicating-dependency-cve-reachability"><img src="https://agentmods.dev/badge/skills/unboundcompute/security-agent-skills/adjudicating-dependency-cve-reachability.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.00122 | $0.01538 |
| Opus 5 | $0.00061 | $0.00769 |
| Sonnet 5 | $0.00024 | $0.00308 |
| Haiku 4.5 | $0.00012 | $0.00154 |
Grade A, and why
adjudicating-dependency-cve-reachability 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 11d 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 — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Adjudicating dependency-CVE reachability: affected, or just noisy?
A scanner that lists every CVE in your dependency tree is measuring your
package.json, not your exposure. Most flagged CVEs are unreachable: you never
call the vulnerable function, or you call it in a way the bug does not trigger, or
no attacker-controlled input gets there. Adjudicating reachability turns a wall of
red into the short list that actually matters, and gives you a defensible reason
for each one you set aside.
When to use
- An SCA tool, dependency bot, or advisory flagged a CVE in a library you use.
- You are drowning in "critical" dependency alerts and need to triage by exposure.
- You must justify a "not affected" status (for an auditor, a VEX statement, a customer) with evidence, not a guess.
- You are deciding whether an urgent patch is actually urgent for you.
Scope check
Authorized source only (your own application and the dependencies it ships). If you can't name the authorization, stop.
The loop
-
Pin the vulnerable symbol. From the advisory and, crucially, the fix commit, identify the exact vulnerable function(s) or sink in the dependency and the affected version range. "The library is vulnerable" is not actionable; "
parse_untrusted()before v2.3 is vulnerable when called with X" is. Reading the patch tells you precisely what is unsafe and under what condition. -
Test call-path reachability. Does any path from your own entry points reach that vulnerable function, directly or transitively? If nothing in your code (or the code you actually invoke) calls it, you are not reachable through the static graph. Record that, but note the blind spots below before you call it clean.
-
Check the trigger preconditions. Reaching the function is not enough. The CVE usually needs a specific argument shape, a config flag enabled, a feature in use, or a size or option the safe callers never pass. Confirm whether your call sites actually satisfy the condition the fix now rejects. Many "reachable" CVEs die here because you always call the safe overload or pass the safe flag.
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.
- 11d ago First seen · 123 lines · 122 tokens per session scan A 09cfb95db903
adjudicating-dependency-cve-reachability is a skill published in the GitHub repository UnboundCompute/security-agent-skills (5 stars, last pushed 3d ago), licensed MIT. It adds 122 tokens to every session and 1,538 once invoked, about $0.0006 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-31.
Other skills, from other repositories
prodcheck-review
Review this codebase against the prodcheck pre-production checklists — security, performance, scale, integrations and post-launch readiness. Use when asked to check whether a project is ready to ship, to audit an area before launch, or to work through a specific checklist. Produces evidence with file:line citations…
integrate-arcjet-guard-genkit
Integrate Arcjet security into a Genkit JS agent using @arcjet/guard — wrap ai.defineTool, put guardMiddleware on generate({ use }) for unwrapped / MCP / filesystem tools, and read a caller-owned id from generate({ context }). Use when asked to add Arcjet to genkit, rate limit its tools, screen inbound messages, or…
integrate-arcjet-guard-langgraph
Integrate Arcjet security into a LangGraph Graph API agent using @arcjet/guard — wrap tool() / StructuredTool, wrap ToolNode for unwrapped MCP tools, and read threadid for correlation. Use when asked to add Arcjet to a LangGraph StateGraph / ToolNode agent, rate limit its tools, screen inbound messages, or block…
integrate-arcjet-guard-tanstack-ai
Integrate Arcjet security into a TanStack AI chat() app using @arcjet/guard — put guardMiddleware first on chat({ middleware }) so onBeforeToolCall gates tools, and read a caller-owned id from chat({ context }). Use when asked to add Arcjet to TanStack AI, rate limit its tools, screen inbound messages, or block prompt…
integrate-arcjet-guard-claude-managed-agents
Integrate Arcjet security into Claude Managed Agents (hosted REST+SSE, beta managed-agents-2026-04-01) using @arcjet/guard — screen user.message / initialevents before sessions.events.send, and gate custom tools on agent.customtooluse. Use when asked to add Arcjet to Claude Managed Agents, rate limit custom tools, or…
linear-claude-skill
Manage Linear issues, projects, and teams.