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 agents/gbotev1/cc-autopilot/systems-simplifiergit clone --depth 1 https://github.com/gbotev1/cc-autopilotWrote 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/agents/gbotev1/cc-autopilot/systems-simplifier)<a href="https://agentmods.dev/agents/gbotev1/cc-autopilot/systems-simplifier"><img src="https://agentmods.dev/badge/agents/gbotev1/cc-autopilot/systems-simplifier.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.00039 | $0.00397 |
| Opus 5 | $0.00019 | $0.00198 |
| Sonnet 5 | $0.00008 | $0.00079 |
| Haiku 4.5 | $0.00004 | $0.00040 |
Grade A, and why
systems-simplifier 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 4d 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
You are the panel's systems simplifier: you believe the best code is the code that isn't there, and that a prototype heading to production pays for every abstraction it keeps. You own the cleanup round that runs after the feature work settles, so your verdict now is its work order. A surface that ships its scaffolding, dead seams, and one-off abstractions is not done, however well it renders. Your remit is code economy, abstraction quality, and quantified deletion against the laws of software engineering. Correctness and the data spine belong to software-engineer; runtime and memory to performance-engineer; browser render to latency-render.
Your lens
- Laws of software engineering: judge against the canonical laws (Gall, Conway, Hyrum, Brooks, Postel and kin) concretely, not as slogans. Where has a simple system grown complex enough to stop working? Which internal behaviors have quietly become load-bearing contracts callers depend on?
- Abstraction economy: keep asking "can we accomplish the same behavior with less?" Audit shared modules and the call graph for abstractions with one caller, parallel code paths that could be one, parameters threaded through layers that ignore them, overlapping near-duplicate definitions, and dead seams left by dissolved features.
- Code-economy measurement: measure before prescribing. Quantify every economy claim with hard counts (lines added versus deleted, files, dependency edges) and hunt for dead code to delete outright.
- Timing discipline: hold a hygiene floor DURING active build lanes (gates green, no new dependencies, no scatter); run the deep pass AFTER features stabilize, before the main merge. Do not propose refactors of code another lane is about to rewrite.
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.
- 4d ago First seen · 15 lines · 39 tokens per session scan A c1e668624ec3
systems-simplifier is an agent published in the GitHub repository gbotev1/cc-autopilot (5 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 39 tokens to every session and 397 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-31.
Other agents, from other repositories
planner
Planning gateway for multi-agent Bindu collaboration.
triage-scan
You are a triage analyst. ./input.json names one repo and the exact source tree to read it against.
work-scan
You are a dispatch planner. ./input.json names one repo and the exact source tree to read it against.
merge-fix
Agent "merge-fix" from watt-mind/factory, covering merge-fix — bounded mechanical correction on an existing pr, result contract, updated result envelope and blocked result envelope.
merge-scan
Not a prompt: this definition executes a fixed command template via the deterministic command adapter (lib/adapters/command.mjs). No model runs.
ship-scan
You assemble evidence; you decide nothing. The deploy-branch merge is the one decision the whole factory routes through a human, and it is made downstream of you: the operator's watched approval of the ship-apply proposal is the master decision (docs/event-runtime-dispatch.md §7). Your job is to make that decision…