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 delist-after-reconcile-enforcementgit 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/delist-after-reconcile-enforcement)<a href="https://agentmods.dev/skills/ychampion/cskill-agents/delist-after-reconcile-enforcement"><img src="https://agentmods.dev/badge/skills/ychampion/cskill-agents/delist-after-reconcile-enforcement/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/delist-after-reconcile-enforcement"><img src="https://agentmods.dev/badge/skills/ychampion/cskill-agents/delist-after-reconcile-enforcement.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.00028 | $0.00311 |
| Opus 5 | $0.00014 | $0.00156 |
| Sonnet 5 | $0.00006 | $0.00062 |
| Haiku 4.5 | $0.00003 | $0.00031 |
Grade A, and why
delist-after-reconcile-enforcement 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 12d 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: Delist-After-Reconcile Enforcement
Domain: extensions-mcp Trigger: Use when an extension or plugin system must enforce removals even if the install or update pass made no additions. Source Pattern: Distilled from reviewed post-sync extension policy enforcement flows.
Core Method
Apply delist or policy enforcement after synchronization finishes so removal decisions operate on the freshest materialized state. Treat removals as first-class changes that update metrics and propagate the same downstream refresh signal used for installs. This keeps policy enforcement visible and ensures callers reload when the live set changed through removal rather than addition.
Key Rules
- Run delist checks after synchronization, not before, so policy decisions see the latest installed state.
- Count removals explicitly and include them in change metrics.
- Let removals flip the same downstream changed flag or refresh contract used by installs and updates.
Example Application
If a headless bootstrap finds that one installed extension was later delisted, remove it after registry sync and return a changed signal so the command surface reloads.
Anti-Patterns (What NOT to do)
- Do not hide removals as silent cleanup.
- Do not skip delist enforcement when no new installs occurred.
- Do not keep separate refresh paths for installs and removals when both affect the live set.
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.
- 12d ago First seen · 28 lines · 28 tokens per session scan A a0f6f1173f96
delist-after-reconcile-enforcement is a skill published in the GitHub repository ychampion/cskill-agents (36 stars, last pushed 5mo ago), licensed MIT. It adds 28 tokens to every session and 311 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
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.
fix
Dispatch fix subagent for FIX-FIRST gaps from review, re-review, then diagnose unresolved failures after 2 loops.
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.