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/neeeophytee/agent-stylebooks/google-developer-docsnpx skills add Neeeophytee/agent-stylebooks --skill google-developer-docsgit clone --depth 1 https://github.com/Neeeophytee/agent-stylebooksWrote 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/neeeophytee/agent-stylebooks/google-developer-docs)<a href="https://agentmods.dev/skills/neeeophytee/agent-stylebooks/google-developer-docs"><img src="https://agentmods.dev/badge/skills/neeeophytee/agent-stylebooks/google-developer-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.00054 | $0.00748 |
| Opus 5 | $0.00027 | $0.00374 |
| Sonnet 5 | $0.00011 | $0.00150 |
| Haiku 4.5 | $0.00005 | $0.00075 |
Grade A, and why
google-developer-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 4d 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 — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Google developer docs
Produce developer documentation that helps a reader understand or complete a technical task without decoding the prose.
Protect the source material
- Preserve facts, code, commands, names, URLs, prerequisites, and constraints.
- Do not invent product behavior, defaults, compatibility, or results.
- Mark a missing fact as a question or placeholder instead of guessing.
- Follow a project-specific terminology or API guide before this style.
Plan the page
- Identify the reader, their assumed knowledge, and the outcome they need.
- Choose the page type: concept, procedure, tutorial, reference, or troubleshooting.
- Put prerequisites before the first action that depends on them.
- Lead with the outcome and the shortest useful context. Move rationale after the action unless understanding it is necessary for safety or correctness.
- Decide one term for each concept and use it throughout.
Write the prose
- Address the reader as
youwhen describing their actions. - Give every important action a visible actor and verb.
- Prefer active voice when the actor matters. Use passive voice only when the result matters more or the actor is unknown.
- Put conditions before instructions when a reader must evaluate the condition before acting.
- Keep one main idea in each sentence and one purpose in each paragraph.
- Define an unfamiliar term on first use. Expand an uncommon abbreviation once.
- Use literal, globally understandable language. Remove idioms, wordplay, and culture-specific comparisons from instructional content.
- Use present tense for current behavior. Attach time-sensitive claims to a version or date.
- State limitations directly. Do not soften them with promotional language.
Write procedures
- Start each step with an imperative verb.
- Keep one primary action per numbered step. Put the expected result after it.
- Tell the reader where to act before naming a UI control if context is unclear.
- Provide copyable commands and code. Explain placeholders next to the example.
- Add a verification step when success is not visible.
- Add cleanup or rollback when the procedure creates persistent resources.
What ships with it
2 files 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.
- 4d ago First seen · 78 lines · 54 tokens per session scan A 0e3a06b5acac
google-developer-docs is a skill published in the GitHub repository Neeeophytee/agent-stylebooks (58 stars, last pushed 11d ago), licensed MIT. It adds 54 tokens to every session and 748 once invoked, about $0.0003 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
readme
Create, redesign, audit, or update a repository README.md by inspecting the actual project; write accurate setup and usage guidance with a selectable brand voice, polished information architecture, evidence-based badges and claims, discoverability suggestions, and an optional editable SVG/PNG banner. Use when the user…
yapper
Yapper forces AI responses to be maximally verbose, thoroughly elaborated, and exhaustively explained. All output is expanded by 200–400%. Technical accuracy is maintained at 100%. This plugin is the structural and philosophical inverse of compression-based plugins.
ciel-documentation-engine
CIEL's framework for high-integrity documentation generation, validation, and semantic indexing.
golden-rss
Use when testing the rss golden build.
spec-kitty-charter-doctrine
Run charter interview, generation, context, and sync workflows for project governance in Spec Kitty 3.x. Access doctrine artifacts programmatically via DoctrineService. Resolve agent profiles. Load action-scoped governance context iteratively, not all at once. Triggers: "interview for charter", "generate charter"…
agy-delegate
Delegate a coding task to the Google Antigravity CLI (agy) as a background implementer, then review its diff and land it yourself. Use this whenever the user wants to hand implementation work to Antigravity or agy - phrasings like "have Antigravity do X", "delegate this to agy", "run it through agy", or "use…