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/itdove/devaiflow/claude-mdgit clone --depth 1 https://github.com/itdove/devaiflowWhat 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.00122 | $0.00122 |
| Opus 5 | $0.00061 | $0.00061 |
| Sonnet 5 | $0.00024 | $0.00024 |
| Haiku 4.5 | $0.00012 | $0.00012 |
Grade A, and why
devaiflow CLAUDE.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
OpenWolf
@.wolf/OPENWOLF.md
This project uses OpenWolf for context management. Read and follow .wolf/OPENWOLF.md every session. Check .wolf/cerebrum.md before generating code. Check .wolf/anatomy.md before reading files.
DevAIFlow
See AGENTS.md for detailed project information and coding guidelines.
For daf tool usage instructions: See the daf-workflow skill - This skill is automatically loaded when you open sessions and provides comprehensive guidance on using daf commands, issue tracker integration, and workflows.
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 · 13 lines · 122 tokens per session scan A 75a7ea4b3106
devaiflow CLAUDE.md is an instructions file published in the GitHub repository itdove/devaiflow (2 stars, last pushed 14d ago), licensed Apache-2.0. It adds 122 tokens to every session, about $0.0006 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
mcp-atlassian copilot-instructions.md
Instructions for sooperset/mcp-atlassian, covering mcp atlassian - development guide, build, test, and lint, run all tests, run with coverage and run single test file.
AllBeads CLAUDE.md
Instructions for thrashr888/AllBeads, covering claude.md, project overview, what allbeads does, current state (v0.2.0) and rust development commands.
atlassian-skills CLAUDE.md
Instructions for eunsanMountain/atlassian-skills, covering atlassian-skills — claude.md, project overview, build & run, install (uv recommended) and run the cli.
kraken AGENTS.md
Instructions for rafael-adcp/kraken, covering agents.md — running as a kraken tentacle, your operating contract — read these, then follow them, why there are no deltas any more and driving it non-interactively.
claude-code-plugins CLAUDE.md
Instructions for zhebil/claude-code-plugins, covering claude.md, what this repo is, plugins, auto-enrich and common commands.
ultra-jira-mcp AGENTS.md
Instructions for criblio/ultra-jira-mcp, covering agents.md and quick reference.