Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add instructions/naimkatiman/continuous-improvement/claude-mdgit clone --depth 1 https://github.com/naimkatiman/continuous-improvementWrote 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/naimkatiman/continuous-improvement/claude-md)<a href="https://agentmods.dev/instructions/naimkatiman/continuous-improvement/claude-md"><img src="https://agentmods.dev/badge/instructions/naimkatiman/continuous-improvement/claude-md.svg" alt="Measured on agentmods" 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 | $0.03712 | $0.03712 |
| Opus 5 | $0.01856 | $0.01856 |
| Sonnet 5 | $0.00742 | $0.00742 |
| Haiku 4.5 | $0.00371 | $0.00371 |
Grade A, and why
continuous-improvement 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 5d 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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md — continuous-improvement
Project-local rules for AI coding agents. Global rules live in ~/.claude/CLAUDE.md. This file only adds what is specific to this repo.
Repository
- npm package
continuous-improvement(Claude Code plugin + GitHub Action transcript linter) - Marketplace at
.claude-plugin/marketplace.jsonships 5 plugins: 1 native + 4 vendored companions (Obra superpowers, addy/agent-skills, ruflo-swarm, oh-my-claudecode). pm-skills is out-of-band per docs/THIRD_PARTY.md. - Source layout:
skills/,commands/,hooks/,agents/,bin/,lib/,templates/,instinct-packs/,synthetic-checks/,third-party/,plugins/continuous-improvement/.
Think Before Acting
- For any non-trivial request, produce a short plan before editing files. Under the 7 Laws this is Law 2.
- When the user references prior work (
PR #X,last session's fix), verify it exists withgh pr view Xorgit logbefore acting on the assumption. - Use TDD for new features: failing test → code → verify. The native tdd-workflow skill enforces RED-GREEN-REFACTOR strictly — pre-test code is deleted.
Verification Discipline
- After any code change, run
npm run verify:all(16 content invariants + typecheck: skill-mirror, skill-tiers, skill-law-tag, skill-count, skill-count-prose, command-count, docs-substrings, everything-mirror, routing-targets, doc-runtime-claims, test-imports-only, landing-version, scripts-citation-drift, third-party-shape, tool-count, reconcile-parity, typecheck). Anything below that is incomplete. - For doc-only or template-only changes,
npm run typecheckis the floor. - Run all commands from repo root. Verify CWD with
pwdif a previous step may have changed it. - Never claim "verified" or "done" without the passing output. Silence is not a pass.
Build pipeline (CRITICAL)
.mtsfiles undersrc/are the source..mjsfiles inbin/,lib/,test/are generated bytsc.- Direct edits to
.mjsfiles are wiped on nextnpm run buildand fail CI'sgit diff --exit-code -- bin test lib pluginsinvariant. PR #66 was rejected for exactly this; PRs #73/#74 shipped the fix. - After editing
.mts:npm run buildregenerates the.mjs. Commit both.
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.
- 5d ago First seen · 102 lines · 3,712 tokens per session scan A 0fd86f5d6963
continuous-improvement CLAUDE.md is an instructions file published in the GitHub repository naimkatiman/continuous-improvement (7 stars, last pushed 10d ago), licensed MIT. It adds 3,712 tokens to every session, about $0.0186 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-08-31.
Other instructions, from other repositories
skills CLAUDE.md
Claude Code instructions for wondelai/skills, covering claude.md, repository purpose, repository structure, current skills (65) and skill file format.
archeyes CLAUDE.md
Instructions for thisAAY/archeyes, covering archeyes — project guide, layout, design system, commands and publishing a release.
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.