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 agentmods add skills/littlebearapps/pitchdocs/launch-artifactsnpx skills add littlebearapps/pitchdocs --skill launch-artifactsgit clone --depth 1 https://github.com/littlebearapps/pitchdocsWhat 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 | $0.00058 | $0.02111 |
| Opus 5 | $0.00029 | $0.01056 |
| Sonnet 5 | $0.00012 | $0.00422 |
| Haiku 4.5 | $0.00006 | $0.00211 |
Grade A, and why
launch-artifacts 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 3d 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 — 322 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Launch Artifacts Generator
Philosophy
Great documentation is useless if nobody finds it. This skill transforms existing PitchDocs-generated content (README, CHANGELOG, features) into platform-specific posts for launch and promotion.
Scope boundary: This skill generates content from existing code artifacts — it does not create generic marketing playbooks. Every artifact traces back to the README, CHANGELOG, or codebase features.
Prerequisites
Before generating launch artifacts, ensure the project has:
- A PitchDocs-generated README with hero section and features
- A CHANGELOG with the release being announced (if applicable)
- Feature extraction completed via the
feature-benefitsskill
Platform Templates
Dev.to Article
Transform README + CHANGELOG into a Dev.to blog post. Dev.to uses Liquid tags for frontmatter.
---
title: "[Project Name]: [Value proposition from README hero]"
published: false
description: "[README explanatory sentence, condensed to 100 chars]"
tags: [up to 4 relevant tags]
canonical_url: https://github.com/org/repo
---
[Opening hook — rewrite the README "Why" section as a narrative problem statement]
## The Problem
[Expand on the problem from the README's "Why" section — use reader-centric language]
## What [Project Name] Does
[Condense the README features into 3-5 key capabilities with code examples]
### [Feature 1]
[Brief explanation with code example from README quickstart]
\`\`\`typescript
// Copy the most compelling code example from the quickstart
\`\`\`
### [Feature 2]
[Another key feature with a practical example]
## Getting Started
\`\`\`bash
[Installation command from README]
\`\`\`
[Minimal usage example — keep it under 10 lines]
## What's Next
[Link to ROADMAP or upcoming features]
---
*[Project Name] is open source ([licence]) — [link to repo]. Contributions welcome!*
Dev.to tag selection:
- Use existing popular tags (check dev.to/tags)
- Maximum 4 tags per article
- Include language tag (
typescript,python), category tag (opensource,devtools), and 1-2 topic tags
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.
- 3d ago First seen · 322 lines · 58 tokens per session scan A 0665b4d4f78a
launch-artifacts is a skill published in the GitHub repository littlebearapps/pitchdocs (7 stars, last pushed 3mo ago), licensed MIT. It adds 58 tokens to every session and 2,111 once invoked, about $0.0003 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
skill-builder
Automatically detect source types and build AI skills using Skill Seekers. Use when the user wants to create skills from documentation, repos, PDFs, videos, or other knowledge sources.
golden-chat
Use when testing the goldenchat golden build.
golden-epub
Use when testing the epub golden build.
golden-epub-kw
Use when testing keyword categorization.
golden-html-multi
Use when testing the multi-file html build.
golden-jupyter
Use when testing the goldenjupyter golden build.