Borrowing it
Nothing to install: this file belongs to yschimke/compose-ai-tools. 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/yschimke/compose-ai-tools/main/CLAUDE.mdgit clone --depth 1 https://github.com/yschimke/compose-ai-toolsWrote 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/yschimke/compose-ai-tools/claude-md)<a href="https://agentmods.dev/instructions/yschimke/compose-ai-tools/claude-md"><img src="https://agentmods.dev/badge/instructions/yschimke/compose-ai-tools/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/yschimke/compose-ai-tools/claude-md"><img src="https://agentmods.dev/badge/instructions/yschimke/compose-ai-tools/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.00437 | $0.00437 |
| Opus 5.5 | $0.00175 | $0.00175 |
| Sonnet 5.5 | $0.00087 | $0.00087 |
| Haiku 4.5 | $0.00044 | $0.00044 |
Grade A, and why
compose-ai-tools 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 1mo 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.
What it actually says
@AGENTS.md
The file above is the repository's canonical agent instructions — the CI-enforced
invariants, the PR workflow, and the map to docs/. Everything below is
Claude-Code-specific harness mechanics that no other agent can act on. Nothing
here restates a rule from AGENTS.md; if the two ever disagree, AGENTS.md wins.
Claude Code
- Repo-local skills live in
.claude/skills/and load on demand rather than on every turn:steward— driving a PR you opened to green: which fast checks to run before pushing, what counts as a failure that is not this PR's, and the check-in loop. Read it before acting on a CI failure or a review comment.render-evidence— capturing the before/after renders a UI-affecting PR needs, including bringing an Android SDK up in a fresh sandbox.flake-triage— proving a preview the diff bot flagged is unstable rather than regressed.
- Subscribe to every PR you open, on the same turn you open it
(
subscribe_pr_activity). Don't ask — tracking is the default; mention it in the reply. Stop on request withunsubscribe_pr_activityand push nothing further to that branch. - Keep a check-in scheduled while a PR you own is red or conflicted
(
send_later, roughly an hour out). Webhook events miss CI successes and merge transitions, so events alone are not enough. Re-arm silently when nothing changed; stop once the PR is merged or closed. <github-webhook-activity>events on tracked PRs are not no-ops. Push the fix when the change is clear and in scope,AskUserQuestionwhen it is ambiguous or architecturally significant, skip silently only for duplicates and echoes of your own comments.stewardhas the full posture.
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.
- 1mo ago First seen · 31 lines · 437 tokens per session scan A 82144b8f5298
compose-ai-tools CLAUDE.md is an instructions file published in the GitHub repository yschimke/compose-ai-tools (121 stars, last pushed today), licensed Apache-2.0. It adds 437 tokens to every session, about $0.0017 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).
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.