Borrowing it
Nothing to install: this file belongs to HuTa0kj/vetix. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/HuTa0kj/vetix/main/AGENTS.mdgit clone --depth 1 https://github.com/HuTa0kj/vetixWrote 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/instructions/huta0kj/vetix/agents-md)<a href="https://agentmods.dev/instructions/huta0kj/vetix/agents-md"><img src="https://agentmods.dev/badge/instructions/huta0kj/vetix/agents-md.svg" alt="Measured on agentmods" 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.00920 | $0.00920 |
| Opus 5 | $0.00460 | $0.00460 |
| Sonnet 5 | $0.00184 | $0.00184 |
| Haiku 4.5 | $0.00092 | $0.00092 |
Grade A, and why
vetix 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 6d 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Vetix — Project Map
Vetix is an LLM-agent-based scanner for SKILL directories. It pairs deterministic plugin rules with an LLM behavioral analyst so both obvious IOCs and subtle, obfuscated attack chains get caught in one pass.
End-user docs live in README.md / README_CN.md. This file is a map for navigating the codebase.
Repository Layout
vetix/
cli.py Typer entry point — `vetix scan`
agent.py Orchestrator — builds the workflow, runs it
cache.py Loads a previously saved report.json (cache-hit fast path)
config.py YAML config loader (cached, sets LangSmith env)
model.py Role → ChatOpenAI factory (`get_llm`)
plugin.py Plugin ABC, Issue/Severity types, plugin loader
audit/
graph.py LangGraph workflow definition
state.py Shared state + finding Pydantic models
nodes/ Workflow nodes (one file per stage)
plugins/ Deterministic scanners (auto-discovered)
middleware/ Agent middleware (e.g. tool filtering)
prompts/ System prompts for each LLM stage
skills/ Helper skills mounted into the analyst agent
utils/ Logging, file classification, helpers
config.yaml Runtime config (gitignored) — see example.config.yaml
example.config.yaml Config template
Workflow
gather_base_info → plugins_check → plugins_findings_verify → behavioral_analysis → report
State is shared via SkillSafeAuditState (Pydantic). Each node returns a dict that merges into state; there are no conditional edges.
Scans short-circuit on a cache hit: before the workflow is built, agent.py compares directory_hash[:16] (computed by gather_base_info) against the subdirectories of the output directory and, if <output-dir>/<hash[:16]>/report.json exists, loads it back into state and renders it instead of running the pipeline. --force bypasses the cache.
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.
- 6d ago First seen · 70 lines · 920 tokens per session scan A 455eab52e67f
vetix AGENTS.md is an instructions file published in the GitHub repository HuTa0kj/vetix (61 stars, last pushed 1mo ago), licensed MIT. It adds 920 tokens to every session, about $0.0046 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-30.
Other instructions, from other repositories
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.