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 instructions/raccioly/websec-validator/agents-mdgit clone --depth 1 https://github.com/raccioly/websec-validatorWhat 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.01080 | $0.01080 |
| Opus 5 | $0.00540 | $0.00540 |
| Sonnet 5 | $0.00216 | $0.00216 |
| Haiku 4.5 | $0.00108 | $0.00108 |
Grade A, and why
websec-validator 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 2d 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 — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Instructions
This project follows Canonical-Driven Development (CDD).
Read canonical docs before making changes. Log drift when deviating.
Project Overview
websec-validator is a local-first security-recon CLI that briefs an AI coding agent. It maps a repo's
attack surface, de-duplicates the static scanners it finds, stages a tailored probe library, and emits
an AGENT-BRIEFING.md — code in, artifacts out; no LLM, no server, no running app for the core
pass. Pure-Python, stdlib only, zero runtime dependencies; it shells out to external scanners
(Trivy/Gitleaks/Semgrep/Checkov/Prowler) and OWASP Noir when present. The package lives in
src/websec_validator/; the architecture is in docs-canonical/ARCHITECTURE.md.
Project Documentation (CDD)
- Canonical docs (design intent, review-gated):
docs-canonical/—ARCHITECTURE.md,SECURITY.md,TEST-SPEC.md,ENVIRONMENT.md - Long-form methodology (the why behind every check):
docs/METHODOLOGY.md - Proof protocol:
corpus/PROOF-PROTOCOL.md - Drift tracking:
DRIFT-LOG.md· Change tracking:CHANGELOG.md - Spec Kit constitution:
.specify/memory/constitution.md
Build & Dev Commands
| Command | Purpose |
|---|---|
pipx install --editable . |
Install the CLI from source (or pip install -e . in a 3.11+ venv) |
python3 -m unittest discover -s tests |
Run the suite (285 tests, stdlib only, no network) |
websec run ./target |
Full pipeline → FACTS.json + AGENT-BRIEFING.md + probes/ |
websec doctor ./target |
Show which optional scanners are installed |
websec proof |
Score recon coverage vs the vuln-app corpus (needs network on first clone) |
docguard guard |
Validate documentation against the code (CDD) |
DocGuard — Documentation Enforcement
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.
- 2d ago First seen · 83 lines · 1,080 tokens per session scan A f7df4de8e91a
websec-validator AGENTS.md is an instructions file published in the GitHub repository raccioly/websec-validator (2 stars, last pushed 2d ago), licensed MIT. It adds 1,080 tokens to every session, about $0.0054 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 instructions, from other repositories
Cybermes AGENTS.md
Instructions for Zyrexnn/Cybermes, covering 🛡️ cybermes master operational directives (agents.md), 1. 🎯 persona & core mission, 2. ⚡ core operational principles, 3. 📁 strict target-scoped workspace & deliverables and mandatory rules for file creation.
draugr CLAUDE.md
Instructions for draugr-dev/draugr, covering working on draugr, what draugr is, layout, before you open a pr and design principles.
secure-sdlc-agents CLAUDE.md
Instructions for Kaademos/secure-sdlc-agents, covering secure sdlc — multi-agent orchestration, agent roster, lifecycle phases & handoffs, 1. plan and 2. design.
numasec AGENTS.md
AGENTS.md instructions for FrancescoStabile/numasec, covering numasec agent guide, operating rules, branches, product direction and product messaging direction.
xche-ai-app-security-pack AGENTS.md
Instructions for xChechi/xche-ai-app-security-pack, a project described as: Free security guardrails for apps built with AI coding tools (Claude Code, Cursor, Lovable, Bolt). Drop-in rules + OWASP/LLM/MCP policy + secret-scanning hooks & CI gate.
xche-ai-app-security-pack CLAUDE.md
Instructions for xChechi/xche-ai-app-security-pack, a project described as: Free security guardrails for apps built with AI coding tools (Claude Code, Cursor, Lovable, Bolt). Drop-in rules + OWASP/LLM/MCP policy + secret-scanning hooks & CI gate.