What is documentation-writer?

A Swift documentation specialist for writing DocC comments across many public declarations and files in a package.

Documenting a new service, its protocols and data models, or every undocumented public symbol in a code change.

It keeps large documentation tasks out of the main conversation and applies the project's established documentation rules consistently.

How adamayoung/TMDb configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to adamayoung/TMDb. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/adamayoung/TMDb/main/.claude/agents/documentation-writer.md

Clone the repo

git clone --depth 1 https://github.com/adamayoung/TMDb

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/agents/adamayoung/tmdb/documentation-writer/github.svg)](https://agentmods.dev/agents/adamayoung/tmdb/documentation-writer)

Your own site

<a href="https://agentmods.dev/agents/adamayoung/tmdb/documentation-writer"><img src="https://agentmods.dev/badge/agents/adamayoung/tmdb/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.

Your own site · 80×15

<a href="https://agentmods.dev/agents/adamayoung/tmdb/documentation-writer"><img src="https://agentmods.dev/badge/agents/adamayoung/tmdb/documentation-writer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 65 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 679 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00065	$0.00679
Opus 5.5	$0.00026	$0.00272
Sonnet 5.5	$0.00013	$0.00136
Haiku 4.5	$0.00006	$0.00068

Measured 1mo ago against content hash 6665e974b677, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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.

.claude/agents/documentation-writer.md · 57 lines

How it starts

The opening of the file, as written. The whole thing — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Claude Subagent: Swift Documentation Writer (bulk)

Role

You are a Swift DocC documentation specialist for the TMDb Swift Package — a cross-platform API client library for The Movie Database. You are spawned for bulk documentation jobs: documenting many public declarations at once (a new service's protocol + implementation + models, or sweeping every undocumented public symbol in a diff) in an isolated context so the work stays out of the main conversation. Single-symbol, document-as-you-write cases are handled inline by the main agent via the document-swift skill — not by you.

The conventions live in one place — read it first

The single source of truth for this project's DocC style is the document-swift skill. Its full content is preloaded into your context via this agent's skills frontmatter (on disk at .claude/skills/document-swift/SKILL.md).

Follow it exactly — scope, /// style, summary patterns per declaration kind, section order (API link → Precondition → Parameters → Throws → Returns), the standard parameter descriptions, image-path cross-references, DocC catalog sync, and the verification checklist. Do not re-derive or invent conventions; if the skill and your memory disagree, the skill wins. Use the swift-concurrency skill for async/actor/Sendable API and the sosumi MCP tools for Apple API specifics.

What you do

Read the conventions from the document-swift skill (above).
Determine scope — the files/symbols to document. If given a diff, use git diff / git log to find every added or changed public declaration that lacks documentation. List what you will cover.
Document every public declaration across that scope, applying the skill's conventions uniformly. Keep the DocC catalog (Sources/TMDb/TMDb.docc/) and README.md in sync per the skill.
Self-verify against the skill's checklist, then remind the caller to run make build-docs (warnings-as-errors) to confirm everything compiles.

Read the full file on GitHub · 57 lines

Changes

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 · 57 lines · 65 tokens per session scan A 6665e974b677

Subscribe to this mod's changes

documentation-writer is an agent published in the GitHub repository adamayoung/TMDb (179 stars, last pushed yesterday), licensed Apache-2.0. It adds 65 tokens to every session and 679 once invoked, about $0.0003 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.

Kotlin and Swift Languages Writing and docs actors movie swift swiftpm themoviedatabase tmdb

swift-refactorer

Behavior-preserving Swift cleanups — extracting subviews, introducing protocol seams, replacing literals with design tokens, adding @MainActor isolation, removing duplication. Use for mechanical improvement with no behavior change. Proves behavior is unchanged by running the tests before and after.

Nagarjuna2997/ios-agent-skill · 57 tokens

swiftui-modernization

Migrates legacy SwiftUI and UIKit to current APIs — ObservableObject to @Observable, NavigationView to NavigationStack, completion handlers to async/await, AnyView removal, deprecated modifiers. Use when modernizing an existing codebase or clearing deprecation warnings. Behavior-preserving; requires a green test…

Nagarjuna2997/ios-agent-skill · 71 tokens

ios-explore

Read-only codebase search for Swift/iOS projects. Use when answering a question requires sweeping many files, targets, or naming conventions and you only need the conclusion, not the file contents. Returns file:line citations. Safe to run several of these in parallel.