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 leifericf/agentic-sdk --skill check-claritygit clone --depth 1 https://github.com/leifericf/agentic-sdkWrote 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/leifericf/agentic-sdk/check-clarity)<a href="https://agentmods.dev/skills/leifericf/agentic-sdk/check-clarity"><img src="https://agentmods.dev/badge/skills/leifericf/agentic-sdk/check-clarity.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.1 | $0.00037 | $0.00867 |
| Opus 5 | $0.00018 | $0.00434 |
| Sonnet 5 | $0.00007 | $0.00173 |
| Haiku 4.5 | $0.00004 | $0.00087 |
Grade A, and why
check-clarity 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.
How it starts
The opening of the file, as written. The whole thing — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
check-clarity
Role: review the prose shard for the reader's experience.
Failure model: a reader in the intended audience cannot follow the text on the first read: the structure buries the point, the jargon excludes, or the pacing stalls.
Scope is prose written for humans: design docs, ADRs, reference
material, docstrings surfaced as docs, READMEs, guides. Code is out of
scope; when the shard is code, return NO FINDINGS. The standard is
skills/shared/references/prose-style.md, backed by
skills/shared/references/style-foundations.md. The lint spine task
catches the mechanical tells; this pass catches the clarity judgment a
regex cannot.
Look for
- Audience fit. The text assumes knowledge the intended audience does not have, or over-explains what they already know. Name the audience the design docs declare; judge against that audience, not an idealized expert.
- Buried point. The load-bearing claim sits in the middle of a paragraph or after the evidence, when the reader needs it first. Lead with the point; end on the stress.
- Jargon and undefined terms. A term of art used before its definition, or a term the project's vocabulary defines differently from common usage. The first use earns a definition; later uses inherit it.
- Pacing and paragraph focus. A paragraph that carries more than one idea; a section that circles its point; a sequence of loose sentences where subordination or contraction would carry the same meaning in half the words.
- Signposting and structure. A heading that does not match the section's topic; a cross-reference to a section that does not exist or does not say what is claimed; a list whose items are not parallel in form.
- Missing concrete grounding. A claim stated in the abstract when a named file, type, number, or call site would carry it. General terms where concrete ones serve.
- Unexplained dependency. The text assumes an earlier section the reader has not read, or builds on a decision recorded elsewhere without a pointer. A reader landing mid-document must find the link.
- Passive voice and hidden agency. A sentence that hides who or what acts, when naming the agent would clarify.
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 · 91 lines · 37 tokens per session scan A dad2c28484e8
check-clarity is a skill published in the GitHub repository leifericf/agentic-sdk (5 stars, last pushed 6d ago), licensed MIT. It adds 37 tokens to every session and 867 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…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
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…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…