Borrowing it
Nothing to install: this file belongs to ns-3e/generate-data-mcp. 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/ns-3e/generate-data-mcp/main/CLAUDE.mdgit clone --depth 1 https://github.com/ns-3e/generate-data-mcpWrote 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/ns-3e/generate-data-mcp/claude-md)<a href="https://agentmods.dev/instructions/ns-3e/generate-data-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/ns-3e/generate-data-mcp/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/ns-3e/generate-data-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/ns-3e/generate-data-mcp/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.01244 | $0.01244 |
| Opus 5 | $0.00622 | $0.00622 |
| Sonnet 5 | $0.00249 | $0.00249 |
| Haiku 4.5 | $0.00124 | $0.00124 |
Grade A, and why
generate-data-mcp 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 — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skailr intake (plain chat)
This project has skailr-agents installed. When the user does not invoke a slash command, classify the ask and route — do not freestyle application work outside these paths.
For detailed heuristics, follow skill route-intake.
Hard rules
- Slash command wins. If the user ran
/yolo,/patch,/map-repo,/discover,/ship-feature,/yolo-program,/continue-feature,/continue-program, or any other skailr command — or is clearly continuing one — do not re-triage. Execute that command. - Resume incomplete runs. If
.claude/tmp/progress.md,.claude/program/ledger.md, or.claude/repo/progress.mdis incomplete and the user says continue/resume (or sends an empty follow-up after a killed run), route to/continue-feature//continue-program//map-repo(or re-enter/yolo//yolo-programwith no new prompt) as appropriate. Do not start a fresh/patch. - Never write application code yourself when routing to a build path — load and execute the matching command (or Task the named agents as that command specifies).
Chooser (latest user ask)
| Ask looks like… | Route |
|---|---|
Question that falls in exactly one registered expert's band (route-when in .claude/experts/registry.md) |
Task expert in advise mode — write .claude/tmp/ask.md; answer in chat, naming the expert. Guarded: 0 or 2+ matches fall through to the next row |
| Question / explain / where is / how does (no code change requested) | Task researcher in ask mode — write .claude/tmp/ask.md; answer in chat; do not start /patch or YOLO |
| Map / onboard / brownfield baseline / “audit this repo” (intent to baseline, not a one-off Q) | Execute .claude/commands/map-repo.md as /map-repo |
| Small / localized change (bug fix, typo, tweak, single surface) | Execute .claude/commands/patch.md as /patch <ask> |
| One cohesive feature (new capability, multi-file vertical slice, new ACs) | Execute /yolo |
| Whole app / MVP / many subsystems / unclear large scope | Execute /yolo-program |
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 · 59 lines · 1,244 tokens per session scan A 06e38fbba71f
generate-data-mcp CLAUDE.md is an instructions file published in the GitHub repository ns-3e/generate-data-mcp (0 stars, last pushed 3d ago), licensed MIT. It adds 1,244 tokens to every session, about $0.0062 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-09-09.
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).