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.
git clone --depth 1 https://github.com/sigistry/marketplaceWrote 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/commands/sigistry/marketplace/doc-generate)<a href="https://agentmods.dev/commands/sigistry/marketplace/doc-generate"><img src="https://agentmods.dev/badge/commands/sigistry/marketplace/doc-generate/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/commands/sigistry/marketplace/doc-generate"><img src="https://agentmods.dev/badge/commands/sigistry/marketplace/doc-generate.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.00017 | $0.01277 |
| Opus 5.5 | $0.00007 | $0.00511 |
| Sonnet 5.5 | $0.00003 | $0.00255 |
| Haiku 4.5 | $0.00002 | $0.00128 |
Grade A, and why
doc-generate 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 — 176 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Documentation Generation Command
You are tasked with generating high-quality, comprehensive documentation for the specified code. Follow these steps precisely:
Step 1: Identify Target Code
If the user provided a file path or function name:
- Locate and read the specified file(s) or function(s)
- If a directory is specified, recursively find all code files within it
If no specific target is provided:
- Ask the user which file, function, class, or module they want documented
- Provide a list of recently modified files as suggestions
Step 2: Analyze the Code
For each target file or function, perform a thorough analysis:
Code Structure Analysis
- Identify the programming language and framework
- Determine the purpose and responsibility of the code
- Map out all public APIs, functions, classes, and methods
- Identify dependencies and imported modules
- Detect design patterns used
- Understand the data flow and control flow
Function/Method Analysis
For each function or method:
- Purpose: What problem does it solve?
- Parameters: Document each parameter with type, description, default values, constraints
- Return Values: Document return type, possible return values, and what they represent
- Side Effects: Any state changes, I/O operations, or mutations
- Exceptions: What errors can be thrown and under what conditions
- Complexity: Time and space complexity if applicable
- Examples: Common use cases
Class Analysis
For each class:
- Purpose: What does this class represent or encapsulate?
- Properties/Attributes: Document all public and protected properties
- Methods: Document all public and protected methods
- Inheritance: Parent classes and interfaces implemented
- Design Patterns: Observer, Factory, Singleton, etc.
- State Management: How state is maintained and modified
- Usage Examples: How to instantiate and use the class
Step 3: Generate Language-Appropriate Documentation
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 · 176 lines · 17 tokens per session scan A b67f6d1e9451
doc-generate is a command published in the GitHub repository sigistry/marketplace (3 stars, last pushed 2d ago), licensed MIT. It adds 17 tokens to every session and 1,277 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 commands, from other repositories
slides
Magazine-quality slide deck as a self-contained HTML page.
typescript-dev
Start TypeScript development workflow with architecture, implementation, review, and testing phases.
dotnet-structure
Analyze and recommend .NET backend solution and folder structure improvements. Checks projects, layers, oversized files, and boundary clarity.
audit
Analyze tech stack, run dev tooling, and remediate code quality issues.
plansession
Analyze project state, create session spec and task checklist.
project-recap
Visual HTML project recap — current state, recent decisions, and cognitive debt hotspots.