Modern Web Guidance is a source repository for coding-agent skills that provide web-platform guidance, recommended practices, and browser compatibility information. It helps coding agents choose newer web APIs and patterns when generating web applications. The catalogue skills are the guidance produced and maintained by this project.
Borrowing it
Nothing to install: this file belongs to GoogleChrome/modern-web-guidance-src. 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/GoogleChrome/modern-web-guidance-src/main/.agents/skills/project-coding-standards/SKILL.mdgit 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/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/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="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00056 | $0.01696 |
| Opus 5.5 | $0.00022 | $0.00678 |
| Sonnet 5.5 | $0.00011 | $0.00339 |
| Haiku 4.5 | $0.00006 | $0.00170 |
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 18d 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 — 119 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.antigravityCliBinorconfig.environment.jetskiCliBin) 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_JETSKI === '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:
- Use centralized enums like
Agentsfromsrc/harness/config.ts(Agents.ANTIGRAVITY_CLI,Agents.JETSKI_CLI,Agents.CLAUDE_CODE,Agents.CODEX_CLI).
- Use centralized enums like
- Extract metadata from source-of-truth files:
- Never infer properties (such as
targetFileoragent) 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.
- 18d ago Changed d6047993ec13
- 21d ago Changed 455328f9c918
- 1mo ago Changed · -1 lines 007ddbd42308
- 1mo 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,202 stars, last pushed today), licensed Apache-2.0. It adds 56 tokens to every session and 1,696 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-08-30.
Other skills, from other repositories
autoreview
Structured code review through the shared OpenClaw agent-skills installation.
omh-code-review
This is an OMH code-review workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
revdiff-plan
Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…
re0-merge
Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…
explore-unknowns
Guide the user through a quadrant walk that maps the unknowns of a task — open by listing the known knowns, then work through known unknowns, unknown knowns, and unknown unknowns one stage at a time, ending with a complete four-quadrant map in the user's hands. Use when a request is ambiguous or underspecified, the…
asplos-writing-style
Use when drafting or revising ASPLOS prose — engineering the first two pages that rapid review actually reads, stating the cross-layer insight as one quotable sentence, structuring per-layer mechanism sections, writing bounded claims, and fitting everything into 11 self-contained pages that include figures and…