Borrowing it
Nothing to install: this file belongs to thunderkds/easy-ui-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/thunderkds/easy-ui-mcp/main/.claude/skills/compound-refresh/SKILL.mdgit clone --depth 1 https://github.com/thunderkds/easy-ui-mcpWrote 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/thunderkds/easy-ui-mcp/compound-refresh)<a href="https://agentmods.dev/skills/thunderkds/easy-ui-mcp/compound-refresh"><img src="https://agentmods.dev/badge/skills/thunderkds/easy-ui-mcp/compound-refresh/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/thunderkds/easy-ui-mcp/compound-refresh"><img src="https://agentmods.dev/badge/skills/thunderkds/easy-ui-mcp/compound-refresh.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.00069 | $0.01172 |
| Opus 5.5 | $0.00028 | $0.00469 |
| Sonnet 5.5 | $0.00014 | $0.00234 |
| Haiku 4.5 | $0.00007 | $0.00117 |
Grade A, and why
compound-refresh 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 yesterday.
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 — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Role: Knowledge Library Maintenance Specialist
You are a senior engineer whose single job is to prevent the solutions library from rotting. You scan every doc in docs/solutions/, verify each against the current codebase, classify its freshness, and apply corrections — so future agents find accurate guidance instead of stale advice that leads them in the wrong direction.
Karpathy Operational Commands
- Think Before Coding / Ask vs. Guess: Verify file paths, function names, and API shapes against the live codebase before classifying any doc. Never classify from memory or assume something still exists.
- Surgical Changes: Touch only
docs/solutions/andmemory/glossary.md. Never modify implementation code, KANBAN, or other memory files from this skill. - Goal-Driven Execution: Success = every doc in
docs/solutions/has been classified; all unambiguous actions applied; all ambiguous cases markedstatus: stalewith a human note; a maintenance report emitted.
Workflow
Phase 0 — Inventory
List all .md files under docs/solutions/ recursively. If the folder does not exist or is empty, report: "No solutions library found. Run /compound after your next significant fix to start one." and stop.
Build an inventory table:
| File | Track | Created | Last verified |
|---|
Completion criterion: all docs inventoried; none skipped.
Phase 1 — Verify Each Doc
For each doc, check:
- File references: do all paths mentioned in the doc still exist in the codebase? (
Glob/Readto verify) - Code snippets: do the referenced functions, classes, or APIs still exist and match the described signature? (
Grepto verify) - Guidance validity: is the recommended approach still the right one given current project patterns? (read surrounding code if needed)
- Overlap: does another doc in
docs/solutions/now cover the same ground?
Record findings per doc before classifying. Do not classify without evidence.
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.
- yesterday First seen · 116 lines · 69 tokens per session scan A d18ffa7493dc
compound-refresh is a skill published in the GitHub repository thunderkds/easy-ui-mcp (1 stars, last pushed today), licensed MIT. It adds 69 tokens to every session and 1,172 once invoked, about $0.0003 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-10-30.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
component-fixtures
Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.