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 skills add dosatos/minimise --skill jobgit 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/skills/dosatos/minimise/job)<a href="https://agentmods.dev/skills/dosatos/minimise/job"><img src="https://agentmods.dev/badge/skills/dosatos/minimise/job/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/skills/dosatos/minimise/job"><img src="https://agentmods.dev/badge/skills/dosatos/minimise/job.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.00030 | $0.00811 |
| Opus 5 | $0.00015 | $0.00405 |
| Sonnet 5 | $0.00006 | $0.00162 |
| Haiku 4.5 | $0.00003 | $0.00081 |
Grade A, and why
job 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 8d 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 — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Running work as a minimise job
Why a job beats this session
A mini job runs each task in a fresh agent session that sees only the previous task's
diff and completion report, so context does not rot across a long build the way it does here.
The plan is a YAML file the user reviews, edits, and commits — the pipeline lives in the
repo instead of evaporating in a transcript. Failed tasks retry; a crash mid-run resumes
from the first incomplete task. And hooks gate the work: a pre_plan review can block a
bad plan before any code runs, and a post_task review can re-run a task with the findings
fed back in.
Prerequisite
If mini --help fails, mini is not installed. Tell the user to run /minimise:setup and
stop. Do not install it from here.
PROPOSE — nothing runs until the user says yes
The user asked for a job; they have not yet seen the shape of it. Never author a plan, never
run mini job new, before they agree to the breakdown. Put in front of them:
- The task breakdown — 2–6 tasks, each with a one-line goal, in the order they must run. Say what each task hands the next one. If you cannot break the work into tasks that stand alone with only the previous diff as context, say so — that work belongs inline, not in a job.
- The gates you would wire — at minimum a
pre_plan/minimise:review-planhook. - The ask — "Want me to set this up as a mini job, or just do it here?"
Then wait. If the user says no, do the work inline without further mention of minimise.
On a yes
- Author the plan YAML. Schema, required fields, and the hook contract:
reference/plan-schema.md. Read it —estimated_duration_minis required on every task and hook, and a plan missing it fails atmini job new. Write it toworklogs/scratch/if that exists, otherwise a plans dir the project already uses (docs/plans/), otherwise ask where it should live. Do not drop YAML in the repo root. - Wire the review-plan gate — a plan-level
pre_hooksentry running/minimise:review-plan(exact shell string in the reference). It is a blocking gate: a failing review aborts the job before any task runs. - Show the user the plan file before running it. It is theirs to edit.
- Run it:
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 8d ago First seen · 62 lines · 30 tokens per session scan A 112de8231518
job is a skill published in the GitHub repository dosatos/minimise (11 stars, last pushed 19d ago), licensed MIT. It adds 30 tokens to every session and 811 once invoked, about $0.0002 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.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…