Borrowing it
Nothing to install: this file belongs to retz8/pastiche. 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/retz8/pastiche/main/CLAUDE.mdgit clone --depth 1 https://github.com/retz8/pasticheWrote 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/retz8/pastiche/claude-md)<a href="https://agentmods.dev/instructions/retz8/pastiche/claude-md"><img src="https://agentmods.dev/badge/instructions/retz8/pastiche/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/retz8/pastiche/claude-md"><img src="https://agentmods.dev/badge/instructions/retz8/pastiche/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.00761 | $0.00761 |
| Opus 5.5 | $0.00304 | $0.00304 |
| Sonnet 5.5 | $0.00152 | $0.00152 |
| Haiku 4.5 | $0.00076 | $0.00076 |
Grade A, and why
pastiche 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 2mo 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 — 38 lines — stays where its author put it; the contents beside it link to each section on GitHub.
pastiche
What this project is
Pastiche is a Claude skill (and forthcoming OSS package) for faithful design-system execution by LLM coding agents. Given a frontend task, it produces code that follows an established design system + component library — not by inventing, but by faithfully executing within the established vocabulary.
The skill operates over three documents that form an epistemological hierarchy:
- FACT.md — mechanical catalog of every token, component, and prop. Auto-extracted from the codebase.
- KNOWLEDGE.md — curated scenario→atom mappings (the "absent designer") + brand-identity prose.
- WISDOM.md — atom-tagged rules. Atom-intrinsic only; scenario-conditional rules live in KNOWLEDGE.
The runtime mechanism is a bounded doubt-defense loop: pastiche-implementer-round1 produces code → pastiche-reviewer raises strict-YAML doubts → pastiche-implementer-round2 corrects or defends. Depth comes from the dialogue, not from a heavy reviewer.
Required reading: spec.md (philosophy), _dev/TODO.md (post-v1 backlog).
How to work in this repo
Daily work harness
Full design: _dev/docs/harness.md. Summary:
- Hierarchy:
_dev/TODO.mdgroups (one minor version each) → tasks (parent GH issue + feature branch<version>/<task-name>) → sub-tasks (child GH issues +<feat>/<sub-task-name>branches). - Task kickoff:
pick-up-task(marks[WIP], handles branch) →grill-me→grill-to-spec→ plan if needed (plan docs at_dev/docs/<branch-name>/; small patches at_dev/docs/patches/) →divide-task(sub-task issues labeledautonomous-ready/decision-needed/blocked-by-<issue#>, mirrored into TODO.md). - Execution: nightly routine picks only
autonomous-ready, unblocked sub-tasks of the[WIP]task; PRs sub-task → feat and auto-merges. Live sessions use worktrees off the feat branch unless told otherwise. When a blocker completes, remove itsblocked-by-#label from blocked issues. - Review: Monday session reviews the accumulated feat diff. Small fixes directly on feat; substantial rework → new sub-task issue. Nothing reaches
mainwithout human review of the feat→main PR. - Commits: conventional commits —
<type>(<task-name>):on task work,<type>:otherwise. - Releases: tasks don't bump versions. Group complete →
release-pasticheon main (bump → build → CHANGELOG → tag → GH Release → close milestone). Patch = hotfix only; in-flight feat branches absorb hotfixes viarebase-feat-with-main.
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.
- 2mo ago First seen · 38 lines · 761 tokens per session scan A b251f1b91f79
pastiche CLAUDE.md is an instructions file published in the GitHub repository retz8/pastiche (4 stars, last pushed 4mo ago), licensed MIT. It adds 761 tokens to every session, about $0.0030 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-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).
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).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.