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 skills/surendranb/writing-skills/google-dev-docsnpx skills add surendranb/writing-skills --skill google-dev-docsgit clone --depth 1 https://github.com/surendranb/writing-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/surendranb/writing-skills/google-dev-docs)<a href="https://agentmods.dev/skills/surendranb/writing-skills/google-dev-docs"><img src="https://agentmods.dev/badge/skills/surendranb/writing-skills/google-dev-docs.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 | $0.00037 | $0.00571 |
| Opus 5 | $0.00018 | $0.00285 |
| Sonnet 5 | $0.00007 | $0.00114 |
| Haiku 4.5 | $0.00004 | $0.00057 |
Grade A, and why
google-dev-docs 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 — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Google Developer Documentation Style
Write precise, task-oriented technical documentation with second-person address and active voice.
The core rule
Task-oriented headings, present tense, second person ("you"), active voice.
Workflow: state user goal in title → prerequisites first → numbered steps with concrete code examples → verification step.
Mechanics
- Second person. Address the developer directly as "you"; avoid "we", "us", or third-person generalities.
- Present tense. Describe current system behavior in present tense ("Returns a 200 OK status", not "Will return").
- Task-oriented headings. Start headings with gerunds or action verbs ("Configuring authentication", not "Authentication overview").
- Active voice. "The server processes the request" rather than "The request is processed by the server".
- Code blocks with context. Every code snippet must include necessary imports, setup, and expected output.
- Pronoun clarity. Ensure "this", "that", and "it" clearly point to a preceding noun.
- Consistent terminology. Use identical terms across guides, API references, and UI labels.
- Concise error messages. Explain what went wrong and how to fix it immediately.
Verify
- Headings use gerunds or action verbs describing tasks
- Sentences consistently use second person ("you")
- Code snippets are complete, syntactically valid, and tested
- Active voice used throughout instructions
- Present tense used for API descriptions
Do not
- Use future tense for deterministic software behavior ("The method will return...")
- Leave code snippets without imports or setup context
- Use vague filler phrases ("Simply run...", "Just configure...")
- Mix second person and first person within the same tutorial
References
For exact mechanical rules (numbers, percentages, ordinals, ranges, abbreviations, units), read references/REFERENCE.md when a draft contains any of these — load on demand, not upfront.
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.
- 5d ago First seen · 56 lines · 37 tokens per session scan A bae61bc46396
google-dev-docs is a skill published in the GitHub repository surendranb/writing-skills (29 stars, last pushed 2d ago), licensed MIT. It adds 37 tokens to every session and 571 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-30.
Other skills, from other repositories
gemini
Cross-model second opinion from Google Gemini — a different AI reviewing the same changes, with deep Google ecosystem knowledge. Three modes: review (pass/fail gate for Google Ads campaigns, SEO metadata, or code), challenge (adversarial stress-test that tries to break your changes), and consult (open Q&A with Gemini…
schema-markup-generator
Generate JSON-LD structured data markup for rich results in Google Search. Supports FAQ, HowTo, Article, Product, LocalBusiness, and multi-type schemas. Validates against Google requirements and provides implementation guidance. Use when asked to "add schema markup", "generate structured data", "JSON-LD", "rich…
google-ads-landing
Score and diagnose Google Ads landing pages. Use when asked to audit a landing page, check landing page quality, diagnose high-CTR but low-conversion-rate ad groups, improve Quality Score's Landing Page Experience component, or compare an ad group's messaging against its landing page. Trigger on "landing page audit"…
content-planner
GSC-driven content calendar. Pulls real Search Console data, finds the highest click-potential opportunities (striking-distance queries at positions 5-20, unanswered query intent, related-keyword expansions), and produces a dated, prioritized content calendar — ready to hand to /content-writer. Use when the user asks…
keyword-research
Discover, analyze, and prioritize keywords for SEO and GEO content strategies from a seed keyword or niche. Identifies high-value opportunities based on search volume, competition, intent, and business relevance. Generates topic clusters. For building a dated editorial calendar from your own Search Console data, use…
meta-tags-optimizer
Optimize title tags, meta descriptions, Open Graph, and Twitter cards for maximum click-through rate. Generates multiple A/B test variations with character counting and SERP preview. Use when asked to "optimize title tag", "write meta description", "improve CTR", "Open Graph tags", "fix my meta tags", "social media…