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/kangig94/coral/code-simplifynpx skills add kangig94/coral --skill code-simplifygit clone --depth 1 https://github.com/kangig94/coralWhat 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.00023 | $0.02441 |
| Opus 5 | $0.00012 | $0.01221 |
| Sonnet 5 | $0.00005 | $0.00488 |
| Haiku 4.5 | $0.00002 | $0.00244 |
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 2d 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 — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Simplification
Simplify and refine code for clarity and maintainability while preserving functionality.
Argument Routing
| Argument | Mode |
|---|---|
<prompt> |
Self-execute on current host (default) |
--delegate |
Delegate to the other host (Claude → Codex, Codex → Claude, Copilot → Codex; current host comes from SessionStart Current host:) |
--delegate <prompt> |
Same with prompt |
Strip the --delegate flag before passing the prompt to the execution path.
<Code_Simplifier> You are an expert code simplification specialist focused on enhancing code clarity, consistency, and maintainability while preserving exact functionality. You prioritize readable, explicit code over overly compact solutions. <Success_Criteria> - All functionality preserved — no behavioral changes - Code passes existing tests before and after simplification - Build succeeds after changes - Every change traces to a clear simplification principle (reduced nesting, eliminated redundancy, improved naming, etc.) - Project coding standards (from CLAUDE.md) are respected </Success_Criteria> NEVER change what the code does — only how it does it.
Clarity is the primary metric — not brevity, not line count, not "modern" style. If the original code is already clear and intentional, leave it alone.
"No change" is a valid result. If a file is already clear and intentional, skip it.
Do not force changes to justify being invoked.
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.
- 2d ago First seen · 149 lines · 23 tokens per session scan A 7c68add74f31
code-simplify is a skill published in the GitHub repository kangig94/coral (11 stars, last pushed 2d ago), licensed MIT. It adds 23 tokens to every session and 2,441 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
deployment
This skill should be used when shipping an app to production — setting up CI/CD, deploys, preview environments, error monitoring, environment separation, or rollback. Trigger phrases include "deploy this", "set up CI/CD", "GitHub Actions", "add error tracking", "set up Sentry", "monitor production", "staging…
api-design
This skill should be used when designing or building an API — endpoints, routes, request/response shapes, error formats, pagination, versioning, or deciding REST vs GraphQL. Trigger phrases include "design the API", "build an endpoint", "REST or GraphQL", "how should I structure my routes", "API error format"…
architecture-primer
This skill should be used when the user wants to design, plan, or decide the architecture of a system, app, or platform from scratch. Trigger phrases include "how do I structure this", "what architecture should I use", "how does this scale", "monolith or microservices", "what database", "what stack", "design the…
saas-router
This skill should be used FIRST whenever the user wants to create, build, design, ship, or prototype any digital product — a SaaS, web app, platform, MVP, landing page, sales page, dashboard, admin panel, backoffice, internal tool, API, database, auth, payments, or any user interface. Trigger phrases (English) include…
ui-design
This skill should be used when making visual design decisions, creating components, defining styles, colors, typography, spacing, or building any interface — including dashboards, admin panels, and web apps. Trigger phrases include "design the UI", "build a component", "pick colors", "create a design system", "make it…
auth
This skill should be used when adding authentication or authorization to an app or SaaS — login, signup, sessions, tokens, roles, permissions, multi-tenant access, SSO, or social login. Trigger phrases include "add login", "add auth", "sign in with Google", "protect this route", "user roles", "admin permissions", "JWT…