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/mojomast/devussy/agents-mdgit clone --depth 1 https://github.com/mojomast/devussyWhat 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.01834 | $0.01834 |
| Opus 5 | $0.00917 | $0.00917 |
| Sonnet 5 | $0.00367 | $0.00367 |
| Haiku 4.5 | $0.00183 | $0.00183 |
Grade A, and why
devussy 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.
How it starts
The opening of the file, as written. The whole thing — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
This file provides guidance to agents when working with code in this repository.
🔗 CRITICAL: Anchor-Based Context Management
⚠️ READ THIS FIRST - This is the most important pattern in this project.
Devussy uses stable HTML comment anchors for efficient context management and safe file updates. All agents MUST use anchors when reading/writing devplan, phase, and handoff files.
Required Anchors
| File | Anchor | Purpose |
|---|---|---|
| devplan.md | <!-- PROGRESS_LOG_START --> / <!-- PROGRESS_LOG_END --> |
Track completed work |
| devplan.md | <!-- NEXT_TASK_GROUP_START --> / <!-- NEXT_TASK_GROUP_END --> |
Current 3-5 tasks to execute |
| phase*.md | <!-- PHASE_TASKS_START --> / <!-- PHASE_TASKS_END --> |
Phase-specific tasks |
| phase*.md | <!-- PHASE_PROGRESS_START --> / <!-- PHASE_PROGRESS_END --> |
Outcomes and blockers |
| handoff_prompt.md | <!-- QUICK_STATUS_START --> / <!-- QUICK_STATUS_END --> |
Status snapshot |
| handoff_prompt.md | <!-- HANDOFF_NOTES_START --> / <!-- HANDOFF_NOTES_END --> |
Agent handoff notes |
How to Use Anchors
Reading (CORRECT):
Read devplan.md lines between <!-- NEXT_TASK_GROUP_START --> and <!-- NEXT_TASK_GROUP_END -->
# Result: ~100 tokens loaded
Reading (WRONG):
Read entire devplan.md
# Result: ~3000 tokens wasted
Writing: Always use safe_write_devplan() from src/file_manager.py:
- Creates
.bakbackup before writing - Validates anchors exist in new content
- Refuses to overwrite if anchors missing (writes to
.tmpinstead)
Token Budget
| File | Section | ~Tokens | When to Read |
|---|---|---|---|
| handoff.md | Progress Log | ~200 | Start of session |
| devplan.md | NEXT_TASK_GROUP | ~100 | Every turn |
| devplan.md | PROGRESS_LOG | ~100 | If needed |
| phase*.md | PHASE_TASKS | ~80 | When working on phase |
Target: Stay under 500 tokens per turn by reading ONLY anchored sections.
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 · 131 lines · 1,834 tokens per session scan A 2b7b4e28e377
devussy AGENTS.md is an instructions file published in the GitHub repository mojomast/devussy (22 stars, last pushed 9mo ago), licensed MIT. It adds 1,834 tokens to every session, about $0.0092 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
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.
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).
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.
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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.