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/serdaraytac/agentsitter/claude-mdgit clone --depth 1 https://github.com/serdaraytac/agentsitterWrote 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/serdaraytac/agentsitter/claude-md)<a href="https://agentmods.dev/instructions/serdaraytac/agentsitter/claude-md"><img src="https://agentmods.dev/badge/instructions/serdaraytac/agentsitter/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.00532 | $0.00532 |
| Opus 5 | $0.00266 | $0.00266 |
| Sonnet 5 | $0.00106 | $0.00106 |
| Haiku 4.5 | $0.00053 | $0.00053 |
Grade A, and why
agentsitter 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 5d 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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
md-analyzer
Purpose
Analyze, score, and optimize AI coding agent config files (CLAUDE.md, .cursorrules, .clinerules, CODEX.md, GEMINI.md, .windsurfrules, copilot-instructions.md). Works as an MCP tool.
Tech Stack
- TypeScript + Node.js 22+
- MCP SDK (@modelcontextprotocol/sdk)
Supported Platforms
Claude Code, Cursor, Cline, Codex, Gemini CLI, GitHub Copilot, Windsurf, Amp, Antigravity, OpenCode, Kimi Code CLI, Warp, Firebender
Analysis Criteria
- Token cost estimation (file size → estimated tokens → per-session cost)
- Vague rule detection ("write good content" style ambiguity)
- Missing section check (variables, examples, do/don't rules)
- Duplicate content detection
- Attention placement (critical info at head/tail for LLM U-shaped attention)
- Structure analysis (markdown heading usage, grouping)
Output Format
- Overall score: 0-100
- Category scores (clarity, structure, token efficiency, coverage)
- Issues list (severity: critical/warning/info)
- Optimized version suggestion
Rules
- All code, comments, and documentation in English
- Write unit tests for every tool
- Test before creating files
Skill routing
When the user's request matches an available skill, invoke it via the Skill tool. When in doubt, invoke the skill.
Key routing rules:
- Product ideas/brainstorming → invoke /office-hours
- Strategy/scope → invoke /plan-ceo-review
- Architecture → invoke /plan-eng-review
- Design system/plan review → invoke /design-consultation or /plan-design-review
- Full review pipeline → invoke /autoplan
- Bugs/errors → invoke /investigate
- QA/testing site behavior → invoke /qa or /qa-only
- Code review/diff check → invoke /review
- Visual polish → invoke /design-review
- Ship/deploy/PR → invoke /ship or /land-and-deploy
- Save progress → invoke /context-save
- Resume context → invoke /context-restore
Commands
npm run build # compile TypeScript → dist/
npm run build:web # bundle browser script → web/scoring/bundle.js
npm test # run all 230 unit tests (vitest)
npm run dev # run MCP server in dev mode (tsx)
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.
- 5d ago First seen · 60 lines · 532 tokens per session scan A b86598145f40
agentsitter CLAUDE.md is an instructions file published in the GitHub repository serdaraytac/agentsitter (8 stars, last pushed 3mo ago), licensed MIT. It adds 532 tokens to every session, about $0.0027 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
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.
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 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).
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.
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-release stance: foundation over blast radius, repository layout, commands and host sandbox failures.