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/aidemd-mcp/server/claude-mdgit clone --depth 1 https://github.com/aidemd-mcp/serverWrote 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/aidemd-mcp/server/claude-md)<a href="https://agentmods.dev/instructions/aidemd-mcp/server/claude-md"><img src="https://agentmods.dev/badge/instructions/aidemd-mcp/server/claude-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 | $0.01396 | $0.01396 |
| Opus 5 | $0.00698 | $0.00698 |
| Sonnet 5 | $0.00279 | $0.00279 |
| Haiku 4.5 | $0.00140 | $0.00140 |
Grade A, and why
server 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 3d 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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AIDE — Autonomous Intent-Driven Engineering
This project uses the AIDE methodology. AIDE treats a short .aide intent
spec living next to orchestrator code as the contract every downstream
agent (architect, implementor, QA) works from — when the intent changes,
the code changes.
The full canonical methodology is installed in this project at
.aide/docs/. Start at .aide/docs/index.md for the doc list, then
crawl into the specific canonical doc your current task requires. Read
only what the task actually needs — the doc directory is organized for
progressive disclosure, not for front-loading.
Before writing, editing, or acting on any .aide file, crawl the doc directory
and read the canonical doc that governs the work you are about to do.
Never guess AIDE rules from memory: the files under .aide/docs/ are
the authoritative source, and any decision that disagrees with them is
wrong by definition.
AIDE tools quick-reference:
aide_discover— map where.aidespecs live in the projectaide_read— read a specific.aidefile with contextaide_scaffold— create a new.aidefileaide_validate— check spec layout for drift or issuesaide_init— bootstrap AIDE into a new project (first-time setup)aide_upgrade— update/sync/refresh AIDE docs, commands, agents, and skills to the latest canonical versions (use this when asked to "update AIDE", "update the docs", or "sync the methodology")
Invoking /aide and /aide:*: when the user invokes any AIDE slash command, your first action must be to invoke the matching skill via the Skill tool — for /aide, that is Skill(skill="aide", args=...). The slash-command file at .claude/commands/aide.md is a thin signpost; the orchestrator prose and the MANDATORY BOOT SEQUENCE live in the aide skill (.claude/skills/aide/SKILL.md). Do NOT attempt to handle the request from the command file alone, do NOT skip the skill, and do NOT respond to the user's request before the boot sequence completes — skipping boot means orchestrating a methodology you don't know.
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.
- 3d ago First seen · 84 lines · 1,396 tokens per session scan A 8b896d1b24b5
server CLAUDE.md is an instructions file published in the GitHub repository aidemd-mcp/server (3 stars, last pushed 3mo ago), licensed MIT. It adds 1,396 tokens to every session, about $0.0070 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
memorix CLAUDE.md
Instructions for AVIDS2/memorix, covering memorix - agent instructions for claude code, using memorix memory tools, when to search memory, when to store memory and when to resolve memory.
memorix GEMINI.md
Instructions for AVIDS2/memorix, covering memorix - cross-agent memory rules, session start - bind project, then load context, during session - capture important context, architecture & decisions and bug fixes & problem solving.
speclock CLAUDE.md
Instructions for sgroy10/speclock, covering speclock development rules, mandatory release process, step 1: version bump (all 7 files), step 2: commit + push and step 3: npm publish.
speclock copilot-instructions.md
Instructions for sgroy10/speclock, covering github copilot instructions (speclock), constraints and project decisions.
speclock GEMINI.md
Instructions for sgroy10/speclock, covering gemini.md — project constraints (speclock), goal, non-negotiable constraints and decisions.
speclock AGENTS.md
Instructions for sgroy10/speclock, covering speclock development guide, project, required checks, security and compatibility.