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 EzraApple/skills-init --skill simplifygit clone --depth 1 https://github.com/EzraApple/skills-initWrote 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/ezraapple/skills-init/simplify)<a href="https://agentmods.dev/skills/ezraapple/skills-init/simplify"><img src="https://agentmods.dev/badge/skills/ezraapple/skills-init/simplify/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/ezraapple/skills-init/simplify"><img src="https://agentmods.dev/badge/skills/ezraapple/skills-init/simplify.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.00024 | $0.00309 |
| Opus 5.5 | $0.00010 | $0.00124 |
| Sonnet 5.5 | $0.00005 | $0.00062 |
| Haiku 4.5 | $0.00002 | $0.00031 |
Grade A, and why
simplify 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 18d 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
Reduce the work needed to understand and safely change the code. Line count is only a clue: fewer layers with more hidden state can be harder to maintain.
Trace the behavior and real callers before deleting a boundary. Find decisions that are duplicated, values renamed across layers, state kept in sync with derivable values, and wrappers that only forward arguments.
Prefer the direct version when it stays clear. Consolidate ownership and remove unneeded paths before adding an abstraction. A helper earns its place by naming a coherent operation, hiding a real boundary, or removing meaningful repetition. Single use alone is not a reason to inline it.
Pass an existing domain value through unchanged when it already represents what the next operation needs. Keep translation where it protects a real wire, storage, or public contract. Merge paths only when their invariants and failure behavior match; shared syntax is not enough.
Keep mutable state in the smallest useful scope. Derive values instead of maintaining parallel copies. Replace scattered conditionals with a domain model only when it removes invalid states or repeated rules.
For a requested implementation, make the smallest behavior-preserving change and check the affected contract. For review, report the concrete simplification, its benefit, and any compatibility cost. Leave complexity that represents a real domain constraint; a forced abstraction or rewrite is not a simplification.
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.
- 18d ago Changed · -195 lines · -23 tokens per session 41e07c431594
- 2mo ago First seen · 228 lines · 47 tokens per session scan A f148330af721
simplify is a skill published in the GitHub repository EzraApple/skills-init (2 stars, last pushed 19d ago), licensed MIT. It adds 24 tokens to every session and 309 once invoked, about $0.0001 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-31.
Other skills, from other repositories
go-testing
Trigger: Go tests, go test coverage, Bubbletea teatest, golden files. Apply focused Go testing patterns.
design-review
Five-dimension design audit (frontend UI/UX · server data-model & flow · endpoint spec · daemon-runtime/SDK & local-cache-first · built-in skill/agent-role), executed by a NON-implementing agent. Every dimension gets a verdict; N/A only with a stated reason. A dimension the design silently skipped must be surfaced as…
codebase-design
Design maintainable module interfaces, review scoped code changes, and simplify implementations with behavioral verification. Use for code review, cleanup, testability, and module design work.
review-work
Post-implementation gate review: run manual QA on the real surface yourself, then launch ONE gate reviewer (never a panel) to audit goal, constraints, code quality, security, missed context, and QA evidence. Use before a PR handoff or when the user explicitly asks to review completed work.
tech-lead/code-review
A checklist-based method for examining code for correctness, security, performance, clarity, and ease of maintenance.
pr-blocker-summarizer
Summarizes open pull requests into a blockers-first standup digest. Activates when the user asks to summarize open PRs, find blocked pull requests, generate a PR standup, or triage review backlog from a PR export.