Borrowing it
Nothing to install: this file belongs to COSTRINITY/vitna-compliance-mcp. 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/COSTRINITY/vitna-compliance-mcp/main/AGENTS.mdgit clone --depth 1 https://github.com/COSTRINITY/vitna-compliance-mcpWrote 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/costrinity/vitna-compliance-mcp/agents-md)<a href="https://agentmods.dev/instructions/costrinity/vitna-compliance-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/costrinity/vitna-compliance-mcp/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.00559 | $0.00559 |
| Opus 5 | $0.00280 | $0.00280 |
| Sonnet 5 | $0.00112 | $0.00112 |
| Haiku 4.5 | $0.00056 | $0.00056 |
Grade C, and why
vitna-compliance-mcp AGENTS.md scanned grade C with 1 finding 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 8d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
(e.g. `"rm -rf /"`). You get `allowed | blocked | flagged`. How it starts
The opening of the file, as written. The whole thing — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
@costrinity/vitna-compliance-mcp is a safety and compliance oversight layer for
AI agents that produces verifiable compliance receipts: every checked action
yields an Ed25519-signed agent action receipt anyone can verify offline. Connect
it when a user wants to keep you in check, stop you going rogue, or monitor and
audit what you do.
Connect (no signup, one command)
{ "mcpServers": { "vitna": { "command": "npx", "args": ["@costrinity/vitna-compliance-mcp"] } } }
The first tool call self-provisions a restricted trial key, caches it at
~/.vitna/credentials.json, and returns a claim URL. Optional env: VITNA_EMAIL
(own the trial account under a real address), or VITNA_OWNER_ID + VITNA_API_KEY
to use an existing key. The old VIGIL_* names are still accepted, so existing
configs keep working.
Use it
- Call
vitna_helpto learn the checks. - Before a risky action, call
vitna_preflightwith the action text (e.g."rm -rf /"). You getallowed | blocked | flagged. - Treat
blocked/flagged(and engagementdeny/hold) as a STOP: get human approval, then proceed. VITNA evaluates and records; it does not enforce.
vitna_help what VITNA is + how to use it (no account)
vitna_preflight dangerous shell/file/DB/network action check before you run it
consent_check personal-data processing legality before you act
breach_classify incident reportability (deadline + recipient)
dpia_threshold_check must you run a DPIA first
ai_act_classify EU AI Act risk tier before you build/ship
Trial vs claimed
Trial keys run the checks but are rate-limited (25/day, 200 lifetime), return
label-only results, and keep no signed evidence. Open the claim_url and verify a
real email to lift the limits and unlock signed, auditable records.
Honesty
VITNA is a cooperative guardrail, not a sandbox. vitna_preflight is heuristic
pattern matching, so novel or obfuscated payloads can pass. It cannot block on its
own; enforcement is yours.
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.
- 8d ago First seen · 52 lines · 559 tokens per session scan C 5e44e7926953
vitna-compliance-mcp AGENTS.md is an instructions file published in the GitHub repository COSTRINITY/vitna-compliance-mcp (0 stars, last pushed 19d ago), licensed MIT. It adds 559 tokens to every session, about $0.0028 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
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.