Borrowing it
Nothing to install: this file belongs to dosatos/minimise. 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/dosatos/minimise/main/CLAUDE.mdgit clone --depth 1 https://github.com/dosatos/minimiseWrote 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/dosatos/minimise/claude-md)<a href="https://agentmods.dev/instructions/dosatos/minimise/claude-md"><img src="https://agentmods.dev/badge/instructions/dosatos/minimise/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/dosatos/minimise/claude-md"><img src="https://agentmods.dev/badge/instructions/dosatos/minimise/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.01133 | $0.01133 |
| Opus 5.5 | $0.00453 | $0.00453 |
| Sonnet 5.5 | $0.00227 | $0.00227 |
| Haiku 4.5 | $0.00113 | $0.00113 |
Grade A, and why
minimise 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 25d 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 — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Claude Code Project Settings
Quick Start
Global commands (work everywhere):
/onboard # Read latest handoff + get oriented
/handoff # Create session handoff for next time
Or manually:
cat worklogs/handoffs/session-latest.md
Scratch & Generated Files — Keep the Repo Root Clean
NEVER write scratch, test, or generated artifacts to the repo root. They pollute
the package. Put them under worklogs/ (gitignored) instead:
- Throwaway plan YAMLs, sample plans, experiment configs →
worklogs/scratch/ - Test-run output / captured logs →
worklogs/(or pipe to/tmp) - Session handoffs →
worklogs/handoffs/ - Working plan docs →
docs/plans/*.md(gitignored; onlydocs/plans/completed/is tracked) - Agent/tool working dirs are local-only and globally ignored
The root must stay limited to real package files (src/, tests/, docs/,
packaging, README). If a tool needs a path, point it at worklogs/.
Environment
- Python: 3.9+
- Package: minimise (pip install -e .)
- Entry Point:
minicommand - Tests:
pytest tests/ -v - Config:
~/.minimise/(auto-created)
Session Handoff
At end of each session:
cp worklogs/handoffs/HANDOFF_TEMPLATE.md worklogs/handoffs/session-YYYY-MM-DD-HHmm.md
# Fill in: what was done, what's next, how to run, gotchas, current state
ln -sf session-YYYY-MM-DD-HHmm.md worklogs/handoffs/session-latest.md
Next session, read the handoff to get context.
Key Commands
# Orient yourself
cat worklogs/handoffs/session-latest.md
# Run tests
pytest tests/ -v
# Try the tool
mini job new --plan examples/example-plan.yaml
mini job list
# View docs
cat README.md
cat TESTING.md
Build Through mini, Not Inline
Implement features and fixes by running a mini job (or a mini loop for
open-ended refinement of one artifact). Author the plan with /minimise:job or
/minimise:brainstorm. This dogfoods the tool: every job is a test of mini.
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.
- 25d ago Changed · -1 lines · -23 tokens per session 8cc13ec42415
- 2mo ago First seen · 117 lines · 1,156 tokens per session scan A a66eab37e6e2
minimise CLAUDE.md is an instructions file published in the GitHub repository dosatos/minimise (11 stars, last pushed today), licensed MIT. It adds 1,133 tokens to every session, about $0.0045 per session on Opus 5.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
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).
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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 copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.