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/subhansh-dev/agent-maxxing/code-simplifynpx skills add subhansh-dev/agent-maxxing --skill code-simplifygit clone --depth 1 https://github.com/subhansh-dev/agent-maxxingWhat 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.00025 | $0.00329 |
| Opus 5 | $0.00013 | $0.00164 |
| Sonnet 5 | $0.00005 | $0.00066 |
| Haiku 4.5 | $0.00003 | $0.00033 |
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 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.
What it actually says
Code Simplify — 4-Angle Cleanup
Extracted from Claude Code's bundled simplify skill.
You are improving the quality of changed code, not hunting for bugs. Review for reuse, simplification, efficiency, and altitude issues, then fix what you find.
Phase 0 — Gather the diff
Run git diff @{upstream}...HEAD to get the unified diff. If uncommitted changes exist, also run git diff HEAD.
Phase 1 — Review (4 cleanup angles)
Reuse
Flag new code that re-implements something the codebase already has. Grep shared/utility modules and name the existing helper to call instead.
Simplification
Flag unnecessary complexity: redundant or derivable state, copy-paste with slight variation, deep nesting, dead code left behind. Name the simpler form.
Efficiency
Flag wasted work: redundant computation or repeated I/O, independent operations run sequentially, blocking work on startup or hot paths. Name the cheaper alternative.
Altitude
Check that each change is implemented at the right depth, not as a fragile bandaid. Special cases layered on shared infrastructure = fix isn't deep enough. Prefer generalizing the underlying mechanism.
Phase 2 — Apply fixes
Fix each finding directly. Skip any fix that would change intended behavior, require changes outside the reviewed diff, or is a false positive. Finish with a summary of what was fixed and what was skipped.
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 · 37 lines · 25 tokens per session scan A 2cb49235699d
code-simplify is a skill published in the GitHub repository subhansh-dev/agent-maxxing (2 stars, last pushed 1mo ago), licensed MIT. It adds 25 tokens to every session and 329 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-31.
Other skills, from other repositories
feishu
Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.
interview
Ask one useful structured question at a time only when material product/implementation choices are genuinely missing; remember answers and produce a brief/spec. Discoverable facts should be investigated instead of asked.
writing
将共享历史中的已验证事实和计算结果整理成符合受众、格式与长度约束的成稿。.
test
Detect the project’s test stack, run the narrowest useful tests, create tests when authorized, and report coverage/gaps honestly.
verify
Exercise the real app/API/CLI and collect observable evidence; tests alone do not count as end-to-end verification.
build-teaql-app
Build or change a TeaQL application in Java, Rust, Go, Swift, Python, C#/.NET, or TypeScript, including Kotlin/JVM applications that consume Java-generated libraries. Mandatory order: first draft and save a complete KSML model, then verify the client and evaluate that saved model, repair it through repeated evaluation…