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 agentmods add skills/clawnify/greybeard/check-resolvablenpx skills add clawnify/greybeard --skill check-resolvablegit clone --depth 1 https://github.com/clawnify/greybeardWrote 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/clawnify/greybeard/check-resolvable)<a href="https://agentmods.dev/skills/clawnify/greybeard/check-resolvable"><img src="https://agentmods.dev/badge/skills/clawnify/greybeard/check-resolvable.svg" alt="Measured on agentmods" 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 | $0.00047 | $0.00783 |
| Opus 5 | $0.00023 | $0.00392 |
| Sonnet 5 | $0.00009 | $0.00157 |
| Haiku 4.5 | $0.00005 | $0.00078 |
Grade A, and why
check-resolvable 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 5d 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.
How it starts
The opening of the file, as written. The whole thing — 47 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Check Resolvable
Audit the entire skill/tool registry and report whether it is a clean resolver: every capability reachable by name, nothing duplicated, nothing overlapping, nothing missing. Run it whenever the library changes — especially right after skillify adds something new.
"I run check resolvable, which is — look at all the other skills and tools that exist, and is it DRY (don't repeat yourself) and is it MECE (mutually exclusive, collectively exhaustive)? It's bad to have ten skills that do the same thing. It's good to have one skill or one tool that has parameters." — Pete Koomen / Andrej Karpathy, YC
The two tests
DRY — don't repeat yourself. No two skills should do the same job. If two skills differ only in a value (one emails Slack, one emails Discord), that's one skill with a parameter. Collapse near-duplicates; don't tolerate them.
MECE — mutually exclusive, collectively exhaustive.
- Mutually exclusive: each skill owns a distinct job. Given a task, exactly one skill is the obvious choice — no "which of these three do I use?" ambiguity.
- Collectively exhaustive: every skill is reachable from the resolver (the index the agent reads), and the index covers the real surface of work — no orphan skill files, no silent gaps.
Procedure
-
Enumerate. List every skill (e.g.
skills/*/SKILL.md) and every entry in the resolver index (AGENTS.md/CLAUDE.mdskills list / tool registry). -
Cross-check index ↔ files. Flag:
- Skills on disk with no resolver entry (unreachable — invisible to the agent).
- Resolver entries pointing at missing files (dead links).
-
DRY pass. Group skills by what they actually do (read the
description+ procedure, not just the name). For each group with overlap, propose the merge: which becomes the canonical skill, what parameter absorbs the difference, which files to delete. -
MECE pass. For each remaining skill, confirm its job is distinct and its trigger ("use when …") doesn't collide with another's. Flag pairs whose triggers overlap — they'll cause the agent to pick wrong. Note obvious gaps in coverage.
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.
- 5d ago First seen · 47 lines · 47 tokens per session scan A 2003c4fa5391
check-resolvable is a skill published in the GitHub repository clawnify/greybeard (7 stars, last pushed today), licensed MIT. It adds 47 tokens to every session and 783 once invoked, about $0.0002 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
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.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…