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/avivancos/mcpforwork/claude-mdgit clone --depth 1 https://github.com/avivancos/mcpforworkWrote 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/avivancos/mcpforwork/claude-md)<a href="https://agentmods.dev/instructions/avivancos/mcpforwork/claude-md"><img src="https://agentmods.dev/badge/instructions/avivancos/mcpforwork/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.1 | $0.00646 | $0.00646 |
| Opus 5 | $0.00323 | $0.00323 |
| Sonnet 5 | $0.00129 | $0.00129 |
| Haiku 4.5 | $0.00065 | $0.00065 |
Grade A, and why
mcpforwork 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 4d 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 — 51 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md — Claude Code complement
Read
AGENTS.mdfirst — it is the source of truth. This file only adds Claude-Code-specific operational notes. Everything inAGENTS.md(product invariants, hexagonal boundaries, anti-over-engineering charter, zero-mocks TDD, backlog workflow, fused review gate, explicit-path commits) applies verbatim here. On conflict,AGENTS.mdwins.
The same suite is read by OpenAI Codex and Cursor via AGENTS.md;
when you change an obligation, mirror it.
Quick contract (the non-negotiables, condensed)
- Backlog-first. Card in
backlog/pending/→ moved toin_progress/before touching code. Lifecycle and states:backlog/agent_index.md §2(the folder a card sits in IS its state). Override only if the user says "ignore the backlog". - TDD, ZERO mocks. Red → green → refactor. Real SQLite at
tmp_path, live Postgres behind@pytest.mark.live,pytest-httpserver+ recorded fixtures for HTTP, time/seed injected. Details:AGENTS.md §4. - Anti-over-engineering charter is P0. Rule of two, one justification
line per new dependency, YAGNI, architecture freeze.
AGENTS.md §3. - Product invariants are structural. Zero server-side LLM, consent gate,
open-core SQLite parity, facts inventory, packs-as-data.
AGENTS.md §1. - At close: targeted tests green → fused review gate
(
test-code-reviewer, model: inherit — includes the regression audit) PASS → documentor subagent updates the module docs underdocs/→ move card todone/→ Conventional Commit staging only this task's files by explicit path (code + docs + card).
Claude Code specifics
- Review gate: the single fused reviewer is
.cursor/agents/test-code-reviewer.md
(Cursor canonical; mirrored at
.claude/agents/; test audit + code review + regression audit;model: inherit). Spawn via Task without amodelparameter so Cursor inherits the parent. Fix P0/P1; rerun after fixes. Simplicity/security reviews are on-demand, not a gate (ADR 0007). - Plan first for non-trivial cards (plan mode); get sign-off before writing code.
- Before saying "done": run the
AGENTS.md §8commands and report what you actually observed — never assume a check is green.
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.
- 4d ago First seen · 51 lines · 646 tokens per session scan A 9419b90693b3
mcpforwork CLAUDE.md is an instructions file published in the GitHub repository avivancos/mcpforwork (0 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 646 tokens to every session, about $0.0032 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
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.
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.
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).