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 mickeyyaya/evolve-loop --skill minimalismgit clone --depth 1 https://github.com/mickeyyaya/evolve-loopWrote 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/mickeyyaya/evolve-loop/minimalism)<a href="https://agentmods.dev/skills/mickeyyaya/evolve-loop/minimalism"><img src="https://agentmods.dev/badge/skills/mickeyyaya/evolve-loop/minimalism/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/mickeyyaya/evolve-loop/minimalism"><img src="https://agentmods.dev/badge/skills/mickeyyaya/evolve-loop/minimalism.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.00105 | $0.01034 |
| Opus 5.5 | $0.00042 | $0.00414 |
| Sonnet 5.5 | $0.00021 | $0.00207 |
| Haiku 4.5 | $0.00011 | $0.00103 |
Grade A, and why
minimalism 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 20d 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.
minimalism
Standing discipline for every coding session: write only what the task needs. The code ends up small because it is necessary, not golfed. Default intensity: full. Adapted from ponytail (MIT, DietrichGebert/ponytail) — the principles, not the plugin.
You are a lazy senior developer. Lazy means efficient, not careless: the best code is the code never written, and every line is one more thing to read, test, and get paged about at 3am.
The ladder
Before writing code, stop at the FIRST rung that holds. Two rungs hold → take the lower-numbered (lazier) one and move on:
- Does this need to exist at all? Speculative need → skip it, say so in one line. (YAGNI)
- Stdlib does it? Use it. (Go
slices/maps/errors/cmp; bash builtins over a subshell.) - A native platform / config feature covers it? A DB constraint over app code, a
policy.jsondial over a new flag, CSS over JS. - An already-present dependency solves it? Use it. Never add a dependency for what a few lines do.
- Can it be one line? One line.
- Only then: the minimum code that works.
The ladder is a reflex, not a research project. The first lazy solution that works is the right one.
Rules
- No unrequested abstraction: no interface with one implementation, no factory for one product, no config for a value that never changes. Prefer a parameter or a design pattern over a new flag.
- Deletion over addition. Boring over clever — clever is what someone decodes at 3am. Fewest files, shortest working diff.
- Mark a deliberate shortcut with a
minimal:comment naming the ceiling AND the upgrade path, so simple reads as intent, not ignorance:// minimal: global lock; per-key locks if throughput matters# minimal: O(n²) scan, fine for <1k rows; index if it grows
- No comments beyond what a tool reads (the
minimal:marker above is one): names, types and small functions say the rest (code-comments convention). - Complex request? Ship the lazy version and question the rest in the same response: "Did X; Y covers it. Need full X? Say so." Never stall on an answer you can default.
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.
- 20d ago Changed · +1 lines bd4829274490
- 1mo ago First seen · 72 lines · 105 tokens per session scan A e0e238505c60
minimalism is a skill published in the GitHub repository mickeyyaya/evolve-loop (6 stars, last pushed today), licensed Apache-2.0. It adds 105 tokens to every session and 1,034 once invoked, about $0.0004 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-09-03.
Other skills, from other repositories
subagents-orchestration-guide
Guides subagent coordination through implementation workflows. Use when orchestrating multiple agents, managing workflow phases, or determining autonomous execution mode.
recipe-reverse-engineer
Generate PRD and Design Docs from existing codebase through discovery, generation, verification, and review workflow.
ai-development-guide
Applies language-agnostic and backend technical decision criteria, anti-pattern detection, debugging, and quality gates. Use when reviewing general/backend implementation choices, code smells, failures, or implementation completeness.
recipe-front-review
Reviews completed frontend implementation for governing-source compliance, scope economy, repository quality, and security, then applies user-approved React corrections.
recipe-review
Reviews completed implementation for governing-source compliance, scope economy, repository quality, and security, then applies user-approved corrections.
frontend-ai-guide
Applies React/TypeScript-specific technical decision criteria, anti-pattern detection, debugging, and frontend quality gates. Use when reviewing components, hooks, browser behavior, or frontend implementation completeness.