Borrowing it
Nothing to install: this file belongs to work0r-ai/agent-kit. 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/work0r-ai/agent-kit/main/CLAUDE.mdgit clone --depth 1 https://github.com/work0r-ai/agent-kitWrote 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/work0r-ai/agent-kit/claude-md)<a href="https://agentmods.dev/instructions/work0r-ai/agent-kit/claude-md"><img src="https://agentmods.dev/badge/instructions/work0r-ai/agent-kit/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/work0r-ai/agent-kit/claude-md"><img src="https://agentmods.dev/badge/instructions/work0r-ai/agent-kit/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.01262 | $0.01262 |
| Opus 5.5 | $0.00505 | $0.00505 |
| Sonnet 5.5 | $0.00252 | $0.00252 |
| Haiku 4.5 | $0.00126 | $0.00126 |
Grade A, and why
agent-kit 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.
How it starts
The opening of the file, as written. The whole thing — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
workorai-agent-kit — Agent Instructions
Implementation Protocol
Applies when a task is a feature or touches 3+ files. For smaller changes (1-2 files, typo, question, research-only), skip this protocol and work normally.
Preconditions (first step)
- git: if the repo is under git, the commit rule is active. If not, skip
commits and note
Commit: N/A (no git)in the diary. - clawmem: check the index (
index_stats/status). If not indexed, index it first (reindex; add the project to~/.config/clawmem/index.ymlif needed), then continue. If indexing is impossible, mirror the durable summary into the diary withclawmem: N/A.
1. Prior-art search (before planning)
Search whether this was built or researched before — including by other agents in other projects (clawmem covers all indexed collections simultaneously):
- clawmem:
search/intent_searchfor direct matches;find_similarfor semantically close patterns;kg_query/find_causal_linksfor graph-based cross-project discovery - git:
git log --grepandgit log -S - tasks: grep past diaries in
.tasks/
Record findings in the diary. If a similar feature exists in another project, reuse or adapt — note what was borrowed and why.
If a brainstorm precedes the work, run this same search during the brainstorm too — the findings sharpen the design doc. This does not replace the pre-planning search; do both.
2. Diary (.tasks/, gitignored)
Create .tasks/YYYY-MM-DD-<slug>.md first. One file per task. The agent only
creates and appends — it never deletes (the human cleans manually).
Structure:
- Plan: checklist of tickets (T1, T2, …)
- Prior art: clawmem / git / tasks findings + conclusion
- Per ticket on close: what done, how, deviations from plan + why, research, commit hash (if git), clawmem id
3. Stages & commits
A stage = an atomic, revertable unit that can be described as one change. Group tickets into a stage by this criterion, not by ticket count.
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 · 107 lines · 1,262 tokens per session scan A ef72f32739e2
agent-kit CLAUDE.md is an instructions file published in the GitHub repository work0r-ai/agent-kit (0 stars, last pushed 3mo ago), licensed MIT. It adds 1,262 tokens to every session, about $0.0050 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
pudo-code-system pudo-api.instructions.md
Instructions for DongDuong2001/pudo-code-system, covering backend code guidelines, api changes, database changes, authentication & permissions and verification.
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).