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 skills/dosatos/minimise/setupnpx skills add dosatos/minimise --skill setupgit clone --depth 1 https://github.com/dosatos/minimiseWhat 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 | $0.00028 | $0.00710 |
| Opus 5 | $0.00014 | $0.00355 |
| Sonnet 5 | $0.00006 | $0.00142 |
| Haiku 4.5 | $0.00003 | $0.00071 |
Grade A, and why
setup 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 2d 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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Setting up minimise
Get mini working in the user's current project. Verify first, install only what is
missing, and write nothing into their repo.
Do not touch the project
This skill is read-only with respect to the user's repository. It must NOT create or edit
.claude/settings.json, hooks, plan files, scaffolding, or any other file in their project.
All minimise state (config, database, job dirs) lives in ~/.minimise/, which is created
automatically on first run. If the user asks for project scaffolding, that is a different
conversation — say so rather than quietly writing files.
1. Check the three prerequisites
mini --help # the minimise CLI (there is no --version flag)
claude --version # the agent harness minimise shells out to for every task
git rev-parse --show-toplevel # jobs run inside a git repo; commits/diffs track task output
Report each as present or missing before doing anything about it.
claudemissing — minimise cannot execute a single task without it. Point the user at https://docs.anthropic.com/en/docs/claude-code and stop; do not try to install it for them.- Not a git repo — jobs commit each task's work, so there is nothing to commit against.
Tell the user to
git init(or move to a repo) and stop. Do notgit initfor them. minimissing — install it (below).
2. Install mini if it is missing
Requires Python 3.9+. From a local clone:
pip install -e . # run from the minimise repo root
Or straight from the repo:
pip install git+https://github.com/dosatos/minimise.git
Then re-verify — an install that does not put mini on PATH is not an install:
mini --help
If it still is not found, the likely cause is a pip that installed into a different Python
than the one on PATH (pyenv/venv mismatch). Say that plainly and show which -a python3 pip
rather than guessing.
3. Confirm and hand off
When all three checks pass, tell the user:
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.
- 2d ago First seen · 71 lines · 28 tokens per session scan A 9549d3b71dd3
setup is a skill published in the GitHub repository dosatos/minimise (11 stars, last pushed 13d ago), licensed MIT. It adds 28 tokens to every session and 710 once invoked, about $0.0001 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…