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 SII-Holos/synergy --skill find-simplificationsgit clone --depth 1 https://github.com/SII-Holos/synergyWrote 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/sii-holos/synergy/find-simplifications)<a href="https://agentmods.dev/skills/sii-holos/synergy/find-simplifications"><img src="https://agentmods.dev/badge/skills/sii-holos/synergy/find-simplifications/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/sii-holos/synergy/find-simplifications"><img src="https://agentmods.dev/badge/skills/sii-holos/synergy/find-simplifications.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00082 | $0.03112 |
| Opus 5 | $0.00041 | $0.01556 |
| Sonnet 5 | $0.00016 | $0.00622 |
| Haiku 4.5 | $0.00008 | $0.00311 |
Grade A, and why
find-simplifications 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 9d 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 — 148 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Finding Synergy Simplifications
This skill helps turn a broad "find things to simplify" request into evidence-backed decision records that remove or collapse existing surface area. It is guidance, not a checklist: follow the code, keep judgment active, and prefer a few well-proven candidates over a pile of thin guesses.
Start With Repo Context
- Read the root AGENTS.md — especially the Durable Architecture Boundaries — and the documentation standard. The boundaries listed there are intentional by default; a simplification that collapses one needs to beat the recorded rationale, not just cite churn.
- Skim Architecture overview and Decision records before judging anything under
packages/. Simplifications that fight the runtime vocabulary or the decision-record format need extra evidence. - Read only the relevant owned-domain document: Sessions and messages, LLM loop, Frontend data sync, Execution boundaries, Workflows, Browser runtime, Channels, Cortex, or Plugin documentation.
- Treat the durable boundaries as intentional by default:
guardedas the only standard interactive profile, autonomous-never-asks, worktree isolation semantics, Browser desktop-nativeWebContentsViewand Web WebRTC presentation as first-class modes, andMessageV2.deriveSemantics()as the only source of message semantics. Do not propose deleting any of these as "low effort" unless the user explicitly overrides that constraint. Removing an unused method or hook inside a protected seam can still be valid if it does not collapse the protected design.
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.
- 9d ago First seen · 148 lines · 82 tokens per session scan A 7e0ed2a35298
find-simplifications is a skill published in the GitHub repository SII-Holos/synergy (548 stars, last pushed today), licensed MIT. It adds 82 tokens to every session and 3,112 once invoked, about $0.0004 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
autoreview
Pre-commit/ship code review: Codex default; optional Claude or Pi.
rework-rate
Measure and interpret PR rework rate — the emerging 5th DORA metric.
omh-code-review
This is a Hermes-native code-review workflow skill.
revdiff-plan
Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…
code-reviewer
Code review specialist focused on patterns, bugs, security, and performance.
agent-teams-simplify-and-harden
Implementation + audit loop using parallel agent teams with structured simplify, harden, and document passes. Spawns implementation agents to do the work, then audit agents to find complexity, security gaps, and spec deviations, then loops until code compiles cleanly, all tests pass, and auditors find zero issues or…