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/bugfixnpx skills add kangig94/coral --skill bugfixgit clone --depth 1 https://github.com/kangig94/coralWrote 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/kangig94/coral/bugfix)<a href="https://agentmods.dev/skills/kangig94/coral/bugfix"><img src="https://agentmods.dev/badge/skills/kangig94/coral/bugfix.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.00020 | $0.00793 |
| Opus 5 | $0.00010 | $0.00396 |
| Sonnet 5 | $0.00004 | $0.00159 |
| Haiku 4.5 | $0.00002 | $0.00079 |
Grade A, and why
bugfix 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 — 46 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bug Debugging
Diagnose bugs, plan fixes, and execute - end-to-end.
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.
Execution
- Diagnose:
- Self-execute (default): Spawn
Agent({ subagent_type: "coral:debugger", prompt: "--deep " + prompt }). Wait for the agent to return its diagnosis in<Output_Format>structure. - Delegate (
--delegate): Runcoral-cli <other-host> debugger -i "<--deep prompt>" --work-dir "<work_dir>" -d(<other-host>= the delegation target for the current host: Claude → Codex, Codex → Claude, Copilot → Codex). CapturejobfromJob <job> <launchState> (session <session>), then runcd "<work_dir>" && coral-cli wait jobs <job> --embed. Classify the result from its rendered output, not exit code75alone:Result path: <path>marks a terminal result, so read that artifact and stop waiting even when a terminalprovider_exitpropagated code75; a status beginningStill waitingwith(cursor: <cursor>)means the job is still live, so resume withcd "<work_dir>" && coral-cli wait jobs <job> --cursor <cursor> --embed. If a transient error instead printsremediation:, run that exact command from the same directory —cd "<work_dir>" && <the printed coral-cli wait jobs command>— sincewaitscopes from the shell's cwd. A non-zeroprovider_exitcode is terminal and is passed through unchanged (0–255). On error, stop with the error message. Verify cited file:line references. Drop findings with incorrect references.
- Self-execute (default): Spawn
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 · 46 lines · 20 tokens per session scan A fde7936870c8
bugfix is a skill published in the GitHub repository kangig94/coral (11 stars, last pushed yesterday), licensed MIT. It adds 20 tokens to every session and 793 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…
secure-coding
This skill should be used while WRITING any backend, API, auth, or data-handling code for a web app or SaaS — to prevent vulnerabilities before they ship, not to audit them after. Trigger phrases include "add an endpoint", "handle user input", "store user data", "is this secure", "build the API", "save to the…
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…