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 Gerg/ai_agent_skills --skill doc-writinggit clone --depth 1 https://github.com/Gerg/ai_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/skills/gerg/ai_agent_skills/doc-writing)<a href="https://agentmods.dev/skills/gerg/ai_agent_skills/doc-writing"><img src="https://agentmods.dev/badge/skills/gerg/ai_agent_skills/doc-writing/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/gerg/ai_agent_skills/doc-writing"><img src="https://agentmods.dev/badge/skills/gerg/ai_agent_skills/doc-writing.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.00047 | $0.00972 |
| Opus 5 | $0.00023 | $0.00486 |
| Sonnet 5 | $0.00009 | $0.00194 |
| Haiku 4.5 | $0.00005 | $0.00097 |
Grade A, and why
doc-writing 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 9d 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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
User-Facing Documentation Writing
Context: This skill covers technical documentation writing across all platforms and domains. For platform-specific formatting and conventions, see the references/ directory.
When using this skill, begin by stating: "I'm using the doc-writing skill to write accurate, user-focused technical documentation based on implementation verification."
Workflow
1. Understand the scope
Before writing, establish what is actually implemented vs. designed but not yet shipped:
- Read specs and design docs, but treat them as aspirational; implementations often differ.
- Read the implementation directly (source code, config, tests). This is the ground truth.
- Use git history to constrain your search: find relevant commits by issue tracker reference or keyword, then read the diff.
- Compare implemented behavior against the spec to identify gaps. These become "known limitations" or are simply omitted.
2. Understand the existing docs
- Find the most similar existing doc and match its structure, style, and terminology.
- Identify where the new doc fits in the navigation hierarchy and what cross-links are needed.
- Check whether existing docs need to be updated to reference the new content.
3. Plan before writing
- Determine what the user needs to know to accomplish their goal, not what is technically interesting.
- Assume the reader has general domain knowledge. Link out rather than re-explaining concepts covered elsewhere.
- Focus on differences from existing behavior. What is new or different about this feature compared to what the reader already knows?
- Keep the doc minimal. Add sections only when they carry information the user cannot get from linked docs.
4. Write
- Write for task completion, not comprehensiveness. Procedures > explanations.
- Verify every factual claim against the implementation before including it. When uncertain, omit or flag.
- Use one example where several would be redundant. Link to the main reference docs for exhaustive coverage.
- Review the draft before completing. Check facts, links, and style.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 9d ago First seen · 95 lines · 47 tokens per session scan A ac32a5df1d0c
doc-writing is a skill published in the GitHub repository Gerg/ai_agent_skills (2 stars, last pushed 2mo ago), licensed MIT. It adds 47 tokens to every session and 972 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 skills, from other repositories
orbit-notion
Open Orbit briefing skill — selected by the Orbit pipeline when Notion is the user's only connected connector, or when the user explicitly scopes their daily digest to Notion. Pulls the past 24 hours of document edits, comments, mentions, and database row changes from the user's authenticated Notion connection and…
instrument-data-to-allotrope
Convert laboratory instrument output files (PDF, CSV, Excel, TXT) to Allotrope Simple Model (ASM) JSON format or flattened 2D CSV. Use this skill when scientists need to standardize instrument data for LIMS systems, data lakes, or downstream analysis. Supports auto-detection of instrument types. Outputs include full…
baoyu-youtube-transcript
A tool for downloading the written captions, subtitles, chapter information, speaker labels, and cover image from a YouTube video using its URL or ID.
feishu
Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.
read
Reads URLs and PDFs by fetching source content, defaulting to concise summaries for plain read requests and clean Markdown when asked to convert, save, quote, cite, or feed downstream work. Use when users ask in any language to read, fetch, check, summarize, quote, cite, convert, or save a URL or PDF. Not for local…
overleaf-sync
A two-way connection between a local paper folder and Overleaf, a web-based LaTeX editor for writing research papers. It lets you move changes between the local files and the shared Overleaf project.