Borrowing it
Nothing to install: this file belongs to OpenAgentsInc/openagents. 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/OpenAgentsInc/openagents/main/.agents/skills/google-developer-style/SKILL.mdgit clone --depth 1 https://github.com/OpenAgentsInc/openagentsWrote 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/openagentsinc/openagents/google-developer-style)<a href="https://agentmods.dev/skills/openagentsinc/openagents/google-developer-style"><img src="https://agentmods.dev/badge/skills/openagentsinc/openagents/google-developer-style/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/openagentsinc/openagents/google-developer-style"><img src="https://agentmods.dev/badge/skills/openagentsinc/openagents/google-developer-style.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.00039 | $0.00571 |
| Opus 5.5 | $0.00016 | $0.00228 |
| Sonnet 5.5 | $0.00008 | $0.00114 |
| Haiku 4.5 | $0.00004 | $0.00057 |
Grade A, and why
google-developer-style 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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Google Developer Documentation Style
Use this skill when you write or review user-facing documentation, READMEs, AGENTS.md, and commit messages for OpenAgents.
How to use this skill
Apply these rules to the text you produce or edit. When a rule would make something less clear, break the rule and stay consistent.
Voice and tone
- Be conversational and friendly, but not frivolous or overly casual.
- Write as a knowledgeable friend who understands what the developer wants to do.
- Avoid jargon, buzzwords, clichés, metaphors, ableist language, and pop-culture references.
- Avoid exclamation marks and over-polite phrases such as "please" or "please note."
- Avoid filler words like "simply," "just," "it's easy," or "quickly" in procedures.
- Avoid phrasing like "let's do something" or "we" for the reader; speak to the reader with "you."
Language and grammar
- Use active voice. Make clear who performs the action.
- Use second person ("you") for the reader.
- Use present tense.
- Use standard American spelling and punctuation.
- Put conditions before instructions, not after.
- Use serial commas.
- Do not use ampersands (&) as conjunctions in body text or headings.
Formatting
- Use sentence case for all headings, titles, and navigation.
- Use code font for code, filenames, class names, method names, HTTP status codes, placeholders, and user input.
- Use bold for UI elements and run-in headings.
- Use italics sparingly, mainly when introducing or defining terms.
- Underline only for link text.
- Do not override global font styles.
Lists
- Use numbered lists for sequences and procedures.
- Use bulleted lists for related but unordered items.
- Use description lists for related pairs of data.
- Keep list items parallel in structure.
Code and links
- Put code in text in code font.
- Use descriptive link text. Avoid "click here" or "this page."
- Use unambiguous date and time formatting.
- Provide alt text for images.
Banned patterns
- "Dude!" / "This is awesome!"
- "It's that simple" / "It's easy" / "simply"
- "Please" in instructions
- "At this time" / "please note"
- "Let's" as an imperative to the reader
- All-caps or title-case headings
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 · 68 lines · 39 tokens per session scan A afb103c87f28
google-developer-style is a skill published in the GitHub repository OpenAgentsInc/openagents (458 stars, last pushed today), licensed Apache-2.0. It adds 39 tokens to every session and 571 once invoked, about $0.0002 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-09-19.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…