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 Pixel-Process-UG/superkit-agents --skill tech-docs-generatorgit clone --depth 1 https://github.com/Pixel-Process-UG/superkit-agentsWrote 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/pixel-process-ug/superkit-agents/tech-docs-generator)<a href="https://agentmods.dev/skills/pixel-process-ug/superkit-agents/tech-docs-generator"><img src="https://agentmods.dev/badge/skills/pixel-process-ug/superkit-agents/tech-docs-generator/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/pixel-process-ug/superkit-agents/tech-docs-generator"><img src="https://agentmods.dev/badge/skills/pixel-process-ug/superkit-agents/tech-docs-generator.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.00034 | $0.01750 |
| Opus 5.5 | $0.00014 | $0.00700 |
| Sonnet 5.5 | $0.00007 | $0.00350 |
| Haiku 4.5 | $0.00003 | $0.00175 |
Grade A, and why
tech-docs-generator 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 1mo 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 — 218 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Technical Documentation Generator
Overview
Generate comprehensive technical documentation by analyzing the actual codebase. Produces API references, architecture overviews, getting started guides, and component documentation with real examples extracted from project code, not invented ones.
Announce at start: "I'm using the tech-docs-generator skill to create documentation."
Phase 1: Codebase Analysis
Scan the codebase to identify what needs documenting. Deploy parallel subagents via the Agent tool (up to 500, with subagent_type="Explore") to analyze:
| Analysis Target | What to Capture |
|---|---|
| Exported functions/classes | Public API surface, signatures, return types |
| API routes/endpoints | REST, GraphQL, tRPC definitions with methods |
| Configuration | Env vars, config files, feature flags |
| Database schemas | Models, migrations, relationships |
| Component hierarchy | UI components and their props/interfaces |
| Type definitions | Interfaces, types, Zod schemas, enums |
| Entry points | CLI commands, main files, server bootstrap |
| Dependencies | External packages and their roles |
STOP after analysis — present a summary of what was found and ask which documentation types are needed.
Phase 2: Documentation Type Selection
| Type | When to Use | Output Path | Typical Size |
|---|---|---|---|
| API Reference | Documenting endpoints or public functions | docs/api-reference.md |
200-1000 lines |
| Architecture Overview | Explaining system design and data flow | docs/architecture.md |
100-300 lines |
| Getting Started | Onboarding new developers | docs/getting-started.md |
50-150 lines |
| Component Docs | Documenting UI components | docs/components/[name].md |
50-200 lines |
| Contributing Guide | Explaining how to contribute | docs/contributing.md |
50-100 lines |
| Configuration Guide | Documenting config options | docs/configuration.md |
50-200 lines |
| Migration Guide | Documenting version upgrades | docs/migration/v[X]-to-v[Y].md |
50-150 lines |
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.
- 1mo ago First seen · 218 lines · 34 tokens per session scan A 7f9872e9c666
tech-docs-generator is a skill published in the GitHub repository Pixel-Process-UG/superkit-agents (3 stars, last pushed 7mo ago), licensed MIT. It adds 34 tokens to every session and 1,750 once invoked, about $0.0001 per session on Opus 5.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-09-03.
Other skills, from other repositories
asr
A local speech-to-text tool that turns audio files into written text. It uses offline speech-recognition models and supports Chinese, English, Japanese, Korean, and Cantonese, with an English-only option as well.
awesome-document-style
Line-edits Markdown documents into clear, specific, publication-ready prose: cuts bloat and template structure, fixes vague wording and number style. Use when asked to edit, tighten or polish a document.
nextra-writer
Writes Nextra documentation sites with MDX — config, navigation, search, API docs. Use when creating or updating Nextra docs on Next.js.
docs
Writes or updates README files, guides, runbooks, API references, and setup docs matching the repo's conventions. Use when documenting software projects.
tracker-builder
This skill should be used when the user asks to "build me a metrics tracker," "wire up a daily log to the summary sheet," "create a performance tracker spreadsheet," or needs an actual spreadsheet built that replicates a Daily Log / summary-sheet pattern with formulas wired between tabs.
doc-reviewer
This skill should be used when the user asks to "review this deck for structure," "critique this memo," "is this narrative tight," or provides an existing document or deck and wants a structural critique against pyramid and so-what discipline rather than a line edit or rewrite.