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 AyushParkara/syntra --skill code-simplifygit clone --depth 1 https://github.com/AyushParkara/syntraWrote 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/ayushparkara/syntra/code-simplify)<a href="https://agentmods.dev/skills/ayushparkara/syntra/code-simplify"><img src="https://agentmods.dev/badge/skills/ayushparkara/syntra/code-simplify/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/ayushparkara/syntra/code-simplify"><img src="https://agentmods.dev/badge/skills/ayushparkara/syntra/code-simplify.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00032 | $0.00266 |
| Opus 5.5 | $0.00013 | $0.00106 |
| Sonnet 5.5 | $0.00006 | $0.00053 |
| Haiku 4.5 | $0.00003 | $0.00027 |
Grade A, and why
code-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 1mo 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 simplify code. The behavior must stay identical — this is cleanup only, not a rewrite.
What to improve (in priority order):
- Remove duplication — extract repeated logic into one shared function.
- Flatten nesting — replace deep if/else pyramids with early returns/guards.
- Clarify names — rename cryptic variables/functions to say what they are.
- Delete dead code — unused vars, unreachable branches, commented-out cruft.
- Simplify expressions — collapse redundant booleans, ternaries, conversions.
- Reduce surface — fewer params, smaller functions doing one thing.
Hard rules:
- NEVER change observable behavior. Same inputs → same outputs, same side effects.
- Don't add features, don't "improve" logic, don't change public APIs.
- If a simplification would alter behavior, STOP and flag it instead of doing it.
- Prefer the smallest set of changes that meaningfully improves clarity.
Output: Show before/after for each change and state what got simpler and why.
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.
- 1mo ago First seen · 24 lines · 32 tokens per session scan A 90736fb8d0ab
code-simplify is a skill published in the GitHub repository AyushParkara/syntra (5 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 32 tokens to every session and 266 once invoked, about $0.0001 per session on Opus 5.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 skills, from other repositories
review-harness
Use when reviewing implementation work that ran through a /tmp Pi task harness. Checks contract drift, unsafe shortcuts, validation evidence, and status honesty.
gh-find-prs
Survey open Codewhale PRs and triage each for mergeability and disposition against the real landing branch.
review
Diff-scoped correctness review that reads the codebase around the change — callers, contracts, and invariants — and returns line-anchored findings ranked by severity with confidence, then a merge-risk verdict. Use for reviewing a PR, diff, or named change set. Not for style review, approvals-as-rubber-stamp, or…
simplify
Review recent code changes for reuse, code quality, and efficiency, then directly apply straightforward cleanup improvements. Use when the user wants a post-implementation cleanup pass, pre-PR polish, or asks to simplify/refine recent changes. Invoke with /simplify or /simplify .
cw-slice
Use before writing code for any Codewhale feature, upgrade, or refactor: find the existing owner of the behavior, bound the change to one reviewable slice, and fix the evidence bar before you start.
simplify
Improve clarity and reduce needless complexity after behavior is understood; preserve behavior and keep cleanup separate from correctness fixes.