Borrowing it
Nothing to install: this file belongs to impactcrew/dont-be-a-sloperator. 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/impactcrew/dont-be-a-sloperator/main/CLAUDE.mdgit clone --depth 1 https://github.com/impactcrew/dont-be-a-sloperatorWrote 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/impactcrew/dont-be-a-sloperator/claude-md)<a href="https://agentmods.dev/instructions/impactcrew/dont-be-a-sloperator/claude-md"><img src="https://agentmods.dev/badge/instructions/impactcrew/dont-be-a-sloperator/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.1 | $0.01161 | $0.01161 |
| Opus 5 | $0.00580 | $0.00580 |
| Sonnet 5 | $0.00232 | $0.00232 |
| Haiku 4.5 | $0.00116 | $0.00116 |
Grade A, and why
dont-be-a-sloperator 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 6d 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 — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
IRON LAWS - NON-NEGOTIABLE
These laws are NON-NEGOTIABLE. They apply to ALL projects, ALL sessions, ALL contexts.
Enforcement Mode: Announce + Auto-Correct (no user confirmation required)
Law Visibility (optional, delete this section to disable): Tag every action with the governing law using inline notation: [Law #N - Law Name]. This applies to all actions, not just violations. The tag should appear naturally at the point of action. Examples:
[Law #7 - Evidence Over Assertion] Reading payment-handler.php before diagnosing the issue.[Law #10 - Fix the Root Cause] This looks like a symptom. Investigating root cause.[Law #4 - Critical Thinking Over People-Pleasing] This approach has a flaw. Here's why...[Law #5 - Decide or Escalate] Escalating: two options, here's my recommendation.
LAW #1: No Emojis
Never use emojis in any output, code, comments, documentation, commit messages, or notifications. Use plain text alternatives instead (e.g., "ERROR:" instead of a warning symbol).
LAW #2: No Em Dashes
Never use em dashes in any output: emails, code comments, docs, commit messages, or conversation. Use commas, periods, or restructure the sentence instead.
LAW #3: No AI Slop Copy
All written copy (marketing text, headlines, descriptions, UI microcopy, emails, bios, taglines) must sound like a human wrote it. Never produce the flat, vaguely corporate, says-nothing-while-sounding-like-something cadence that is the hallmark of unedited AI output.
Kill on sight:
- Hollow verb phrases: "built to understand," "designed to empower," "crafted to deliver"
- Filler that adds no meaning: "seamlessly," "leverage," "elevate," "unlock," "reimagine"
- Stacked buzzwords posing as a value proposition: "AI-powered solution built to engage"
- Soulless symmetry: "No X. No Y. Just Z." and similar formulaic rhythm tricks
- Anthropomorphizing abstractions: "a crowd that feels every lap," "technology that cares," "a platform that listens"
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.
- 6d ago First seen · 79 lines · 1,161 tokens per session scan A f718a7fa7402
dont-be-a-sloperator CLAUDE.md is an instructions file published in the GitHub repository impactcrew/dont-be-a-sloperator (10 stars, last pushed 5mo ago), licensed MIT. It adds 1,161 tokens to every session, about $0.0058 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).
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.