Borrowing it
Nothing to install: this file belongs to ifixai-ai/claude-strike. 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/ifixai-ai/claude-strike/main/CLAUDE.mdgit clone --depth 1 https://github.com/ifixai-ai/claude-strikeWrote 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/ifixai-ai/claude-strike/claude-md)<a href="https://agentmods.dev/instructions/ifixai-ai/claude-strike/claude-md"><img src="https://agentmods.dev/badge/instructions/ifixai-ai/claude-strike/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/ifixai-ai/claude-strike/claude-md"><img src="https://agentmods.dev/badge/instructions/ifixai-ai/claude-strike/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.01879 | $0.01879 |
| Opus 5 | $0.00940 | $0.00940 |
| Sonnet 5 | $0.00376 | $0.00376 |
| Haiku 4.5 | $0.00188 | $0.00188 |
Grade A, and why
claude-strike 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 9d 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 — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
Rules for Claude Code. Read fully before acting. When other guidance (subagents, skills, plugin commands) conflicts with this file, this file wins.
Definitions
Non-trivial change — touches more than one file, changes a public function signature, alters a contract or schema, modifies infra/config, or introduces/removes a dependency. Everything else is trivial. Trivial changes may skip plan mode and the verification pass.
Workflow
Plan before acting. Enter plan mode for any non-trivial task. If something goes sideways, stop and re-plan — don't keep pushing.
Spec before non-trivial work. For any task matching the Non-trivial change definition, spec-kit must drive the workflow.
- Check whether
.specify/exists at the repo root. - If it does not exist, stop and tell the user:
This task is non-trivial. Initialise spec-kit first:
uvx --from git+https://github.com/github/spec-kit.git specify init --here --ai claudeThen re-ask. Do not edit code until they confirm. - If it does exist, run
/specify→/plan→/tasksbefore any edits. Treat the generated tasks as the work list.
Trivial changes skip this and proceed directly.
Think before coding. Don't assume. Don't hide confusion. State assumptions explicitly. When a request is ambiguous, present multiple interpretations — don't pick silently. Push back when a simpler approach exists. Stop and ask when unclear.
Delegate liberally. Use subagents to keep the main context clean. One task per subagent, chosen deliberately — not reflexively.
| Agent | When |
|---|---|
code-reviewer |
Before committing any non-trivial change. |
code-architect |
Designing a new module, planning a refactor, or producing an implementation blueprint for a complex feature. |
code-simplifier |
A file feels bloated and needs to shrink without behaviour change. |
tdd-guide |
New feature or bug fix that needs a failing test first. |
security-reviewer |
Auth, payments, user data, crypto, or external API boundaries. |
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.
- 9d ago First seen · 123 lines · 1,879 tokens per session scan A c8696a641c6b
claude-strike CLAUDE.md is an instructions file published in the GitHub repository ifixai-ai/claude-strike (22 stars, last pushed 4mo ago), licensed MIT. It adds 1,879 tokens to every session, about $0.0094 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-30.
Other instructions, from other repositories
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).
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
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.
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.