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/hybridaione/hybridclaw/code-simplificationnpx skills add HybridAIOne/hybridclaw --skill code-simplificationgit clone --depth 1 https://github.com/HybridAIOne/hybridclawWrote 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/hybridaione/hybridclaw/code-simplification)<a href="https://agentmods.dev/skills/hybridaione/hybridclaw/code-simplification"><img src="https://agentmods.dev/badge/skills/hybridaione/hybridclaw/code-simplification.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.00017 | $0.00690 |
| Opus 5 | $0.00009 | $0.00345 |
| Sonnet 5 | $0.00003 | $0.00138 |
| Haiku 4.5 | $0.00002 | $0.00069 |
Grade A, and why
code-simplification 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.
How it starts
The opening of the file, as written. The whole thing — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Simplification
Use this skill for deeper code simplification work while preserving current behavior.
This is intentionally narrower than a generic "simplify" skill: it is for behavior-preserving refactors in a live codebase, with explicit attention to tests, surrounding types, and incremental validation.
Default Workflow
- Identify the exact behavior that must stay the same.
- Read the surrounding code, types, and tests before editing.
- Establish a baseline with the smallest relevant checks.
- Simplify in small reversible steps.
- Re-run validation after each meaningful change.
- Stop when the code is materially clearer, not when it is merely different.
What to Simplify
Prioritize complexity that makes defects more likely:
- deep nesting that can become guard clauses
- duplicated logic that can become one local helper
- conditionals split across too many locations
- wrappers or abstractions with no real caller benefit
- long functions that can be split by responsibility
- state transitions that are hard to follow or partially duplicated
Prefer deleting code over adding a new abstraction when both solve the problem.
Working Rules
- Preserve behavior first; simplification is not a license for feature changes.
- Keep refactors small enough that failures are easy to localize.
- Use existing project patterns instead of inventing a new style.
- Avoid introducing generic helpers until there are at least a few stable call sites that justify them.
- If the code is complex because of a real domain constraint, document that before trying to flatten it away.
Common Moves
Use whichever move makes the code simpler without broad churn:
- convert nested
ifchains into early returns - extract one focused helper from repeated branches
- replace boolean flag tangles with clearer named conditions
- inline one-off wrappers that only obscure data flow
- split data gathering from side effects
- rename unclear variables when the current names hide intent
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 · 103 lines · 17 tokens per session scan A 589278462d47
code-simplification is a skill published in the GitHub repository HybridAIOne/hybridclaw (132 stars, last pushed today), licensed MIT. It adds 17 tokens to every session and 690 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.
Other skills, from other repositories
lilbee-mcp
Search and manage the user's local lilbee knowledge base over MCP. Use whenever the user has indexed code, docs, PDFs, or web pages into lilbee and you need cited answers, or whenever they ask you to ingest content, swap models, or tune retrieval against their library. Every fact returned cites file and line.…
lilbee-mcp-wiki
Wiki layer for lilbee. Use only when the user explicitly asks about wiki / concept / entity / synthesis pages, or when lilbeestatus shows a built wiki. Requires the lilbee-mcp skill to be active for the underlying MCP connection.
m3-health
Health check — package version, installed payload, chatlog DB row count, per-agent hook state.
m3-help
List all m3-memory slash commands / skills and what they do.
m3-forget
Delete a memory permanently. Asks for confirmation first.
m3-status
Chatlog subsystem status — row counts, queue depth, spill, last capture, hook health.