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 statuslinegit 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/statusline)<a href="https://agentmods.dev/skills/kangig94/coral/statusline"><img src="https://agentmods.dev/badge/skills/kangig94/coral/statusline/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/kangig94/coral/statusline"><img src="https://agentmods.dev/badge/skills/kangig94/coral/statusline.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Rogue Agent · line 65 Skill modifies its own code, configuration, or behavior at runtime. Self-modification enables an agent to escalate privileges, disable safety constraints, or install persistent backdoors.Fix: Prevent the skill from modifying its own code, SKILL.md, or configuration files. Treat skill files as read-only at runtime.
- medium Rogue Agent · line 22 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00010 | $0.01179 |
| Opus 5 | $0.00005 | $0.00589 |
| Sonnet 5 | $0.00002 | $0.00236 |
| Haiku 4.5 | $0.00001 | $0.00118 |
Grade A, and why
statusline 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 9d 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 — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Coral Statusline
Manage the coral HUD statusline for Claude Code.
Commands
Config directories:
CONFIG_DIR= the Claude config dir reported in the SessionStart context.CODEX_DIR= absoluteCODEX_HOMEwhen set, otherwise~/.codex. Use each directory consistently for its provider.
install
- Check if
CONFIG_DIR/hud/coral-hud.mjsalready exists:- If exists and content matches
coral-hud.mjsin this skill directory: inform user "HUD is already up to date", skip to step 6 - If exists with different content: inform user "Updating HUD script to latest version", proceed
- If not exists: proceed
- If exists and content matches
- Read
coral-hud.mjsfrom this skill directory and write it toCONFIG_DIR/hud/coral-hud.mjs(createCONFIG_DIR/hud/directory if needed) - Read
CONFIG_DIR/settings.json(create if absent) - If
statusLinealready exists and is NOT coral's, ask the user before overwriting - Set
statusLineto:
Expand{ "statusLine": { "type": "command", "command": "node CONFIG_DIR/hud/coral-hud.mjs" } }CONFIG_DIRto its absolute path (and~to the real home directory). - Check if
CODEX_DIR/auth.jsonexists:- If yes, ask the user: "Codex login detected. Display Codex usage in statusline?"
- yes → create
CONFIG_DIR/hud/.coral-codex-enabled(empty file — the sameCONFIG_DIR/hudas step 2; do not write this to~/.claudewhenCONFIG_DIRdiffers) - no → delete
CONFIG_DIR/hud/.coral-codex-enabledif it exists
- yes → create
- If no
auth.json, skip silently (do not create or delete any Codex files)
- If yes, ask the user: "Codex login detected. Display Codex usage in statusline?"
- Confirm installation to the user
uninstall
- Read
CONFIG_DIR/settings.json - Remove the
statusLinekey - Delete the following files if they exist:
CONFIG_DIR/hud/coral-hud.mjsCONFIG_DIR/hud/.coral-cache.jsonCONFIG_DIR/hud/.coral-codex-enabled- regular files in
CONFIG_DIR/hudwhose basename matches exactly^\.coral-codex-[0-9a-f]{12}-cache\.json$ - regular files in
CONFIG_DIR/hudwhose basename matches exactly^\.coral-codex-[0-9a-f]{12}\.lock$Do not follow symlinks or delete any broader.coral-*pattern.
- Confirm removal to the user
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 9d ago First seen · 79 lines · 10 tokens per session scan A 0f5dc652b9e8
statusline is a skill published in the GitHub repository kangig94/coral (11 stars, last pushed today), licensed MIT. It adds 10 tokens to every session and 1,179 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…