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 asgarovf/locusai --skill documentation-writergit clone --depth 1 https://github.com/asgarovf/locusaiWrote 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/asgarovf/locusai/documentation-writer)<a href="https://agentmods.dev/skills/asgarovf/locusai/documentation-writer"><img src="https://agentmods.dev/badge/skills/asgarovf/locusai/documentation-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/asgarovf/locusai/documentation-writer"><img src="https://agentmods.dev/badge/skills/asgarovf/locusai/documentation-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.00031 | $0.01324 |
| Opus 5.5 | $0.00012 | $0.00530 |
| Sonnet 5.5 | $0.00006 | $0.00265 |
| Haiku 4.5 | $0.00003 | $0.00132 |
Grade A, and why
documentation-writer 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 — 240 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Documentation Writer
When to use this skill
- Writing or improving a README
- Documenting API endpoints
- Creating architecture or design docs
- Writing setup/installation guides
- Adding JSDoc/docstrings to code
- Creating migration guides for breaking changes
README structure
A good README answers: What is this? How do I use it? How do I contribute?
# Project Name
Brief description (1-2 sentences). What does it do and who is it for?
## Quick Start
\`\`\`bash
npm install project-name
\`\`\`
\`\`\`typescript
import { something } from 'project-name';
const result = something('hello');
\`\`\`
## Features
- Feature one — brief explanation
- Feature two — brief explanation
- Feature three — brief explanation
## Installation
\`\`\`bash
# npm
npm install project-name
# yarn
yarn add project-name
\`\`\`
### Prerequisites
- Node.js >= 18
- PostgreSQL >= 14
## Usage
### Basic usage
[Code example with explanation]
### Configuration
[Configuration options with defaults]
### Advanced usage
[More complex examples]
## API Reference
### `functionName(param1, param2)`
Description of what the function does.
**Parameters:**
| Name | Type | Default | Description |
|------|------|---------|-------------|
| `param1` | `string` | — | Description |
| `param2` | `number` | `10` | Description |
**Returns:** `Promise<Result>` — Description
**Example:**
\`\`\`typescript
const result = await functionName('hello', 5);
\`\`\`
## Environment Variables
| Variable | Required | Default | Description |
|----------|----------|---------|-------------|
| `DATABASE_URL` | Yes | — | PostgreSQL connection string |
| `PORT` | No | `3000` | Server port |
| `LOG_LEVEL` | No | `info` | Logging level |
## Development
\`\`\`bash
git clone https://github.com/org/repo.git
cd repo
npm install
npm run dev
\`\`\`
### Running tests
\`\`\`bash
npm test
npm run test:coverage
\`\`\`
## Contributing
[Brief contribution guidelines or link to CONTRIBUTING.md]
## License
[License type] — see [LICENSE](LICENSE)
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 · 240 lines · 31 tokens per session scan A c18013fc8c42
documentation-writer is a skill published in the GitHub repository asgarovf/locusai (23 stars, last pushed 7mo ago), licensed MIT. It adds 31 tokens to every session and 1,324 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-08-30.
Other skills, from other repositories
document-writer
Write or update technical documentation grounded in the real codebase. Use when the user asks for README, API docs, architecture guides, user guides, CONTRIBUTING docs, migration notes, or JSDoc/code comments, or wants technical docs rewritten into natural Chinese with correct terminology. Not for general prose…
doc-generator
Generate accurate, useful documentation for code — README files, API docs, inline docstrings, and changelogs. Use when user needs to document code, write a README, or generate API reference docs.
documentation-standards
Use when writing README files, API documentation, user guides, or technical documentation following industry standards from Google, Microsoft, and GitLab style guides.
doc-generator
Auto-generate documentation from code: README files, JSDoc comments, API docs. Scans project structure, detects frameworks, and produces ready-to-use documentation.
documentation-and-adrs
Use this skill when you need to record an architecture decision (ADR) or document the reasoning behind a design choice — when changing public APIs, shipping features that change behavior, or recording context that future engineers (human or agent) will need to understand the codebase. Does NOT replace code comments or…
documentation
Technical writing, API docs, and documentation best practices.