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/thevibeworks/deva/agents-mdgit clone --depth 1 https://github.com/thevibeworks/devaWhat 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.00092 | $0.00092 |
| Opus 5 | $0.00046 | $0.00046 |
| Sonnet 5 | $0.00018 | $0.00018 |
| Haiku 4.5 | $0.00009 | $0.00009 |
Grade A, and why
deva 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.
What it actually says
AGENTS.md
Repo guidance for coding agents lives in CLAUDE.md (architecture, issue-based development workflow) and workflows/ (issue, commit, PR, release conventions). Read those before changing anything.
Container-environment facts are injected at launch into untracked local files (CLAUDE.local.md; a deva-owned AGENTS.md only in workspaces that have none). They are per-launch state and must never be committed.
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 · 11 lines · 92 tokens per session scan A 907dfe4d6b59
deva AGENTS.md is an instructions file published in the GitHub repository thevibeworks/deva (13 stars, last pushed 5d ago), licensed MIT. It adds 92 tokens to every session, about $0.0005 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
agent-drop GEMINI.md
Gemini CLI instructions for mikezio/agent-drop: When this repo is configured as an MCP server in a CLI agent.
ai-cli-in-docker AGENTS.md
AGENTS.md instructions for vladborovtsov/ai-cli-in-docker, a project described as: Collection of AI CLI wrappers: Run AI CLI tools (OpenAI Codex, Google Gemini, OpenCode, Claude Code) inside Docker to keep your host clean while persisting CLI auth/config on your machine.
prompt-tracker GEMINI.md
Gemini CLI instructions for DaRabus/prompt-tracker, covering gemini.md, project overview, architecture, build & test commands and full stack.
prompt-tracker AGENTS.md
AGENTS.md instructions for DaRabus/prompt-tracker, covering agents.md, project, mandatory rules, rule 1 — always update tests and rule 2 — always update readme.md.
prompt-tracker copilot-instructions.md
Copilot instructions for DaRabus/prompt-tracker, covering github copilot instructions, project, agent skills index, project skills and external skills.
prompt-tracker CLAUDE.md
Claude Code instructions for DaRabus/prompt-tracker, covering claude.md, quick reference, claude-specific behavior, tool usage and skills are mandatory.