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 external-error-preserving-refresh-mergegit 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/external-error-preserving-refresh-merge)<a href="https://agentmods.dev/skills/ychampion/cskill-agents/external-error-preserving-refresh-merge"><img src="https://agentmods.dev/badge/skills/ychampion/cskill-agents/external-error-preserving-refresh-merge/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/external-error-preserving-refresh-merge"><img src="https://agentmods.dev/badge/skills/ychampion/cskill-agents/external-error-preserving-refresh-merge.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.00347 |
| Opus 5 | $0.00014 | $0.00173 |
| Sonnet 5 | $0.00005 | $0.00069 |
| Haiku 4.5 | $0.00003 | $0.00035 |
Grade A, and why
external-error-preserving-refresh-merge 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 10d 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: External Error Preserving Refresh Merge
Domain: plugin-installation Trigger: Use when a refresh path recomputes its own errors but neighboring subsystems maintain related diagnostics that should survive the reload. Source Pattern: Distilled from reviewed refresh-diagnostic ownership and merge implementations.
Core Method
Treat refresh-time errors as one slice of the diagnostic picture rather than the whole state. Preserve errors owned by adjacent subsystems, merge in the freshly computed errors from the current reload, and deduplicate by a stable key so the result stays current without erasing still-relevant external failures. This lets a subsystem update what it owns while respecting error streams maintained elsewhere.
Key Rules
- Preserve only the error sources the current refresh is not authoritative for.
- Build stable dedupe keys from error type and source, not from list position or timing.
- Merge preserved external errors with fresh refresh errors so users see one coherent diagnostic surface.
- Keep the ownership boundary explicit so future refactors know which subsystem may overwrite which errors.
Example Application
If a plugin refresh recomputes loader failures while a language-server manager separately owns connection diagnostics, preserve the language-server errors and merge in the fresh loader errors so the UI retains the full current problem set.
Anti-Patterns (What NOT to do)
- Do not replace the entire error array on every refresh; that silently drops failures from other live subsystems.
- Do not dedupe by array position or timestamp alone; equivalent errors need stable identity.
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.
- 10d ago First seen · 28 lines · 27 tokens per session scan A a3e26ecb984e
external-error-preserving-refresh-merge 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 347 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
fix
Dispatch fix subagent for FIX-FIRST gaps from review, re-review, then diagnose unresolved failures after 2 loops.
report
Investigate bugs comprehensively — cascade through trace, capture browser evidence, extract observability data, and prepare or explicitly create a GitHub issue with grounded findings.
trace
Dispatch trace subagent to investigate unknown issues — reproduces, traces, and reports root cause for fix handoff.
perf
Use when auditing performance in any codebase — cold starts, hot paths, dependency weight, storage query patterns. Assess by default, optimize on request; measure, don't guess, and every number carries the command that produced it.
use-ivygrep
Gather focused local repository context with ivygrep before implementing, debugging, reviewing, or explaining code. Use for coding tasks involving unfamiliar paths, branch changes, stack traces, architectural relationships, callers, dependents, tests, configuration, or documentation. Prefer one bounded context pack…
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.