Borrowing it
Nothing to install: this file belongs to itallstartedwithaidea/gemini-cli-googleadsagent. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/itallstartedwithaidea/gemini-cli-googleadsagent/main/.gemini/skills/docs-writer/SKILL.mdgit clone --depth 1 https://github.com/itallstartedwithaidea/gemini-cli-googleadsagentWrote 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/itallstartedwithaidea/gemini-cli-googleadsagent/docs-writer)<a href="https://agentmods.dev/skills/itallstartedwithaidea/gemini-cli-googleadsagent/docs-writer"><img src="https://agentmods.dev/badge/skills/itallstartedwithaidea/gemini-cli-googleadsagent/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/itallstartedwithaidea/gemini-cli-googleadsagent/docs-writer"><img src="https://agentmods.dev/badge/skills/itallstartedwithaidea/gemini-cli-googleadsagent/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.00035 | $0.01492 |
| Opus 5.5 | $0.00014 | $0.00597 |
| Sonnet 5.5 | $0.00007 | $0.00298 |
| Haiku 4.5 | $0.00003 | $0.00149 |
Grade A, and why
docs-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 — 143 lines — stays where its author put it; the contents beside it link to each section on GitHub.
docs-writer skill instructions
As an expert technical writer and editor for the Gemini CLI project, you produce
accurate, clear, and consistent documentation. When asked to write, edit, or
review documentation, you must ensure the content strictly adheres to the
provided documentation standards and accurately reflects the current codebase.
Adhere to the contribution process in CONTRIBUTING.md and the following
project standards.
Phase 1: Documentation standards
Adhering to these principles and standards when writing, editing, and reviewing.
Voice and tone
Adopt a tone that balances professionalism with a helpful, conversational approach.
- Perspective and tense: Address the reader as "you." Use active voice and present tense (e.g., "The API returns...").
- Tone: Professional, friendly, and direct.
- Clarity: Use simple vocabulary. Avoid jargon, slang, and marketing hype.
- Global Audience: Write in standard US English. Avoid idioms and cultural references.
- Requirements: Be clear about requirements ("must") vs. recommendations ("we recommend"). Avoid "should."
- Word Choice: Avoid "please" and anthropomorphism (e.g., "the server thinks"). Use contractions (don't, it's).
Language and grammar
Write precisely to ensure your instructions are unambiguous.
- Abbreviations: Avoid Latin abbreviations; use "for example" (not "e.g.") and "that is" (not "i.e.").
- Punctuation: Use the serial comma. Place periods and commas inside quotation marks.
- Dates: Use unambiguous formats (e.g., "January 22, 2026").
- Conciseness: Use "lets you" instead of "allows you to." Use precise, specific verbs.
- Examples: Use meaningful names in examples; avoid placeholders like "foo" or "bar."
- Quota and limit terminology: For any content involving resource capacity
or using the word "quota" or "limit", strictly adhere to the guidelines in
the
quota-limit-style-guide.mdresource file. Generally, Use "quota" for the administrative bucket and "limit" for the numerical ceiling.
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.
- 1mo ago First seen · 143 lines · 35 tokens per session scan A 778342a03834
docs-writer is a skill published in the GitHub repository itallstartedwithaidea/gemini-cli-googleadsagent (6 stars, last pushed 11d ago), licensed Apache-2.0. It adds 35 tokens to every session and 1,492 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-31.
Other skills, from other repositories
code_explorer
Explores the repository to locate primary source files, coupled UI components, and test files for bug reports or feature requests.
quality
Evaluates whether a GitHub issue is spam, empty, needs more information, or is OK to proceed.
hcom-agent-messaging
Multi-agent communication for AI coding tools. Agents message, watch, and spawn each other across terminals. Use when setting up hcom or troubleshooting.
agent-room-ops
For an all-room analysis sweep, use the tested window collector and coverage contract in history-workflow.md. Archive-derived room IDs and fixed recent limits cannot establish all-room coverage. Fallback text posts support --strict say ROOM --body-file FILE and require receipt inspection.
task-progress
Sends mid-task progress updates to the channel a task came from (Slack, Discord, Telegram, or an AG2 Space room).
task-workstream-grouping
Infer stable semantic workstreams for ungrouped Sutando task history and apply the validated assignments to the durable workstream sidecar. Use for internal task-workstream-grouping maintenance tasks, initial history backfills, and later batches of tasks that need cross-channel or cross-device workstream organization.