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 giang6283623/minimal-vibe-coding-kit --skill prompt-sharpenergit clone --depth 1 https://github.com/giang6283623/minimal-vibe-coding-kitWrote 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/giang6283623/minimal-vibe-coding-kit/prompt-sharpener)<a href="https://agentmods.dev/skills/giang6283623/minimal-vibe-coding-kit/prompt-sharpener"><img src="https://agentmods.dev/badge/skills/giang6283623/minimal-vibe-coding-kit/prompt-sharpener.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.00034 | $0.00830 |
| Opus 5 | $0.00017 | $0.00415 |
| Sonnet 5 | $0.00007 | $0.00166 |
| Haiku 4.5 | $0.00003 | $0.00083 |
Grade A, and why
prompt-sharpener 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 6d 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 — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Prompt Sharpener
The text the user types after the invocation is the raw prompt. Upgrade it into a prompt that is sharper, not longer - keep the original intent, constraints, and language - then execute the upgraded version immediately in the same turn. No text after the invocation → ask the user what they want and stop.
Step 1 - Diagnose the raw prompt
Scan for every ailment below; each ailment found gets its cure applied directly in the upgraded prompt. Cure silently; call out a cure only when it could shift the user's intent.
- Vague verbs or adjectives ("help me", "make it nicer") → concrete, measurable operations and parameters.
- Two tasks in one prompt → split into an explicit execution order.
- No success criteria → add a binary pass/fail
Done when. - Emotional description ("everything is broken") → extract the specific technical symptom.
- "The whole app" scope → pin exact files/functions/directories; coding tasks always get a scope lock (edit only inside X, leave the rest untouched).
- Relies on memory of an old session → copy the decisions already settled in this conversation (stack, architecture, what was tried and failed) into the
Contextblock. - Invitation to fabricate ("what do experts say about X?") → anchor grounding: state only what can be verified; when unsure, say so explicitly.
- No output format → fix the structure and length; when the format is hard to describe in words, include 2-3 sample examples (including an edge case) in the
Output Contract.
Done when: the raw prompt has been checked against the full list and no ailment is left without its cure in the upgraded prompt.
Step 2 - Build the upgraded prompt
Classify the task (coding / research / writing / analysis / planning / review), then assemble blocks in this order - add a block only when it raises precision; small tasks need just 2-3 blocks:
Objective → Context → Work Style → Tool Rules → Output Contract → Verification → Done Criteria
Focus per task type:
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.
- 6d ago First seen · 55 lines · 34 tokens per session scan A d001b35b8870
prompt-sharpener is a skill published in the GitHub repository giang6283623/minimal-vibe-coding-kit (21 stars, last pushed 9d ago), licensed MIT. It adds 34 tokens to every session and 830 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-30.
Other skills, from other repositories
llm-app-patterns
Production-ready patterns for building LLM applications. Covers RAG pipelines, agent architectures, prompt IDEs, and LLMOps monitoring. Use when designing AI applications, implementing RAG, building agents, or setting up LLM observability.
prompt-optimization
Improve a prompt on the evaluations workbench through a measured loop. Score the baseline first, then duplicate the target column, form a hypothesis from failing rows, edit the copy's prompt draft, run, compare pass rate and cost, and repeat until the numbers hold. Use when the user asks to optimize or improve a…
enhance-prompt
Transforms vague UI ideas into polished, Stitch-optimized prompts. Enhances specificity, adds UI/UX keywords, injects design system context, and structures output for better generation results.
prompt-engineer
Writes, refactors, and evaluates prompts for LLMs — generating optimized prompt templates, structured output schemas, evaluation rubrics, and test suites. Use when designing prompts for new LLM applications, refactoring existing prompts for better accuracy or token efficiency, implementing chain-of-thought or few-shot…
seedance-vocab-en
This skill should be used when an English Seedance 2.0 prompt is slop-heavy, generic, padded with empty quality words, tripping false-positive filters, or needs precise English production vocabulary for camera, lighting, motion, VFX, audio, and constraints.
ideogram4
Prompting patterns for Ideogram 4 text-to-image — best-in-class in-image text rendering and exact color/layout control via structured JSON captions. Use when generating images that need legible on-image text (title cards, thumbnails, logos, signage, CTAs), precise brand colors, or controlled spatial layout. Triggers…