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 yaleh/meta-cc --skill prompt-listgit clone --depth 1 https://github.com/yaleh/meta-ccWrote 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/yaleh/meta-cc/prompt-list)<a href="https://agentmods.dev/skills/yaleh/meta-cc/prompt-list"><img src="https://agentmods.dev/badge/skills/yaleh/meta-cc/prompt-list/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/yaleh/meta-cc/prompt-list"><img src="https://agentmods.dev/badge/skills/yaleh/meta-cc/prompt-list.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.00028 | $0.00315 |
| Opus 5 | $0.00014 | $0.00158 |
| Sonnet 5 | $0.00006 | $0.00063 |
| Haiku 4.5 | $0.00003 | $0.00032 |
Grade A, and why
prompt-list 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 9d 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.
What it actually says
Prompt Library Listing
List saved prompts under .meta-cc/prompts/library/ in the current project.
Arguments
Support these optional key-value arguments when the user provides them:
category=<name>filters by category.sort=usagesorts byusage_countdescending.sort=datesorts byupdateddescending.sort=alphasorts by title or ID ascending.
Default sort is usage.
Workflow
- Resolve the library path as
.meta-cc/prompts/library/from the current project root. - If the directory does not exist, say no prompt library exists.
- Read every
*.mdfile in the library. - Parse YAML frontmatter when present. Prefer these fields when available:
idtitlecategorykeywordsusage_countupdatedstatus
- Apply the category filter if provided.
- Sort according to the requested sort mode.
- Show a summary with total prompt count, category count, and total usage count when available.
- Present a compact table with title, category, uses, updated date, and ID.
Output
Keep output scannable. Tell the user to use $prompt-show <id> for full prompt
details.
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.
- 9d ago First seen · 43 lines · 28 tokens per session scan A 00978e81f0ee
prompt-list is a skill published in the GitHub repository yaleh/meta-cc (21 stars, last pushed 19d ago), licensed MIT. It adds 28 tokens to every session and 315 once invoked, about $0.0001 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 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.
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…