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 kangig94/coral --skill plangit 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/plan)<a href="https://agentmods.dev/skills/kangig94/coral/plan"><img src="https://agentmods.dev/badge/skills/kangig94/coral/plan.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.1 | $0.00021 | $0.05402 |
| Opus 5 | $0.00010 | $0.02701 |
| Sonnet 5 | $0.00004 | $0.01080 |
| Haiku 4.5 | $0.00002 | $0.00540 |
Grade A, and why
plan 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 6d 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 — 328 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Planning
Execute a multi-round planning session with architect/critic review.
Argument Routing
| Argument | Mode |
|---|---|
<prompt> |
Self-execute on current host (default) |
--delegate |
Add a review pass on <other-host> (see Review Phases for the mapping). On a host that is not itself a provider it replaces Phase 2 rather than adding to it, so the net is still one review phase. |
round=N |
Review rounds for every applicable phase (default 1). e.g. round=3 for deeper iteration. |
round=N,M |
Per-phase budget: Phase 1 (<other-host>) gets N rounds, Phase 2 gets M. Turns --delegate on. |
--no-handoff |
Internal: skip implementation prompt at step 5 (caller controls next step) |
Reviewers and the resolver always run in every review phase that dispatches — the round budget only sets how many times each phase iterates.
Parsing the round budget (round=… and --round=… are the same token):
round=N→ every applicable phase getsN. Does not affect--delegate.round=N,M→{maxRounds[1]}=N,{maxRounds[2]}=M, and--delegateis on whether or not it was written. Phase 1 exists only under--delegate, so naming two budgets IS the request for both phases.- Absent →
1for every phase. - Every value must be an integer ≥ 1. More than two values, a
0, or a non-integer is a usage error: report it and stop. Do not clamp, drop the extras, or fall back to the default.
Strip --delegate, the round token, and --no-handoff before passing the prompt to the execution path.
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.
- 6d ago First seen · 328 lines · 21 tokens per session scan A 0969d556bffc
plan is a skill published in the GitHub repository kangig94/coral (11 stars, last pushed 4d ago), licensed MIT. It adds 21 tokens to every session and 5,402 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…