Vulnerability-Scanning AGENTS.md

Vulnerability-Scanning AGENTS.md is an instructions file for Codex, OpenCode from TheSethRose/Vulnerability-Scanning. It costs 978 tokens per session, scanned A, original, MIT.

Repository instructions for a local-first vulnerability scanner, which checks code workspaces and packages for known security problems, plus its Python command-line tool. Normal scans only read data; automatic fixes require explicit permission.

In plain words
What is it for?
Use them to set up or validate scanner tools, scan a workspace, inspect package vulnerabilities, plan remediation, render reports, and run tests.
Why use it?
They explain the safe operating rules, available commands, configuration limits, and tests, helping agents scan without accidentally changing the project.

Instructions file for CodexOpenCode

Install

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.

agentmods
npx agentmods add instructions/thesethrose/vulnerability-scanning/agents-md
Clone the repo
git clone --depth 1 https://github.com/TheSethRose/Vulnerability-Scanning

Made for: Codex, OpenCode.

Wrote 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.

agentmods badge for Vulnerability-Scanning AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/thesethrose/vulnerability-scanning/agents-md.svg)](https://agentmods.dev/instructions/thesethrose/vulnerability-scanning/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/thesethrose/vulnerability-scanning/agents-md"><img src="https://agentmods.dev/badge/instructions/thesethrose/vulnerability-scanning/agents-md.svg" alt="Measured on agentmods" height="20"></a>
Per session 978 This file is loaded in full into every session.
When invoked 978 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00978 $0.00978
Opus 5 $0.00489 $0.00489
Sonnet 5 $0.00196 $0.00196
Haiku 4.5 $0.00098 $0.00098

Measured 4d ago against content hash b1d1b098eace, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

Vulnerability-Scanning AGENTS.md 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.

AGENTS.md · 51 lines

How it starts

The opening of the file, as written. The whole thing — 51 lines — stays where its author put it; the contents beside it link to each section on GitHub.

AGENTS.md

Project Overview

  • This repo packages a local-first vulnerability-scanning skill plus a Python CLI for scanning local workspaces, package intake, scanner validation, and report rendering.
  • Normal scan mode is read-only. Remediation must remain opt-in through --auto-remediate or config that explicitly enables it.
  • Optional package-intake OSV lookups are disabled in the starter config unless package_intake.osv_api_enabled is changed.

Setup Commands

  • There is no root package manager manifest. Do not invent npm, bun, pnpm, or build commands for this repo.
  • Python entrypoint: python3 scripts/vuln-scan.py ...
  • Validate starter config: ./scripts/validate-config.sh templates/config-starter.yaml
  • Validate scanner tools: python3 scripts/vuln-scan.py validate-tools --config templates/config-starter.yaml --format text
  • Deep tool smoke check: python3 scripts/vuln-scan.py validate-tools --config templates/config-starter.yaml --format text --deep

Test and Validation Commands

  • Run all tests: python3 -m unittest discover -s tests -p 'test_*.py'
  • Run one test file: python3 -m unittest tests.test_cli
  • Plan without running scanners: python3 scripts/vuln-scan.py plan --config templates/config-starter.yaml --root "$PWD" --scan-mode full --format text
  • List engines: python3 scripts/vuln-scan.py list-engines --format text
  • Render a saved report: python3 scripts/vuln-scan.py render-report /tmp/vuln-summary.json --format text

Code Style

  • Keep source and test files under 500 lines by splitting by domain, command, parser family, or test area.
  • Exceptions are allowed for generated artifacts, lockfiles, vendored code, or intentionally monolithic reference documents when splitting would reduce clarity.
  • Keep CLI parsing in scripts/vulnscan/cli/; engine orchestration in scripts/vulnscan/orchestration.py; scanner runners in their domain modules; parser normalization in scripts/vulnscan/parsers/.
  • Engine runners should return (findings_by_target, stats) and record missing binaries, timeouts, commands, unsupported targets, and parser failures as setup debt instead of treating them as clean coverage.
  • Parser behavior must stay covered by fixtures or fake-binary integration tests before enabling new parser paths by default.

Read the full file on GitHub · 51 lines

Changes

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.

  1. 4d ago First seen · 51 lines · 978 tokens per session scan A b1d1b098eace

Subscribe to this mod's changes

Vulnerability-Scanning AGENTS.md is an instructions file published in the GitHub repository TheSethRose/Vulnerability-Scanning (5 stars, last pushed 3mo ago), licensed MIT. It adds 978 tokens to every session, about $0.0049 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.