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 progress-event-state-bridgegit 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/progress-event-state-bridge)<a href="https://agentmods.dev/skills/ychampion/cskill-agents/progress-event-state-bridge"><img src="https://agentmods.dev/badge/skills/ychampion/cskill-agents/progress-event-state-bridge/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/progress-event-state-bridge"><img src="https://agentmods.dev/badge/skills/ychampion/cskill-agents/progress-event-state-bridge.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.00027 | $0.00425 |
| Opus 5 | $0.00014 | $0.00212 |
| Sonnet 5 | $0.00005 | $0.00085 |
| Haiku 4.5 | $0.00003 | $0.00042 |
Grade A, and why
progress-event-state-bridge 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 8d 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: Progress Event State Bridge
Domain: plugin-installation
Trigger: Use when background reconciliation emits per-source progress updates and shared UI state must reflect each source's lifecycle (installing, installed, failed).
Source Pattern: Distilled from reviewed install-progress callbacks and immutable UI-state bridge implementations.
Core Method
Let the reconciler emit progress events for each marketplace or extension source, then bridge those events into shared UI state through one immutable update path. Each event should update only the matching source entry, carrying both the new status and any error payload, while leaving unrelated entries untouched. This makes the install UI responsive without forcing broad rerenders or duplicating install logic in the view layer.
Key Rules
- Use one immutable helper or reducer path so only the target entry changes and unrelated UI state keeps structural sharing.
- Preserve the event’s status semantics directly:
installing,installed, andfailedshould remain distinct in the UI state. - If the event carries an error payload, preserve it so the UI can surface meaningful diagnostics.
- Progress events should update previously seeded entries, not silently invent new rows that were never declared to the user.
Example Application
When a background source sync starts, the UI row for that source flips from pending to installing. If the fetch succeeds, it moves to installed; if it fails, it moves to failed and stores the error text for display.
Anti-Patterns (What NOT to do)
- Do not mutate the source list in place or reorder entries when mapping events; unaffected rows should retain reference stability.
- Do not drop the
errorpayload when afailedevent fires; without it, the UI cannot explain why manual intervention is required. - Do not rebuild unrelated state slices while handling these events; keep the bridge scoped to the installation-status surface.
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.
- 8d ago First seen · 30 lines · 27 tokens per session scan A 6d4807f3d7b0
progress-event-state-bridge is a skill published in the GitHub repository ychampion/cskill-agents (36 stars, last pushed 5mo ago), licensed MIT. It adds 27 tokens to every session and 425 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-09-03.
Other skills, from other repositories
grape
Use Grape MCP for Codex context continuity in coding repositories. Use when a task needs repeated-turn context, omitted context restore, stale-context checks, invalidation checks, or safe continuity across branch and dirty-worktree changes.
review
Validate plans, execution, or PRs against wish criteria — returns SHIP / FIX-FIRST / BLOCKED with severity-tagged gaps.
work
Execute an approved wish plan — orchestrate subagents per task group with fix loops, validation, and review handoff.
brainstorm
Explore ambiguous or early-stage ideas interactively — tracks wish-readiness and crystallizes into a design for wish.
genie
Entry point for Genie operations — routes bug reports, questions, and operational commands, resumes existing lifecycle state, and orchestrates work that needs durable planning or coordination. Other ordinary requests bypass the lifecycle with a one-line notice unless the user asks for Genie.
wish
Convert an idea into a structured wish plan with scope, acceptance criteria, and execution groups for work.