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 ychampion/cskill-agents --skill stall-to-alert-color-escalationgit clone --depth 1 https://github.com/ychampion/cskill-agentsWrote 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/ychampion/cskill-agents/stall-to-alert-color-escalation)<a href="https://agentmods.dev/skills/ychampion/cskill-agents/stall-to-alert-color-escalation"><img src="https://agentmods.dev/badge/skills/ychampion/cskill-agents/stall-to-alert-color-escalation/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/ychampion/cskill-agents/stall-to-alert-color-escalation"><img src="https://agentmods.dev/badge/skills/ychampion/cskill-agents/stall-to-alert-color-escalation.svg" alt="Reviewed on agentmods" width="80" 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.00031 | $0.00317 |
| Opus 5.5 | $0.00012 | $0.00127 |
| Sonnet 5.5 | $0.00006 | $0.00063 |
| Haiku 4.5 | $0.00003 | $0.00032 |
Grade A, and why
stall-to-alert-color-escalation 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 1mo 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.
What it actually says
SKILL: Stall-to-Alert Color Escalation
Domain: terminal-ui Trigger: Use when a spinner or progress indicator should warn about stalls without replacing itself with a larger warning UI. Source Pattern: Distilled from reviewed stall-sensitive terminal indicator rendering patterns.
Core Method
Start with the indicator's normal theme color, then interpolate it toward a known alert color as stall intensity rises. If exact color math is unavailable, fall back to a semantic alert token instead of failing. This creates a smooth escalation path that preserves the indicator's footprint while still making degraded states obvious.
Key Rules
- Drive the escalation from a normalized stall intensity rather than fixed hardcoded time branches inside the renderer.
- Keep a safe fallback path when literal color parsing fails.
- Preserve the same spinner or indicator footprint while only changing color and, if needed, subtle glyph intensity.
Example Application
For a long-running build spinner, fade the normal accent color toward red as the system detects a likely stall, while keeping the same single-cell spinner slot.
Anti-Patterns (What NOT to do)
- Do not swap the spinner for a larger banner at the first sign of delay.
- Do not hardcode one threshold and one end-state color without a smooth ramp.
- Do not let stall visuals change the indicator's size or alignment.
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.
- 1mo ago First seen · 28 lines · 31 tokens per session scan A ce3636aea639
stall-to-alert-color-escalation is a skill published in the GitHub repository ychampion/cskill-agents (36 stars, last pushed 6mo ago), licensed MIT. It adds 31 tokens to every session and 317 once invoked, about $0.0001 per session on Opus 5.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-09-03.
Other skills, from other repositories
report
Investigate a failure to its root cause with grounded evidence, hand the diagnosis to fix, and create a GitHub issue only when asked.
static
Stash is your personal home for agent work. Everything you create is scoped to your account — it is yours alone, with nothing to pick or set up first. Your Stash has three primary surfaces.
merge
Resolve an in-progress merge or rebase by the intent of both sides, re-run the full gate on the merged tree, and finish the operation.
tilth
Use the tilth CLI for code reading, outlining, search, callers, blast-radius deps, and structural diffs. Activate when the user asks to explore a repo, find a symbol, trace callers, read a file, view a diff, or analyze impact. Prefer tilth over grep/cat/find/ls — one invocation returns AST-aware outlines, definitions…
fix
Resolve blocking review gaps through bounded repairs and independent re-review; diagnose stalled attempts without expanding scope.
cleanup
Find duplicates, dead links and untagged items in a saved library and propose what to do about each.