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 ooiyeefei/ccc --skill pitch-packagegit clone --depth 1 https://github.com/ooiyeefei/cccWrote 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/ooiyeefei/ccc/pitch-package)<a href="https://agentmods.dev/skills/ooiyeefei/ccc/pitch-package"><img src="https://agentmods.dev/badge/skills/ooiyeefei/ccc/pitch-package.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.00165 | $0.01039 |
| Opus 5 | $0.00082 | $0.00519 |
| Sonnet 5 | $0.00033 | $0.00208 |
| Haiku 4.5 | $0.00016 | $0.00104 |
Grade A, and why
pitch-package 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 7d 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.
Pitch Package - the whole performance
A pitch is one argument delivered through three instruments: the deck (setup), the demo (proof), and the speaker (trust). The demo is the proof; the deck is the setup. This skill's job is sequencing and budget, so the instruments never fight each other. Two rules govern everything: interview before you build, and budget the slot first.
Phase 1 - Interview before you build
STOP: produce no artifacts in this phase. Ask (adapting to what's already known):
- Audience: hackathon judges, VCs, or a customer? What do they explicitly judge or care about (rubric, thesis, their own pain)?
- Slot: total minutes? Is Q&A inside or after it?
- Inventory: what already exists - working product? demo video? deck? scripts? Reuse beats rebuild.
- Demo mode: live product on stage (higher wow, higher risk) or recorded film (deterministic)? Default to recorded unless the live path has been rehearsed with a fallback.
- Speakers: who talks, and are there real credentials to weave into the intro?
- Constraints: venue machine? offline? projector resolution? phone-as-teleprompter?
Reflect the answers back as a one-paragraph brief and get a nod before Phase 2. Skipping this interview is how pitches end up with a beautiful deck for the wrong audience.
Phase 2 - Budget the slot first
Before writing or building anything, write the budget line:
5:00 slot = ~2:30 spoken deck + 2:36 demo video + ~0:10 transitions
(runs ~5:15 as written -> trim points named in the script)
The budget decides scope: how many slides get narrated, whether the demo needs a shorter cut, what gets trimmed live. Every downstream artifact inherits this budget. If the pieces don't sum inside the slot on paper, they won't on stage.
Phase 3 - Compose (gap-fill via the other skills)
Pick the audience lens from references/audiences.md - same assets, different lead, emphasis, and close. Then fill only the gaps the inventory revealed:
What ships with it
3 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.
- 7d ago First seen · 55 lines · 165 tokens per session scan A 1b5fbc66091d
pitch-package is a skill published in the GitHub repository ooiyeefei/ccc (485 stars, last pushed 1mo ago), licensed MIT. It adds 165 tokens to every session and 1,039 once invoked, about $0.0008 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…