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 hamzafarooq/claude-code-starter --skill sharpengit clone --depth 1 https://github.com/hamzafarooq/claude-code-starterWrote 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/hamzafarooq/claude-code-starter/sharpen)<a href="https://agentmods.dev/skills/hamzafarooq/claude-code-starter/sharpen"><img src="https://agentmods.dev/badge/skills/hamzafarooq/claude-code-starter/sharpen/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/hamzafarooq/claude-code-starter/sharpen"><img src="https://agentmods.dev/badge/skills/hamzafarooq/claude-code-starter/sharpen.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.00079 | $0.00974 |
| Opus 5.5 | $0.00032 | $0.00390 |
| Sonnet 5.5 | $0.00016 | $0.00195 |
| Haiku 4.5 | $0.00008 | $0.00097 |
Grade A, and why
sharpen 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 1mo 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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ask the user:
- "Paste the draft — email, Slack message, exec update, anything you're about to send."
- "Who's reading it, and what do you want them to do after reading?"
If the draft came in with the command, don't ask for it again. Only ask question 2 if the reader and the goal aren't obvious from the draft itself.
Before writing anything, run the draft through the six checks. Answer each one honestly.
The six checks:
- Lead — Is the most important sentence first? Or is it buried under warm-up, apology, and background?
- Ask — Is there one clear request the reader can say yes or no to in a single reply? Is it near the top?
- Context — Can the reader act without sending a follow-up question? And is there background they already know that's just taking up space?
- Hedges — Count them: "just", "I think", "maybe", "might", "sort of", "if possible", "no worries if not", "I could be wrong but", "quick question". Each one tells the reader you're not sure you should be asking.
- Objections — What's the first thing the reader will push back on? Does the draft answer it, or leave it hanging?
- Length — Could this be half as long and lose nothing? Every sentence has to earn its place.
Then produce:
Sharpen
Signal strength: 🔴 Weak / 🟡 Mixed / 🟢 Strong
One sentence on why. E.g. "The ask is clear, but it's the last line of a 200-word email and most readers won't get there."
What's weak, and why
Go check by check. Only list the checks that flagged something. For each one, quote the exact words from the draft, then say what they cost the reader.
- Buried ask — "[quoted line]" → This is the whole point of the message and it's in paragraph 4. The reader has to dig to find out what you want.
- Hedge words — "[just wanted to]", "[I think maybe]" → Three hedges in two sentences. It reads like you expect a no.
- Missing context — The reader doesn't know [X], so they can't answer without asking you first.
- Unaddressed objection — The first thing [reader] will think is "[objection]". The draft doesn't answer it.
- Weak lead — "[opening line]" → Warm-up. The real message starts three sentences later.
- Too long — [N] words to make one point. The reader skims and misses the ask.
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.
- 1mo ago First seen · 73 lines · 79 tokens per session scan A 8e05cd1cd02f
sharpen is a skill published in the GitHub repository hamzafarooq/claude-code-starter (145 stars, last pushed 7d ago), licensed MIT. It adds 79 tokens to every session and 974 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-09-14.
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…
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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.