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/boutsioukis/no-botshit/claude-mdgit clone --depth 1 https://github.com/boutsioukis/no-botshitWrote 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/boutsioukis/no-botshit/claude-md)<a href="https://agentmods.dev/instructions/boutsioukis/no-botshit/claude-md"><img src="https://agentmods.dev/badge/instructions/boutsioukis/no-botshit/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.00662 | $0.00662 |
| Opus 5 | $0.00331 | $0.00331 |
| Sonnet 5 | $0.00132 | $0.00132 |
| Haiku 4.5 | $0.00066 | $0.00066 |
Grade A, and why
no-botshit 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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md — no-botshit
What this is
One skill. Two behaviors: council reasoning (internal) + caveman output (external).
Single source of truth: skills/no-botshit/SKILL.md. Root SKILL.md is a mirror — keep them in sync manually.
File layout
no-botshit/
├── README.md # Product pitch — most important file
├── SKILL.md # Root mirror (easy copy-paste for users)
├── CLAUDE.md # This file
├── CONTRIBUTING.md # Contribution guide
├── LICENSE # MIT
├── install.sh # Bash installer shim
├── benchmarks/ # Real output-token harness (no committed results)
│ ├── run.py
│ ├── prompts.txt
│ └── README.md
└── skills/
└── no-botshit/
└── SKILL.md # Source of truth — edit only here
Rules for README changes
- Before/After examples stay first. That's the pitch.
- Preserve caveman voice. "Big brain. Small mouth." is intentional.
- Token math section must stay accurate. Don't invent numbers. The ~65% figure belongs to caveman's benchmark and must stay attributed to them — never restate it as ours. Our numbers come only from
benchmarks/run.py. - Be honest that the council ADDS thinking tokens. no-botshit is not a universal token saver.
- claude.ai needs Extended Thinking toggled on (model picker) for the council to stay out of the answer.
ultrathink/effort:are Claude-Code-only. Keep install instructions in sync with this. - Install instructions must be tested before merge.
- Paper citations must link to real papers and name the author (arXiv 2604.00025 = MD Azizul Hakim).
Rules for SKILL.md changes
- Edit
skills/no-botshit/SKILL.md— single source of truth. - Sync root
SKILL.mdafter every change. ultrathinkkeyword must stay — it triggers extended thinking for the council stages.effort: highfrontmatter must stay — council deliberation needs it.- Auto-clarity exception block must stay — safety before style.
- Test: after changes, verify council stages still run silently (not echoed in output).
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 · 73 lines · 662 tokens per session scan A 093c0a878775
no-botshit CLAUDE.md is an instructions file published in the GitHub repository boutsioukis/no-botshit (6 stars, last pushed 2mo ago), licensed MIT. It adds 662 tokens to every session, about $0.0033 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
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.
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.
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 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).