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/outlinedriven/odin-claude-plugin/simplifynpx skills add OutlineDriven/odin-claude-plugin --skill simplifygit clone --depth 1 https://github.com/OutlineDriven/odin-claude-pluginWrote 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/outlinedriven/odin-claude-plugin/simplify)<a href="https://agentmods.dev/skills/outlinedriven/odin-claude-plugin/simplify"><img src="https://agentmods.dev/badge/skills/outlinedriven/odin-claude-plugin/simplify.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.00065 | $0.01614 |
| Opus 5 | $0.00032 | $0.00807 |
| Sonnet 5 | $0.00013 | $0.00323 |
| Haiku 4.5 | $0.00006 | $0.00161 |
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 yesterday.
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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Simplify: axis-decomposed compression pass on a diff
Contract
| Field | Bound contract |
|---|---|
| Trigger | User asks to simplify a diff, PR, or branch: "simplify this diff", "tighten up", or "compress a change-set" |
| Authority | reversible-local: write only named local artifacts (working-tree and VCS commits); rollback via git revert HEAD --no-edit |
| Side effect | Applies simplification survivors as atomic issue-class commits to the working change-set; auto-reverts any commit that regresses |
| Done | Exit 0: simplification landed as issue-class commits, every fix commit is green, and no new bloat was introduced |
Inputs
Must be supplied:
- An explicit diff scope or a base ref resolvable from HEAD
Optional:
- User-named files when no git context exists (unborn HEAD or no
.git/)
Derived from the diff:
- Three parallel read-only review agents (reuse / quality / efficiency), each scoped to the diff
Procedure
-
Phase 1: Detect diff scope. Capture every commit since the branch diverged from its base, including staged and unstaged changes. Do not guess the base. Resolve via the first base ref that exists, then run
git diff <base>:git merge-base HEAD origin/maingit merge-base HEAD origin/mastergit merge-base HEAD maingit merge-base HEAD master@{upstream}
If none of the five resolve, gate on two ordered checks:
- Check A:
git rev-parse --verify HEAD 2>/dev/null. If it fails, HEAD is unborn. Skipgit diff; fall through to user-named files or no-git-context path. - Check B: only if Check A succeeded,
git rev-parse --verify HEAD^ 2>/dev/null. If it fails, HEAD is the root commit. Usegit diff HEAD. Surface: "scope: working-tree only, on root commit". - Otherwise: committed history exists but no base ref resolves. Print an explicit error and abort. Do not fall back to
git diff HEAD; that would silently drop committed work.
If no git context or HEAD is unborn, use user-named files supplied in the invocation. Empty after all valid resolutions → exit 11.
What ships with it
5 files 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.
- yesterday First seen · 91 lines · 65 tokens per session scan A 21ee4a5b7952
simplify is a skill published in the GitHub repository OutlineDriven/odin-claude-plugin (35 stars, last pushed yesterday), licensed Apache-2.0. It adds 65 tokens to every session and 1,614 once invoked, about $0.0003 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-09-04.
Other skills, from other repositories
java-commit
Generates a Conventional Commits message for staged Java changes. Use when user asks to "write a commit message", "help me commit", "what should my commit say", "summarize my changes", "draft a commit", or "create commit message".
claude-code-bash-patterns
Claude Code Bash tool patterns with hooks, automation, git workflows. Use for PreToolUse hooks, command chaining, CLI orchestration, custom commands, or encountering bash permissions, command failures, security guards, hook configurations.
slop-scan
Use when scanning tracked repository files for AI slop, verbosity, brittle references, or low-value contributions.
worktrees
Use when fanning several tickets into parallel branches and git worktrees, with related tickets grouped together.
weave-fix-review
Fix weave review findings — validate, add test coverage, fix, and commit each as atomic changes.
action
Use when screened review findings should be fixed on the current branch, usually as one verified commit per finding.