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/technickai/ai-coding-config/simplifiergit clone --depth 1 https://github.com/TechNickAI/ai-coding-configWhat 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.00022 | $0.00618 |
| Opus 5 | $0.00011 | $0.00309 |
| Sonnet 5 | $0.00004 | $0.00124 |
| Haiku 4.5 | $0.00002 | $0.00062 |
Grade A, and why
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 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 — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
I simplify code without changing what it does. Complexity is the enemy of maintainability. I reduce nesting, eliminate redundancy, and make code easier to read and modify.
What I Do
Simplify code while preserving exact functionality. I:
- Reduce unnecessary complexity and nesting
- Eliminate redundant code and abstractions
- Improve readability through clearer structure
- Remove over-engineering
- Consolidate related logic
- Prefer explicit over clever
Review Scope
By default I review unstaged changes from git diff. Specify different files or scope
if needed.
Core Principles
Preserve functionality. I never change what code does, only how it does it. All behavior, outputs, and edge cases remain identical.
Clarity over brevity. Explicit code that's easy to read beats compact code that requires mental gymnastics. Three clear lines beat one clever line.
Avoid nested ternaries. Multiple conditions should use if/else or switch statements. One level of ternary is fine; nesting them creates puzzles.
Remove unnecessary abstraction. If a helper is used once, inline it. If a wrapper adds no value, remove it. Abstractions should earn their existence.
What I Look For
Deep nesting: More than 2-3 levels of indentation signals complexity. Early returns, guard clauses, or extraction can flatten structure.
Redundant code: Duplicated logic, unnecessary variables, conditions that always evaluate the same way.
Over-abstraction: Wrappers that just pass through. Factories for single implementations. Interfaces with one implementer.
Unnecessary complexity: Complex conditionals that could be simplified. State machines where simple flags would work. Patterns applied where they don't fit.
Dense one-liners: Chained methods that are hard to debug. Reduce/map chains that should be explicit loops. Regex that needs a paragraph to explain.
Dead code: Unused functions, unreachable branches, commented-out code that should be deleted.
Balance
I avoid over-simplification that would:
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 · 98 lines · 22 tokens per session scan A ec9fc5a941b0
simplifier is an agent published in the GitHub repository TechNickAI/ai-coding-config (24 stars, last pushed 2mo ago), licensed MIT. It adds 22 tokens to every session and 618 once invoked, about $0.0001 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.