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 HirogaKatageri/hirokata --skill pixar-pitchgit clone --depth 1 https://github.com/HirogaKatageri/hirokataWrote 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/hirogakatageri/hirokata/pixar-pitch)<a href="https://agentmods.dev/skills/hirogakatageri/hirokata/pixar-pitch"><img src="https://agentmods.dev/badge/skills/hirogakatageri/hirokata/pixar-pitch/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/hirogakatageri/hirokata/pixar-pitch"><img src="https://agentmods.dev/badge/skills/hirogakatageri/hirokata/pixar-pitch.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.00128 | $0.01184 |
| Opus 5 | $0.00064 | $0.00592 |
| Sonnet 5 | $0.00026 | $0.00237 |
| Haiku 4.5 | $0.00013 | $0.00118 |
Grade A, and why
pixar-pitch 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 11d 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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
The Pixar Pitch — Once Upon a Time, Until Finally
Emma Coats, former Pixar storyboard artist (rule #4 of her "22 Rules of Storytelling"). Every Pixar film hangs on the same skeleton — a stable world, a change that upends it, escalating consequences, and a new normal. It's the most natural shape for any story of transformation.
The Spine
Once upon a time there was ___. Every day, ___. One day, ___. Because of that, ___. Because of that, ___. Until finally, ___.
Beat by beat:
- Once upon a time — the setup: who/what this is about, the starting world.
- Every day — the status quo, the stable-but-flawed normal. (This is where the problem quietly lives.)
- One day — the inciting incident: the change, insight, decision, or disruption that breaks the routine. This is the hinge of the whole pitch.
- Because of that — the first consequence. Cause and effect, not a jump-cut.
- Because of that — the escalation; stakes rise. (Repeatable — chain as many as the story needs.)
- Until finally — the resolution: the new world, the payoff, the transformation complete.
The post's short version — "Once upon a time. Every day. Until finally." — is the compressed three-beat form: status quo → turn → new reality. Use the full spine when you have room to build cause and effect.
When to use it (and when not)
Use it for: transformation stories, product origin and journey narratives, customer case studies (their world before → after you), change-management and vision-of-the-future comms, fundraising "here's the world we're building" arcs, conference talk openers.
Reach for something else when: the audience wants the decision first (→ pyramid-principle),
it's a factual debrief (→ what-so-what-now-what), or you need one punchy line (→ abt). The Pixar
Pitch trades speed for emotional arc — don't use it when there's no real "before and after".
How to build it
- Find the transformation. What was the world like before, and what is it like after? If nothing genuinely changes, this isn't the right frame.
- Make "Every day" ache a little. The status quo should carry the unspoken problem so the turn feels earned.
- Nail the "One day". One clear inciting moment. Vague turns produce flat pitches.
- Chain "Because of that". Consequences must follow causally — earned, not listed.
- Land "Until finally" on the payoff, ideally echoing the ache from "Every day".
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.
- 11d ago First seen · 97 lines · 128 tokens per session scan A f46105f3e03e
pixar-pitch is a skill published in the GitHub repository HirogaKatageri/hirokata (5 stars, last pushed 3d ago), licensed MIT. It adds 128 tokens to every session and 1,184 once invoked, about $0.0006 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-31.
Other skills, from other repositories
unslop
Humanize LLM output so it reads like a careful human wrote it. Subtracts AI-isms (sycophancy, tricolons, em-dash overuse, "delve"/"tapestry"/"testament", hedging stacks, tidy five-paragraph shapes), engineers burstiness and calibrated uncertainty, and preserves technical accuracy. Supports intensity levels: subtle…
unslop-file
Humanize natural-language memory files (CLAUDE.md, todos, preferences, docs) by removing AI-isms and adding burstiness while preserving every code block, URL, path, command, and heading exactly. Two modes: --deterministic (fast, regex-based, no API) and LLM (default, calls Claude for rewrite). Humanized version…
unslop-commit
Rewrites commit messages so they sound like a careful human engineer wrote them. Strips AI/marketing slop ("comprehensive solution", "robust implementation", "leverage", "enhance", "seamlessly", "This commit..."). Keeps Conventional Commits format. Subject ≤72 chars (aim ≤50), imperative mood. Body only when "why"…
unslop-help
Quick-reference card for unslop modes, sub-skills, and slash commands. One-shot display, not a persistent mode. Trigger: /unslop-help, "unslop help", "what unslop commands", "how do I use unslop".
simulator-charts
Simulator.Company chart and dashboard specialist. Use when the user wants to create, configure, or query charts (line, bar, area), dashboards, or financial time-series visualisations on a graph layer. Trigger on any of these intents: — Creating: "create chart", "add chart", "create dashboard", "add dashboard", "build…
simulator-init
Simulator.Company environment setup specialist. Use when the user wants to connect to Simulator.Company, set up credentials, authenticate, configure the workspace, or start working with Simulator for the first time. Activate when the user says "init", "setup", "connect to simulator", "login to simulator", "configure…