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 flurdy/agent-skills --skill prompt-patternsgit clone --depth 1 https://github.com/flurdy/agent-skillsWrote 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/flurdy/agent-skills/prompt-patterns)<a href="https://agentmods.dev/skills/flurdy/agent-skills/prompt-patterns"><img src="https://agentmods.dev/badge/skills/flurdy/agent-skills/prompt-patterns/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/flurdy/agent-skills/prompt-patterns"><img src="https://agentmods.dev/badge/skills/flurdy/agent-skills/prompt-patterns.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.00033 | $0.01766 |
| Opus 5.5 | $0.00013 | $0.00706 |
| Sonnet 5.5 | $0.00007 | $0.00353 |
| Haiku 4.5 | $0.00003 | $0.00177 |
Grade A, and why
prompt-patterns 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 today.
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 — 143 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Prompt Patterns
Use only when the user explicitly asks to analyze their prompt history. Find repeated substantial requests, including paraphrases, that would make useful templates. This is candidate discovery, not certified authorship, secret detection or an automatic template generator.
Read history safety and formats before collection. Requires Python 3.10+ on POSIX with no third-party dependencies. The helper makes no network requests, launches no model/subprocess and writes no files. Pi and Claude Code are the only history sources; Codex is out of scope. Missing sources and malformed/unrecognized records are coverage gaps, not zero usage.
Usage
/prompt-patterns
/prompt-patterns last 14 days
/prompt-patterns minimum 150 characters
In Pi use /skill:prompt-patterns. Defaults: last 30 days, minimum 80 characters and 12 words,
50 distinct redacted candidates and 65,536 total serialized packet bytes. The window is UTC and
half-open. Interpret requested changes as numeric collector options, never as shell text.
Do not run a real-history trial merely because this skill is being implemented or reviewed.
1. Collect metadata only
python3 -B ~/.agents/skills/prompt-patterns/scripts/prompt_patterns.py
Optional flags: --days 1..365, --min-chars 40..10000, --min-words 3..1000,
--max-candidates 1..200, --max-bytes 1024..131072, --max-prompt-chars 80..32000.
Repeat the same options for every subsequent command. The default roots are local Pi sessions
and Claude projects; use --pi-root, --claude-root or repeated --template-root only when the user
explicitly selects those locations. Never widen source roots because a scan is empty or unavailable.
The default output contains only counts, bytes, coverage, truncation, asOf and a digest—no prompt
text, transcript paths, raw session IDs or example snippets. Read all source statuses and limits.
It ignores recently active files and refuses malformed/ambiguous files rather than trying to repair
history. No history/cache/config file is created or changed.
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- today First seen · 143 lines · 33 tokens per session scan A 7a402bdc8166
prompt-patterns is a skill published in the GitHub repository flurdy/agent-skills (9 stars, last pushed yesterday), licensed MIT. It adds 33 tokens to every session and 1,766 once invoked, about $0.0001 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-10-20.
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-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…
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…
omh-model-optimization
This is a Hermes-native model-optimization workflow skill.
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…
seedance-vocab-en
This skill should be used when an English Seedance 2.0 prompt needs clearer production wording, less generic prose, or precise vocabulary for camera, lighting, motion, VFX, audio, and constraints. Route blocked prompts through seedance-filter for context and boundary review.