Borrowing it
Nothing to install: this file belongs to doodledood/manifest-dev. 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/doodledood/manifest-dev/main/CLAUDE.mdgit clone --depth 1 https://github.com/doodledood/manifest-devWrote 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/doodledood/manifest-dev/claude-md)<a href="https://agentmods.dev/instructions/doodledood/manifest-dev/claude-md"><img src="https://agentmods.dev/badge/instructions/doodledood/manifest-dev/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/doodledood/manifest-dev/claude-md"><img src="https://agentmods.dev/badge/instructions/doodledood/manifest-dev/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.08437 | $0.08437 |
| Opus 5.5 | $0.03375 | $0.03375 |
| Sonnet 5.5 | $0.01687 | $0.01687 |
| Haiku 4.5 | $0.00844 | $0.00844 |
Grade A, and why
manifest-dev 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 today.
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 — 309 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
Project Overview
manifest-dev marketplace — manifest-driven workflows for Claude Code. /define interviews and writes a Manifest; /do executes it and makes every Acceptance Criterion and Global Invariant hold on fresh evidence. Ships skills, not custom agents.
Public Repository Discipline
This repo is public. Everything committed or posted to it — docs, ADRs, READMEs, PR titles and descriptions, commit messages, issue text — must stand on its own merits. Keep out what a reader would be worse off for seeing: credentials and secrets, the contents of private planning or strategy documents, anything personal, and links into chat sessions or transcripts nobody outside can open. Also skip commentary on the repo's own adoption or popularity (star counts, usage levels, traction) — a positioning choice, not a secrecy one.
Set the bar there and no lower. Incidental working detail is fine and not worth policing: a branch name, a local path, the name of a workflow mode, a note on how a change was produced. Treating those as exposure costs more than it protects. ADRs state decisions with their technical grounds, not the deliberation history behind them. Temporary ops documents are allowed when clearly marked, but must read as neutral, forward-looking operations content.
Development Commands
# While iterating: lint and format (fixing), typecheck, test across every CPU; `scripts/setup.sh` once
scripts/check.sh --fix # or one group: scripts/check.sh lint|types|tests
# The evidence a change rests on: the same checks through the harness
scripts/verify drive property-suite
# Test plugin locally
/plugin marketplace add /path/to/manifest-dev
/plugin install manifest-dev@manifest-dev
tests/ asserts properties of the shipped prompts themselves — that gate examples use the current
schema, and two host-neutrality invariants over every
shipped Markdown file: no file names a host primitive (a plugin qualifier outside an HTML comment,
a Claude Code tool name, CLAUDE.md outside a detection or comparison, the word
"subagent"), and every skill a shipped skill names ships beside it — never marked
metadata.internal, and user-invocable: false when it exists only to be called. Adding a skill,
a dimension, or a delegation site can therefore turn the suite red without any Python changing,
and that red is the signal working as intended. The same suite fails when dist/codex drifts from
the source tree it copies. It also fails when a shipped file points to a section of another
(`FILE.md` → *Section*) that no longer exists there under that name.
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.
- today Changed · +33 tokens per session b6a77252bf5b
- yesterday Changed · +1 lines · +255 tokens per session ba06a589534e
- 2d ago Changed · -3 tokens per session b5e33c072143
- 4d ago Changed · +15 tokens per session 7728cb653b5e
- 5d ago Changed · +16 tokens per session 03555e07a399
- 6d ago Changed · +1 lines · +124 tokens per session 83dae28431d7
- 7d ago Changed · +1 lines · +63 tokens per session db10ca69faa1
- 8d ago Changed · +1 lines · +48 tokens per session 7c7100a549ee
- 9d ago Changed · +11 lines · +308 tokens per session 5282dcf203de
- 12d ago First seen · 294 lines · 7,578 tokens per session scan A 7bad5cc2aba2
manifest-dev CLAUDE.md is an instructions file published in the GitHub repository doodledood/manifest-dev (77 stars, last pushed yesterday), licensed MIT. It adds 8,437 tokens to every session, about $0.0337 per session on Opus 5.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-30.
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).
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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 copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
vscode model-prompts.instructions.md
Model-specific prompt authoring and registry guidelines.