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/reidemeister94/development-skills/simplify-stuffnpx skills add reidemeister94/development-skills --skill simplify-stuffgit clone --depth 1 https://github.com/reidemeister94/development-skillsWrote 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/reidemeister94/development-skills/simplify-stuff)<a href="https://agentmods.dev/skills/reidemeister94/development-skills/simplify-stuff"><img src="https://agentmods.dev/badge/skills/reidemeister94/development-skills/simplify-stuff.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 | $0.00045 | $0.00263 |
| Opus 5 | $0.00023 | $0.00131 |
| Sonnet 5 | $0.00009 | $0.00053 |
| Haiku 4.5 | $0.00005 | $0.00026 |
Grade A, and why
simplify-stuff 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.
What it actually says
simplify-stuff
The argument is the target scope. Run a deep pass that applies the writing contract to existing files:
- Read every file in the scope, plus the files each one references or shares content with — judge a file inside its ecosystem, never alone. Check what points at the scope from outside before restructuring, so no link or section reference breaks.
- Rewrite each file to the contract, deduplicating across the whole scope: each fact lands in its one right home and the other files link to it.
- Verify before finishing: grep that load-bearing specific tokens (names, paths, commands, conventions) survived; confirm nothing active links to removed content; and check the result is both shorter and clearer — when a cut would lose real capability, relocate the content instead of deleting it.
Record what was removed and why in the project's usual decision record, so cuts stay recoverable.
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 · 17 lines · 45 tokens per session scan A c5b249d46564
simplify-stuff is a skill published in the GitHub repository reidemeister94/development-skills (11 stars, last pushed 1mo ago), licensed MIT. It adds 45 tokens to every session and 263 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
mutation-test
Mutation testing with two engines. Uses the project's NATIVE mutation runner (StrykerJS / Infection / mutmut / PIT / cargo-mutants) when one is configured — installing it on explicit consent when it is not — for a reproducible, comparable score; and an LLM-guided engine for the mutation classes native mutators cannot…
refactor
Structured refactoring runner with ETAP workflow, resumable CONTRACT, and batch processing. Use when restructuring code, extracting methods, splitting files, breaking circular dependencies, or cleaning up god classes. NOT for new features (use zuvo:build). Execution modes: full (default), batch (queue processing).…
review
Structured code review with parallel audit agents, confidence-scored triage, and optional auto-fix. Examines uncommitted changes, staged diffs, commit ranges, or specific paths. Produces a tiered report (MUST-FIX / RECOMMENDED / NIT) backed by evidence, then optionally applies fixes with verification.
db-audit
Database performance and safety audit. 70+ checks across 13 dimensions (DB1-DB13): query patterns, indexes, schema design, connections, transactions, migrations, caching, query optimization, ORM anti-patterns, observability, data lifecycle, DB security, and migration deployment safety. Code-level checks for all ORMs.…
write-tests
Write tests for existing production code. Processes ONE file at a time through a full pipeline: analyze, inventory (frozen BEFORE writing), write, executable coverage gate, verify, blind coverage audit, adversarial review, log. Uses CodeSift for discovery and analysis when available. Modes: [path] (specific target)…
brainstorm
Explores a codebase, researches the problem space, and produces an approved design specification before any code is written. Use when the user wants to create a new feature, add significant functionality, redesign a subsystem, or build something that touches multiple parts of the project.