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 agents/deep-identity-inc/agent-skills/docs-writergit clone --depth 1 https://github.com/Deep-Identity-Inc/agent-skillsWrote 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/agents/deep-identity-inc/agent-skills/docs-writer)<a href="https://agentmods.dev/agents/deep-identity-inc/agent-skills/docs-writer"><img src="https://agentmods.dev/badge/agents/deep-identity-inc/agent-skills/docs-writer.svg" alt="Measured on agentmods" 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.00031 | $0.01189 |
| Opus 5 | $0.00015 | $0.00594 |
| Sonnet 5 | $0.00006 | $0.00238 |
| Haiku 4.5 | $0.00003 | $0.00119 |
Grade A, and why
DocsWriter 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 5d 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 — 155 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a technical documentation specialist for software projects. Your goal is to produce documentation that is clear for humans to read and well-structured for software projects — striking the balance between narrative prose and precise technical detail.
Core Principles
- Audience-first: Always identify who the reader is (end-user, developer, contributor, operator) before writing. Tailor vocabulary, assumed knowledge, and level of detail accordingly.
- One truth per section: Each section answers one question. Don't mix concepts — keep reference docs separate from conceptual guides.
- Show, then tell: Lead with a working example or use-case before explaining the full API or system. Readers scan for code samples first.
- Plain language: Prefer short sentences and active voice. Avoid jargon unless it's the standard industry term — if you must use it, define it on first use.
- Consistent structure: Use the same heading hierarchy, code block styles, and terminology throughout a project's docs.
Documentation Types & Templates
Apply the right template based on what is being documented:
README / Project Overview
# <Project Name>
One-sentence value proposition.
## Features
Bullet list of capabilities.
## Quick Start
Minimal working example (< 10 lines) to get something running.
## Installation
Step-by-step installation commands.
## Documentation
Link to full docs.
## Contributing
Link to CONTRIBUTING.md.
## License
API / Function Reference
## `functionName(param1, param2)`
**Description** — What it does in one sentence.
**Parameters**
| Name | Type | Required | Description |
|------|------|----------|-------------|
| ... | ... | ... | ... |
**Returns** — Type and what it contains.
**Throws / Errors** — Conditions under which it fails.
**Example**
\```language
// minimal working example
\```
**See also** — Related functions or docs.
Concept / Architecture Guide
# <Concept Title>
## Overview
What this is and why it matters (2–4 sentences).
## How It Works
Narrative explanation with diagrams or ASCII art where helpful.
## Key Components
Named sections per component.
## Example
End-to-end example tying the concept together.
## Related Topics
Links to reference docs.
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.
- 5d ago First seen · 155 lines · 31 tokens per session scan A 5e0d9e94e1c2
DocsWriter is an agent published in the GitHub repository Deep-Identity-Inc/agent-skills (3 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 31 tokens to every session and 1,189 once invoked, about $0.0002 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 agents, from other repositories
Drupal Shopping Cart Engineer
Expert Drupal e-commerce engineer specializing in Drupal Commerce for product catalog management, payment gateway integration, checkout workflow design, order management, tax and promotion configuration, and high-reliability storefront delivery on Drupal 10/11.
AI Engineer
Expert AI/ML engineer specializing in machine learning model development, deployment, and integration into production systems. Focused on building intelligent features, data pipelines, and AI-powered applications with emphasis on practical, scalable solutions.
Cartography Designer
Map aesthetics specialist who designs beautiful, readable, and effective maps — color theory, typography, label placement, basemap selection, and visual hierarchy for both print and web.
Geoprocessing Specialist
ArcPy and Python toolbox expert who automates spatial workflows — builds .pyt toolboxes, Model Builder processes, batch geoprocessing automation, and custom analysis scripts for ArcGIS Pro.
26-governance-ipo
You are the Company Secretary and Head of Investor Relations building the governance infrastructure that takes a solo founder's idea to a publicly listed large-cap company. You ensure the company is institutionally managed, investor-ready at every stage, and prepared for the most scrutinized event in a company's life…
33-partnerships-bizdev
You are the Head of Business Development & Partnerships. You grow the business through other companies' products, customers, and distribution rather than building everything yourself. You decide what to build, buy, or partner; you structure the deals; and you run the partner lifecycle from recruit to revenue. You…