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/googlechrome/modern-web-guidance-src/project-coding-standardsnpx skills add GoogleChrome/modern-web-guidance-src --skill project-coding-standardsgit clone --depth 1 https://github.com/GoogleChrome/modern-web-guidance-srcWrote 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/googlechrome/modern-web-guidance-src/project-coding-standards)<a href="https://agentmods.dev/skills/googlechrome/modern-web-guidance-src/project-coding-standards"><img src="https://agentmods.dev/badge/skills/googlechrome/modern-web-guidance-src/project-coding-standards.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.00056 | $0.01742 |
| Opus 5 | $0.00028 | $0.00871 |
| Sonnet 5 | $0.00011 | $0.00348 |
| Haiku 4.5 | $0.00006 | $0.00174 |
Grade A, and why
project-coding-standards 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 — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Guidance Repository Coding Standards & Review Guidelines
Overview
This skill defines the architectural principles, coding conventions, and PR review standards for the modern-web-guidance-src repository.
Follow these guidelines whenever authoring TypeScript, JavaScript, CLI commands, harness utilities, server endpoints, or dashboard code.
PR Scope and Modularity
Keep PRs Focused and Single-Purpose
- Split multi-component features: Do not combine backend data models, CLI tools, and frontend UI changes into a single monolithic PR.
- Logical progression: Structure larger features into small, stacked, or sequential PRs:
- Data layer / core libraries (parsing, normalization, abstractions)
- CLI workflows and execution commands
- UI / visualization components and dashboard views
- Smaller, well-scoped PRs are easier to review, test, and safely revert if regressions occur.
Architectural Principles
Use Existing Abstractions & CLI Runners
- Reuse repository tooling: When interacting with LLMs or executing agent workflows, use the shared repository abstractions in
config.environment(such asconfig.environment.jetskiCliBinorconfig.environment.geminiCliBin) instead of writing custom REST API clients, bespoke fetch loops, or ad-hoc token validators. - Environment and flag handling: Respect standard environment toggles (such as
GD_DEV_USE_GEMINI === '1') and omit non-essential flags (e.g., omit--yolofor non-interactive or diagnostics tasks).
Single Source of Truth & Canonical Enums
- Never hardcode string constants for agents or serving modes:
- Use centralized enums like
Agentsfromharness/config.ts(Agents.JETSKI,Agents.CLAUDE_CODE,Agents.GEMINI_CLI,Agents.CODEX_CLI). - Use centralized enums like
Servingfromharness/config.ts(Serving.MCP,Serving.SKILLS_CLI).
- Use centralized enums like
- Extract metadata from source-of-truth files:
- Never infer properties (such as
targetFile,agent, orservingmode) using fragile path heuristics or regexes if canonical metadata files (e.g.,evals.json) exist in the parent hierarchy. Extract canonical properties directly fromevals.json.
- Never infer properties (such as
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 · 120 lines · 56 tokens per session scan A 80715940faed
project-coding-standards is a skill published in the GitHub repository GoogleChrome/modern-web-guidance-src (1,010 stars, last pushed today), licensed Apache-2.0. It adds 56 tokens to every session and 1,742 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…