Borrowing it
Nothing to install: this file belongs to vassiliylakhonin/agenda-intelligence-md. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/vassiliylakhonin/agenda-intelligence-md/main/CLAUDE.mdgit clone --depth 1 https://github.com/vassiliylakhonin/agenda-intelligence-mdWrote 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/vassiliylakhonin/agenda-intelligence-md/claude-md)<a href="https://agentmods.dev/instructions/vassiliylakhonin/agenda-intelligence-md/claude-md"><img src="https://agentmods.dev/badge/instructions/vassiliylakhonin/agenda-intelligence-md/claude-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.
<a href="https://agentmods.dev/instructions/vassiliylakhonin/agenda-intelligence-md/claude-md"><img src="https://agentmods.dev/badge/instructions/vassiliylakhonin/agenda-intelligence-md/claude-md.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00399 | $0.00399 |
| Opus 5 | $0.00199 | $0.00199 |
| Sonnet 5 | $0.00080 | $0.00080 |
| Haiku 4.5 | $0.00040 | $0.00040 |
Grade A, and why
agenda-intelligence-md 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 11d 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
Claude Code working rules
AGENTS.md is the canonical project contract — apply it, do not restate it. It points to the detail files, loaded when the task needs them:
- docs/vertical-workers.md — shipped workers, the artifact ladder, hard requirements for a new one.
- docs/geography-routing.md — routing term sets; one of the two canon mirrors the routing guard checks.
- docs/local-checks.md — what to run before push, in what order, plus the dual-copy invariant.
Runtime skill contracts: skills/agenda-intelligence/SKILL.md and skills/source-ingest/SKILL.md.
Before push
make ci
Sufficient for most changes — lint, typecheck, full test suite. Everything else, including which step failed and why, is in docs/local-checks.md. Do not keep a second copy of that list here.
Two traps worth naming up front: black --check runs first in CI and fails the whole pipeline on formatting drift, and the dual-copy paths under src/agenda_intelligence/data/ must change in the same commit as their top-level twins.
Working style in this repo
Follow existing schema, CLI, and MCP patterns instead of inventing new ones. Additive changes are allowed without prior approval under the change-discipline rules in AGENTS.md — behind a stable contract, with a contract test and a CHANGELOG entry.
Breaking v1 schema changes, removing MCP tools, and renaming public HTTP endpoints or A2A profiles need an ADR and a version bump. The v1.0.x contract freeze (ADR 0003) is still in force.
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.
- 11d ago First seen · 28 lines · 399 tokens per session scan A e4df02749e3f
agenda-intelligence-md CLAUDE.md is an instructions file published in the GitHub repository vassiliylakhonin/agenda-intelligence-md (6 stars, last pushed 2d ago), licensed MIT. It adds 399 tokens to every session, about $0.0020 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
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
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).
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.
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).