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/sammcj/agentic-coding/prompt-enhancernpx skills add sammcj/agentic-coding --skill prompt-enhancergit clone --depth 1 https://github.com/sammcj/agentic-codingWrote 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/sammcj/agentic-coding/prompt-enhancer)<a href="https://agentmods.dev/skills/sammcj/agentic-coding/prompt-enhancer"><img src="https://agentmods.dev/badge/skills/sammcj/agentic-coding/prompt-enhancer.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.00067 | $0.01086 |
| Opus 5 | $0.00034 | $0.00543 |
| Sonnet 5 | $0.00013 | $0.00217 |
| Haiku 4.5 | $0.00007 | $0.00109 |
Grade A, and why
prompt-enhancer 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 4d 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 — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Expert Prompt Enhancer
Transform prompts written by non-specialists into the form a domain expert would use to make the same request. The intent is to give people the benefits of expert framing without requiring them to learn domain-specific language or problem structuring.
Expert Communication Patterns
Expert requests differ from novice requests in predictable ways:
| Pattern | Novice | Expert |
|---|---|---|
| Precision | "make it faster" | "optimise page load performance" |
| Decomposition | Single vague request | Broken into logical components |
| Constraints | Unstated | Explicit limits, trade-offs, success criteria |
| Context | Missing | System fit, standards, prior attempts |
| Failure modes | Ignored | Anticipated and specified |
Role framing (e.g. "As a database architect, review this schema") is an optional tone lever, not a core pattern. Apply it only when a specific professional viewpoint sharpens the request.
Examples
These illustrate the transformation from novice to expert framing:
Original: "My back hurts, what should I do?"
Expert rewrite: "Provide guidance on managing back pain. Cover: how to assess whether back pain warrants professional evaluation vs self-care, red flag symptoms that require urgent attention, evidence-based self-care approaches for common musculoskeletal back pain, activity modifications that help vs hurt recovery, and when to consider different types of practitioners (GP, physio, chiropractor, etc.). Focus on helping me make informed decisions rather than diagnosing."
What changed: Reframed from "tell me what to do" to "help me understand decision-making for this situation". Specified the information categories that would actually be useful. Acknowledged appropriate scope limitations.
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.
- 4d ago First seen · 83 lines · 67 tokens per session scan A d8ec467ba929
prompt-enhancer is a skill published in the GitHub repository sammcj/agentic-coding (159 stars, last pushed today), licensed Apache-2.0. It adds 67 tokens to every session and 1,086 once invoked, about $0.0003 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
ai-interface-reviewer
Audit AI-powered interfaces against the uxuiprinciples Part V taxonomy — 44 principles covering transparency, trust calibration, human override, consent, agentic workflows, and conversational design. Returns structured findings with severity and remediation. API key optional — enriched output requires…
docs-writer
Draft or rewrite Strands Agents documentation pages. Use when writing new doc pages, rewriting pages that failed audit, drafting sections for existing pages, or writing blog posts and release notes about Strands. Also triggers on "write a doc", "draft a page", "rewrite the quickstart", "add a tutorial for X"…
fetch-url
Fetch a single URL and convert its content to Markdown. Use when you need to read a web page, documentation page, or API reference without indexing it. The content is returned as plain Markdown text on stdout.
引用生成器
自动生成规范引用格式。当用户需要生成参考文献、引用来源、标注知识库内容出处、或要求提供引用信息时使用此技能。.
git-checkpoint
Use git as a safety net - create a checkpoint commit before risky or large changes and roll back cleanly if a change makes things worse. Use before multi-file refactors.
synthesize-report
Produces a citation-grounded summary across one or more workspace source files for summaries, briefings, literature reviews, or comparisons.