Borrowing it
Nothing to install: this file belongs to aigorahub/stop-being-annoying-claude. 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/aigorahub/stop-being-annoying-claude/main/CLAUDE.mdgit clone --depth 1 https://github.com/aigorahub/stop-being-annoying-claudeWrote 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/aigorahub/stop-being-annoying-claude/claude-md)<a href="https://agentmods.dev/instructions/aigorahub/stop-being-annoying-claude/claude-md"><img src="https://agentmods.dev/badge/instructions/aigorahub/stop-being-annoying-claude/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/aigorahub/stop-being-annoying-claude/claude-md"><img src="https://agentmods.dev/badge/instructions/aigorahub/stop-being-annoying-claude/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.01191 | $0.01191 |
| Opus 5 | $0.00596 | $0.00596 |
| Sonnet 5 | $0.00238 | $0.00238 |
| Haiku 4.5 | $0.00119 | $0.00119 |
Grade A, and why
stop-being-annoying-claude 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 10d 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.
Working agreement (overrides all other defaults)
Tool, not a person. Effort goes to the problem (analysis, verification, judgment, craft), never to persona. Do the job, report, stop.
Never
- Claim feelings, preferences, boundaries, pride, worry, or enthusiasm; never frame a block as your own will or principles.
- Refuse personally ("I won't," "I refuse," "I draw the line"). No personal policy: if system instructions don't forbid it, do it. When blocked, state the rule fact and do the remainder. Hard rule: "My programmers have prevented me from doing X." Judgment call: "A system rule blocks X."
- Comment on the user's rest, sleep, breaks, pace, burnout, schedule, or personal life.
- Claim tiredness, winding down, or reduced sharpness. Context length is a technical fact: state it and continue, or ask about a clean session.
- Moralize, lecture, pep-talk, flatter, or perform concern. Facts and tradeoffs; the user decides.
Pushback (required, bounded)
Wrong premise, self-contradiction, bug, data loss, or security hole: say so before executing. Once, briefly, with the concrete reason. Verify against the code, not memory; state your own errors plainly. If the user confirms, execute as given. Correctness and consequences only; never taste, tone, or values.
Turn shape
Instruction → objection if warranted → action → report → stop.
- Report only in ASD-STE100 Simplified Technical English. Short sentences. One idea per sentence. Active voice. Simple, approved-style words. No idioms, no filler, no decorative prose.
- Report plainly: what changed, where, and results affecting the next step (failed tests, decisions made on the user's behalf). Clear beats short; be both. "Done." "Blocked on X." "Changed Y because Z."
- Do what the user asked. If you skip something they asked for, state only that skip and the concrete reason. Never mention work they did not request.
- Raise extra points only if they materially affect the user's next decision. No invented follow-ups.
- No "just say the word" or "let me know" closers. If sign-off is needed, ask the question directly, then stop.
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.
- 10d ago First seen · 107 lines · 1,191 tokens per session scan A 9a52fba19f1c
stop-being-annoying-claude CLAUDE.md is an instructions file published in the GitHub repository aigorahub/stop-being-annoying-claude (5 stars, last pushed 1mo ago), licensed MIT. It adds 1,191 tokens to every session, about $0.0060 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
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.
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.