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/api-referencenpx skills add littlebearapps/pitchdocs --skill api-referencegit 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.00054 | $0.01796 |
| Opus 5 | $0.00027 | $0.00898 |
| Sonnet 5 | $0.00011 | $0.00359 |
| Haiku 4.5 | $0.00005 | $0.00180 |
Grade A, and why
api-reference 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 2d 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 — 288 lines — stays where its author put it; the contents beside it link to each section on GitHub.
API Reference Generator Guidance
Philosophy
API reference docs are the Reference quadrant of the Diataxis framework — information-oriented, accurate, and complete. They document every public function, class, method, parameter, and return type.
This skill does not generate API docs directly — that's the job of language-specific tools (TypeDoc, Sphinx, godoc, rustdoc). Instead, it provides configuration guidance and comment conventions so those tools produce high-quality output.
Language Detection
Detect the project language to recommend the appropriate tool:
# Check for language-specific manifest files
[ -f "package.json" ] && echo "javascript/typescript"
[ -f "tsconfig.json" ] && echo "typescript (confirmed)"
[ -f "pyproject.toml" ] || [ -f "setup.py" ] && echo "python"
[ -f "go.mod" ] && echo "go"
[ -f "Cargo.toml" ] && echo "rust"
TypeScript / JavaScript (TypeDoc)
Tool: TypeDoc — generates HTML or Markdown documentation from TypeScript source code and JSDoc comments.
Installation
npm install --save-dev typedoc
Configuration
Create typedoc.json in the project root:
{
"$schema": "https://typedoc.org/schema.json",
"entryPoints": ["src/index.ts"],
"out": "docs/api",
"plugin": ["typedoc-plugin-markdown"],
"readme": "none",
"excludePrivate": true,
"excludeProtected": true,
"excludeInternal": true,
"categorizeByGroup": true,
"sort": ["source-order"]
}
For Markdown output (recommended for GitHub-hosted docs):
npm install --save-dev typedoc-plugin-markdown
TSDoc Comment Conventions
/**
* Generates a marketing-friendly README from codebase analysis.
*
* Scans the project for features, translates them into benefit-driven
* language, and outputs a complete README.md following the 4-question
* framework.
*
* @param options - Configuration for README generation
* @param options.projectPath - Path to the project root
* @param options.format - Output format: 'github' | 'npm' | 'pypi'
* @returns The generated README content as a string
* @throws {ProjectNotFoundError} If projectPath doesn't exist
*
* @example
* ```typescript
* const readme = await generateReadme({
* projectPath: './my-project',
* format: 'github'
* })
* ```
*
* @see {@link FeatureExtractor} for the scanning workflow
* @since 1.0.0
*/
export async function generateReadme(options: ReadmeOptions): Promise<string> {
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.
- 2d ago First seen · 288 lines · 54 tokens per session scan A 6db27c448cec
api-reference is a skill published in the GitHub repository littlebearapps/pitchdocs (7 stars, last pushed 3mo ago), licensed MIT. It adds 54 tokens to every session and 1,796 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-dir
Use when testing the goldenjupyterdir golden build.