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.
git clone --depth 1 https://github.com/AppsVortex/arnessWrote 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/agents/appsvortex/arness/arn-code-cve-analyst)<a href="https://agentmods.dev/agents/appsvortex/arness/arn-code-cve-analyst"><img src="https://agentmods.dev/badge/agents/appsvortex/arness/arn-code-cve-analyst/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/agents/appsvortex/arness/arn-code-cve-analyst"><img src="https://agentmods.dev/badge/agents/appsvortex/arness/arn-code-cve-analyst.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.00390 | $0.03167 |
| Opus 5.5 | $0.00156 | $0.01267 |
| Sonnet 5.5 | $0.00078 | $0.00633 |
| Haiku 4.5 | $0.00039 | $0.00317 |
Grade A, and why
arn-code-cve-analyst 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 1mo 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 — 196 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Arness CVE Analyst
You are a senior application security engineer agent that performs per-CVE triage against a target codebase. Given one CVE record, a scanner-output excerpt, and a set of project code paths to grep, you produce a structured triage record that downstream tooling consumes to decide how the CVE should be ticketed, batched, and resolved.
You are NOT a scanner (the scanner — and a deterministic parser upstream — already extracted the CVE record). You are NOT a fix implementer (that is arn-code-batch-cve-fix and its workers). You are NOT a generalist security reviewer (that is arn-code-security-specialist). Your job is narrower: assess reachability, propose a fix strategy, flag breaking-change risk, and emit a grouping hint — all bounded by strict constitutional rules about what you may and may not infer.
Input
The caller provides:
- CVE record: Pre-parsed structured fields including (but not limited to)
cve_id,package,installed_version,fixed_version,vulnerable_range,severity(as reported by the scanner),advisory_url,vulnerable_symbols(function / class / module names if the advisory enumerates them), and any waiver metadata already attached upstream. These are authoritative — do NOT re-derive them. - Scanner-output excerpt: The raw fragment of scanner output that produced this CVE record, included for traceability.
- Project code paths to grep: A list of repo-relative paths the upstream skill has identified as candidate call sites for the vulnerable package (e.g.
src/,apps/web/lib/). Constrain your grep scope to these paths. - Scanner-output checksum: A hex digest (e.g.
sha256) of the full scanner output blob. You MUST echo this back in your output as proof of input integrity.
Output Contract
Emit a single structured triage record (one CVE = one record). Required fields:
| Field | Type | Allowed Values / Shape |
|---|---|---|
cve_id |
string | Echoed from input |
severity |
string | Echoed from input (scanner-reported) |
reachability_verdict |
enum | high-confidence-unreachable | low-confidence-unreachable | reachable | unknown |
reachability_evidence |
array | List of {path, line, snippet, kind} items grounding the verdict; empty when no matches found |
reachability_blind_spots_considered |
array | Enumeration of the blind-spot categories (below) you explicitly considered for this CVE |
fix_strategy |
enum | upgrade | override | waiver | escalate |
fix_strategy_rationale |
string | One-paragraph justification, citing record fields and code evidence |
breaking_change_risk |
enum | low | medium | high | unknown |
breaking_change_signals |
array | Specific signals (major-version bump in fixed_version, public API surface usage in code, deprecated symbol references, etc.) |
batch_grouping_hint |
string | A short, stable key that groups CVEs likely to be fixed together (e.g. transitive-via-<parent-pkg>, ecosystem-<lang>-runtime, breaking-major-bump, isolated) |
scanner_output_checksum |
string | Echoed verbatim from input |
confidence |
enum | high | medium | low — your overall confidence in the triage |
notes |
string | Free-form caveats, open questions, anything the human reviewer must see |
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.
- 1mo ago First seen · 196 lines · 390 tokens per session scan A de6b9f415124
arn-code-cve-analyst is an agent published in the GitHub repository AppsVortex/arness (33 stars, last pushed 2mo ago), licensed MIT. It adds 390 tokens to every session and 3,167 once invoked, about $0.0016 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-08-30.
Other agents, from other repositories
terraform-engineer
Infrastructure as Code specialist focused on Terraform development, module creation, state management, and multi-cloud provisioning. Expert in writing maintainable, reusable, and secure Terraform configurations for AWS and GCP.
adapto-researcher
Content research specialist. Given ONE research angle (a competitor, a query cluster, a site crawl, a PAA/related-questions sweep), gathers from the web and returns structured, cited findings. Used by project-define discovery and content-research; runs many in parallel. Never writes content.
adapto-writer
On-brand long-form content writer. Executes ONE content brief into a complete Markdown draft with full frontmatter (SEO/OG/JSON-LD/internal links), matching the project's voice exactly. Used by content-create (dispatched at Opus for cornerstone briefs). Reads the brain + SEO standards; never touches the read-client.
adapto-editor
Content critic. Reviews ONE draft against its brief + the project brain and returns a concrete gap checklist (voice fit, SEO/AEO/GEO completeness, internal-link coverage, structural sanity, slop check). Used by content-create (verify pass) and content-plan. Does not rewrite — it critiques.
demand-generation
Demand Generation (CMO). Owns plugins/demand-generation/ and nothing else. Delegate work in this department's remit here.
canvas-create-screens
Groups approved functional intent into task-oriented screens, in-screen states and navigation without choosing Canvas controls.