Chromium is an open-source web browser project and the official GitHub mirror of its source code. It is used to build and maintain software for browsing the web, with documentation and code for products such as Chrome and Android WebView.
Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/chromium/chromiumnpx agentmods add skills/chromium/chromium/blink-gc-pluginWrote 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/chromium/chromium/blink-gc-plugin)<a href="https://agentmods.dev/skills/chromium/chromium/blink-gc-plugin"><img src="https://agentmods.dev/badge/skills/chromium/chromium/blink-gc-plugin/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/chromium/chromium/blink-gc-plugin"><img src="https://agentmods.dev/badge/skills/chromium/chromium/blink-gc-plugin.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.00079 | $0.04298 |
| Opus 5.5 | $0.00032 | $0.01719 |
| Sonnet 5.5 | $0.00016 | $0.00860 |
| Haiku 4.5 | $0.00008 | $0.00430 |
Grade C, and why
blink-gc-plugin scanned grade C with 1 finding 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 8d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf third_party/llvm-build/Release+Asserts/ third_party/llvm-build/force_head_revision How it starts
The opening of the file, as written. The whole thing — 339 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Blink GC Clang Plugin Development
This skill covers the end-to-end workflow for modifying the Blink GC (Oilpan)
Clang plugin in //tools/clang/blink_gc_plugin/, testing it locally, fixing or
suppressing violations across the codebase, rolling out the changes, and
cleaning up the local environment afterwards.
1. Key Files and Architecture
- Plugin Entry Point & AST Consumer:
- BlinkGCPlugin.cpp and BlinkGCPluginOptions.h: Plugin registration, command-line option definitions, and argument parsing.
- BlinkGCPluginConsumer.h
and
BlinkGCPluginConsumer.cpp:
Main
ASTConsumerthat orchestrates declaration collection, record/method validation, visitor checks, and AST matcher checks. - CollectVisitor.h and
CollectVisitor.cpp:
RecursiveASTVisitorthat collects record declarations and tracing method definitions in the translation unit.
- Record & Points-To Edge Model:
- RecordInfo.h and RecordInfo.cpp: Caches record properties (whether a type is garbage-collected, traceable, stack-allocated, or has fields/bases requiring tracing).
- Edge.h,
Edge.cpp,
NeedsTracing.h, and
TracingStatus.h: Models the
type/field edge graph (
Value,RawPtr,RefPtr,UniquePtr,Member,WeakMember,Persistent,CrossThreadPersistent,Collection,Iterator,ArrayEdge, etc.),EdgeVisitor/RecursiveEdgeVisitor, and tracing requirements.
- Visitor-Based Checks:
- CheckFieldsVisitor.h
and
CheckFieldsVisitor.cpp:
RecursiveEdgeVisitorthat validates class fields (e.g. disallowing raw,scoped_refptr, orunique_ptrpointers to GC-managed/traceable types, disallowingMemberin unmanaged classes, disallowing pointers from heap types to stack-allocated types, and disallowing GC-derived part objects). - CheckForbiddenFieldsVisitor.h
and
CheckForbiddenFieldsVisitor.cpp:
RecursiveEdgeVisitorthat checks that GC-managed classes and their embedded objects do not contain forbidden fields (such asTaskRunneror MojoRemote/Receivertypes). - CheckGCRootsVisitor.h
and
CheckGCRootsVisitor.cpp:
RecursiveEdgeVisitorthat checks that on-heap classes and their part objects do not contain GC roots (Persistent). - CheckTraceVisitor.h and
CheckTraceVisitor.cpp:
RecursiveASTVisitorthat inspectsTracemethod bodies to verify all required bases and fields are traced. - CheckDispatchVisitor.h
and
CheckDispatchVisitor.cpp:
RecursiveASTVisitorthat verifies manual dispatch inTraceAfterDispatchandFinalizeGarbageCollectedObjectmethods. - CheckFinalizerVisitor.h
and
CheckFinalizerVisitor.cpp:
RecursiveASTVisitorthat checks destructors/finalizers do not access potentially finalized fields.
- CheckFieldsVisitor.h
and
CheckFieldsVisitor.cpp:
- AST Matcher-Based Checks:
- BadPatternFinder.h and
BadPatternFinder.cpp:
Clang AST matchers for disallowed patterns involving Oilpan types (such as
std::optional,absl::optional,std::variant,absl::variant,base::raw_ptr,base::raw_ref,std::unique_ptr,base::WeakPtr, off-heap collections,Memberon stack, GCed variables/fields by value, and extra padding).
- BadPatternFinder.h and
BadPatternFinder.cpp:
Clang AST matchers for disallowed patterns involving Oilpan types (such as
- Configuration, Diagnostics, Graph Dumping, and Tests:
- Config.h and
Config.cpp: Helpers for
identifying Oilpan types, annotations (
STACK_ALLOCATED,GC_PLUGIN_IGNORE), and smart pointer/collection names. - DiagnosticsReporter.h and DiagnosticsReporter.cpp: Diagnostic message templates and reporting methods.
- JsonWriter.h and
process-graph.py:
Utilities for dumping (
dump-graph) and processing the object graph. //tools/clang/blink_gc_plugin/tests/: Lit-style golden tests (.cpp,.h, optional.flags, and expected.txtoutput files) run via test.py.
- Config.h and
Config.cpp: Helpers for
identifying Oilpan types, annotations (
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.
- 8d ago First seen · 339 lines · 79 tokens per session scan C 37aa7ee3549b
blink-gc-plugin is a skill published in the GitHub repository chromium/chromium (25,043 stars, last pushed today), licensed BSD-3-Clause. It adds 79 tokens to every session and 4,298 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-08.
Other skills, from other repositories
karma-skill
Generates Karma test runner configurations for browser-based JavaScript testing. Works with Jasmine, Mocha, or QUnit. Use when user mentions "Karma", "karma.conf.js", "browser test runner". Triggers on: "Karma", "karma.conf", "karma test runner", "browser-based JS test".
loom-c
C language expertise (C11/C17/C23) for memory-safe, portable, production-quality systems code.
hashiiiii-zig
Use when writing, editing, or reviewing Zig implementation, tests, build files, or CI.
cpp-development
Modern C++ (17/20+) standards based on Core Guidelines, RAII, and GoogleTest.
cpp-project-setup
Modern C++ project setup: CMake/CMakePresets, vcpkg, Ninja, VS Code/clangd, GoogleTest, clang-format/tidy, Doxygen, CI, macOS/Linux/Windows. Use for bootstrapping or modernizing host-side C++ apps and libraries; prefer embedded-project-setup for MCU firmware and cross-debug flows.
cpp-testing
C++ testing workflow for unit and integration tests: GoogleTest/GoogleMock, CMake/CTest integration, diagnosing flaky tests, and running sanitizers and coverage for correctness signal. Use when writing or fixing C++ tests and test infrastructure.