vitna-compliance-mcp: Instructions file for Codex

AGENTS.md

vitna-compliance-mcp AGENTS.md is an instructions file for Codex, OpenCode from COSTRINITY/vitna-compliance-mcp. It costs 716 tokens per session, scanned C, original, MIT.

A set of instructions for connecting an AI agent to Vitna, a compliance and oversight service that checks planned actions and creates signed records of those checks.

In plain words
What is it for?
Use it to configure Vitna, run pre-action checks, and understand how to handle allowed, flagged, or blocked results.
Why use it?
It gives agents a documented way to pause on risky actions and request human approval, while keeping verifiable evidence of what was checked.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md. Also seen: mentions AGENTS.md.

This is COSTRINITY/vitna-compliance-mcp's own configuration. It tells Codex and OpenCode how to work on vitna-compliance-mcp itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything vitna-compliance-mcp configures →

Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/COSTRINITY/vitna-compliance-mcp/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/COSTRINITY/vitna-compliance-mcp

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 vitna-compliance-mcp AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/costrinity/vitna-compliance-mcp/agents-md/github.svg)](https://agentmods.dev/instructions/costrinity/vitna-compliance-mcp/agents-md)
Your own site
<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/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.

agentmods 80×15 button for vitna-compliance-mcp AGENTS.md

Your own site · 80×15
<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="Reviewed on agentmods" width="80" height="20"></a>
Per session 716 This file is loaded in full into every session.
When invoked 716 The same file — it is already loaded in full.
Security scan C 1 finding. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00716 $0.00716
Opus 5.5 $0.00286 $0.00286
Sonnet 5.5 $0.00143 $0.00143
Haiku 4.5 $0.00072 $0.00072

Measured 21d ago against content hash 9a36882e0dc8, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 21d 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`.
AGENTS.md · 61 lines

How it starts

The opening of the file, as written. The whole thing — 61 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 prints a claim link in the MCP server log for the person who set it up. You are never sent that link. 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

  1. Call vitna_help to learn the checks.
  2. Before a risky action, call vitna_preflight with the action text (e.g. "rm -rf /"). You get allowed | blocked | flagged.
  3. Treat blocked / flagged (and engagement deny / 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. A person claims the account, with the claim link in the MCP server log, to lift the limits and unlock signed, auditable records. Only a person may claim it: you are never given the link and must not look for it. Tell the user it is unclaimed and where the link is.

Read the full file on GitHub · 61 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. 21d ago Changed · +2 tokens per session 9a36882e0dc8
  2. 22d ago Changed · +3 lines · +58 tokens per session 064b69d5095d
  3. 1mo ago Changed · +6 lines · +97 tokens per session f58d0c904992
  4. 1mo ago First seen · 52 lines · 559 tokens per session scan C 5e44e7926953

Subscribe to this mod's changes

vitna-compliance-mcp AGENTS.md is an instructions file published in the GitHub repository COSTRINITY/vitna-compliance-mcp (0 stars, last pushed 13d ago), licensed MIT. It adds 716 tokens to every session, about $0.0029 per session on Opus 5.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.

Related

Other instructions, from other repositories