Borrowing it
Nothing to install: this file belongs to lglucas/ai-dev-operating-system. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/lglucas/ai-dev-operating-system/main/.claude/skills/pitch/SKILL.mdgit clone --depth 1 https://github.com/lglucas/ai-dev-operating-systemWrote 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/lglucas/ai-dev-operating-system/pitch)<a href="https://agentmods.dev/skills/lglucas/ai-dev-operating-system/pitch"><img src="https://agentmods.dev/badge/skills/lglucas/ai-dev-operating-system/pitch.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.00117 | $0.01325 |
| Opus 5 | $0.00059 | $0.00662 |
| Sonnet 5 | $0.00023 | $0.00265 |
| Haiku 4.5 | $0.00012 | $0.00133 |
Grade A, and why
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 8d 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 — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pitch
Two jobs, in order: compress the Business Plan into something a person will sit through, then decide — explicitly — whether it goes on the public internet.
Runs at WIZARD stage 2.9, after BP v0.0.2 is accepted and before Phase 3.
Job 1 — Write the pitch
Source: docs/business/BUSINESS-PLAN.md v0.0.2. Template: templates/business/PITCH.template.md. Output: docs/business/PITCH.md.
The pitch derives from the BP. It never adds to it.
If a claim belongs in the pitch but is not in the BP, that is a signal the BP is incomplete — go back and fix the BP, then re-derive. A pitch that says something the BP does not is how founders end up contradicting their own diligence materials.
Ten sections maximum. If it does not fit, the problem is the argument, not the format.
Job 2 — Ask the publication question
This is a suggestion, not a default. Most founders never consider putting the BP online. The skill's job is to put the option on the table with honest trade-offs and then accept whatever the user decides. "Not now" is a complete, valid answer.
Present all three options:
| Option | What it means |
|---|---|
| (a) Tudo público | BP + Pitch on a public URL, indexed |
| (b) Público enxuto + completo gated | Trimmed public page; full version behind login or a secret link |
| (c) Nada online por enquanto | Decide again after launch |
State both sides. Do not sell it.
In favor: a link beats a PDF attachment; builds authority; lets an investor, partner, or large customer qualify themselves without a meeting; kills the problem of a stale version circulating.
Against: competitors read everything, including what you consider an advantage; published numbers become expectations you get held to; it requires maintenance, and a stale public BP is worse than none; several sections cannot go out at all.
The redaction gate
Mandatory when the answer is (a) or (b). Publishing a Business Plan means publishing whatever is inside it.
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.
- 8d ago First seen · 111 lines · 117 tokens per session scan A bbc7b6da705e
pitch is a skill published in the GitHub repository lglucas/ai-dev-operating-system (11 stars, last pushed 29d ago), licensed MIT. It adds 117 tokens to every session and 1,325 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-30.
Other skills, from other repositories
cn-check
Install and run the Continue CLI (cn) to execute AI agent checks on local code changes. Use when asked to "run checks", "lint with AI", "review my changes with cn", or set up Continue CI locally.
phone-harness
Control the user's phone — iPhone through the Mac's iPhone Mirroring window, or an Android over adb: open apps, tap, type, swipe, read the screen.
security-audit
Java security checklist covering OWASP Top 10, input validation, injection prevention, and secure coding. Works with Spring, Quarkus, Jakarta EE, and plain Java. Use when reviewing code security, before releases, or when user asks about vulnerabilities.
architecture-review
Analyze Java project architecture at macro level - package structure, module boundaries, dependency direction, and layering. Use when user asks "review architecture", "check structure", "package organization", or when evaluating if a codebase follows clean architecture principles.
issue-triage
Triage and categorize GitHub issues with priority labels. Use when user says "triage issues", "check issues", "review open issues", or during regular maintenance of GitHub issue backlog.
git-commit
Generate conventional commit messages for Java projects. Use when user says "commit", "create commit", "commit changes", or after completing code changes that need to be committed.