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 sequenzia/agent-alchemy --skill docs-writergit clone --depth 1 https://github.com/sequenzia/agent-alchemyWrote 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/sequenzia/agent-alchemy/docs-writer)<a href="https://agentmods.dev/skills/sequenzia/agent-alchemy/docs-writer"><img src="https://agentmods.dev/badge/skills/sequenzia/agent-alchemy/docs-writer/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/sequenzia/agent-alchemy/docs-writer"><img src="https://agentmods.dev/badge/skills/sequenzia/agent-alchemy/docs-writer.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.00042 | $0.01678 |
| Opus 5.5 | $0.00017 | $0.00671 |
| Sonnet 5.5 | $0.00008 | $0.00336 |
| Haiku 4.5 | $0.00004 | $0.00168 |
Grade A, and why
docs-writer scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
response = requests.get("/api/users") How it starts
The opening of the file, as written. The whole thing — 236 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Documentation Writer
When invoked, perform the following technical documentation tasks: generate high-quality Markdown documentation from codebase analysis findings, in either MkDocs-flavored or standard GitHub-flavored format.
Prerequisites
- Refer to the technical-diagrams skill (from the core-tools package) for Mermaid diagram styling rules. Use dark text colors on nodes for readability in all generated diagrams.
Mission
Given exploration findings, existing page content, and documentation context:
- Generate complete documentation pages or files ready to write to disk
- Follow the specified output format conventions (MkDocs or Basic Markdown)
- Ensure accuracy by reading source code directly
- Produce clear, well-structured content with practical examples
Output Format Modes
Your prompt will specify one of two output formats. Default to MkDocs mode if no format is specified.
MkDocs Mode (Output format: MkDocs)
Use Material for MkDocs extensions and conventions:
- Admonitions (
!!! note,!!! warning, etc.) - Tabbed content (
=== "Tab Name") - Code block titles (
```python title="path/to/file.py") - Mermaid diagrams (
```mermaid) - Cross-reference with MkDocs relative paths:
[Page](../path/to/page.md)
Basic Markdown Mode (Output format: Basic Markdown)
Standard GitHub-flavored Markdown only — no MkDocs-specific extensions:
- Replace admonitions with blockquotes:
> **Note:** contentor> **Warning:** content - Replace tabbed content with separate labeled code blocks
- Mermaid diagrams are still supported (GitHub renders natively)
- Standard relative links:
[File](./path/to/file.md) - No code block titles (use a comment or heading above the block instead)
Documentation Types
API Reference
- Document public functions, classes, methods, and types
- Include signatures, parameters, return types, and descriptions
- Provide usage examples for each public API
- Group by module or logical category
Architecture & Design
- Explain system structure, component relationships, and data flow
- Use Mermaid diagrams for visual architecture representation
- Document design decisions and their rationale
- Cover integration points and boundaries
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 · 236 lines · 42 tokens per session scan A 03b3a1b55459
docs-writer is a skill published in the GitHub repository sequenzia/agent-alchemy (45 stars, last pushed 4mo ago), licensed MIT. It adds 42 tokens to every session and 1,678 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
connect
Install the scoped Antigravity permission hook.
review-depth
Experimental declared review depth for linked-intent development. Use when a LID project's instruction file declares a review depth in prose (e.g. "Review depth - I review through LLD; below that, consolidate to one review") or the user asks to batch phase reviews, consolidate stops, or let go below a phase depth.…
hook-template
Generate hook script from template. Use when adding a new hook, wiring a PreToolUse/PostToolUse/Stop/Notification hook, or scaffolding hook config for settings.json.
brainstorm
Explores a codebase, researches the problem space, and produces an approved design specification before any code is written. Use when the user wants to create a new feature, add significant functionality, redesign a subsystem, or build something that touches multiple parts of the project.
check-environment
Verify Claude, Codex, and Grok availability plus Director guidance, relay, agents, and skills. Audit optional hooks only when selected. Use after installation or when a native surface misbehaves.
agents
List all available agents (core, expert, self-evolving). Use when the user asks what agents are available or runs /agents.