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 skills add GerritCodeReview/gerrit-mcp-server --skill gerrit-workflowgit clone --depth 1 https://github.com/GerritCodeReview/gerrit-mcp-serverWrote 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/gerritcodereview/gerrit-mcp-server/gerrit-workflow)<a href="https://agentmods.dev/skills/gerritcodereview/gerrit-mcp-server/gerrit-workflow"><img src="https://agentmods.dev/badge/skills/gerritcodereview/gerrit-mcp-server/gerrit-workflow/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/gerritcodereview/gerrit-mcp-server/gerrit-workflow"><img src="https://agentmods.dev/badge/skills/gerritcodereview/gerrit-mcp-server/gerrit-workflow.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.00123 | $0.02003 |
| Opus 5.5 | $0.00049 | $0.00801 |
| Sonnet 5.5 | $0.00025 | $0.00401 |
| Haiku 4.5 | $0.00012 | $0.00200 |
Grade A, and why
gerrit-workflow scanned grade A 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 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
# Via curl (HTTP): How it starts
The opening of the file, as written. The whole thing — 248 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Gerrit Workflow
Gerrit is a code review system that sits in front of a git repository. The key difference from GitHub/GitLab: changes go through a review queue before landing in the branch. This changes several git workflows in important ways.
Core Concepts
Changes and Patch Sets
A Change is the unit of review in Gerrit — it corresponds to one logical commit. Each change has:
- A numeric Change number (e.g.,
12345) - A Change-Id trailer in the commit message (e.g.,
Change-Id: Ic8aaa0728a43936cd4c6e1ed590e01ba8f0fbf5b)
When a commit is revised and re-uploaded, the new version becomes a new patch
set on the same change. Gerrit associates them via the Change-Id trailer —
this is what makes the Change-Id essential.
The Magic refs/for/<branch> Ref
Gerrit intercepts pushes to refs/for/<branch>. These pushes never actually
create that ref; instead Gerrit creates or updates a Change for review. To land
code in master:
# NOT this (bypasses review):
git push origin HEAD:refs/heads/master
# This — submits for review:
git push origin HEAD:refs/for/master
The commit-msg Hook
Gerrit provides a commit-msg hook that auto-inserts Change-Id trailers.
Without it, the Change-Id must be added manually. To install:
# Via curl (HTTP):
curl -Lo .git/hooks/commit-msg <gerrit-url>/tools/hooks/commit-msg
chmod u+x .git/hooks/commit-msg
# Via scp (SSH):
scp -p -P 29418 <user>@<gerrit-host>:hooks/commit-msg .git/hooks/
chmod u+x .git/hooks/commit-msg
Check if it is already installed:
ls -la .git/hooks/commit-msg
Common Workflows
1. Create a New Change
# Make changes, then commit (hook adds Change-Id automatically)
git add <files>
git commit -m "Fix the foo widget"
# Verify Change-Id was added:
git log -1
# Push for review against a target branch:
git push origin HEAD:refs/for/master
The server prints the URL of the new change.
2. Update an Existing Change (New Patch Set)
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.
- 1mo ago First seen · 248 lines · 123 tokens per session scan A a1775e3b848e
gerrit-workflow is a skill published in the GitHub repository GerritCodeReview/gerrit-mcp-server (21 stars, last pushed 2d ago), licensed Apache-2.0. It adds 123 tokens to every session and 2,003 once invoked, about $0.0005 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
bump-version
Bump the Logic-Lens version across all six metadata locations at once (package.json, the four plugin manifests, and the README badge), then validate. Use when cutting a release or when npm run validate reports a version mismatch.
signals-scout-pr-follow-up
Follow-up Signals scout for recently merged pull requests. Works out whether each one has deployed, then checks the project's telemetry for whether it did what it claimed, had the impact it expected, or caused a side effect that needs a look.
signals-scout-skills-store
Skill-hygiene scout for the team's PostHog skills store. Watches recently-changed and most- used skills for authoring violations — vague descriptions, bloated bodies, dead file links, kitchen-sink scope, committed secrets.
swarm-pi-review
Review a Git working tree or branch with read-only Pi workers. Use standard for bugs, security, regressions, and missing tests; use lean for diff-bound simplification, deletion, reuse, YAGNI, or native replacements. Route one question to ask and broader risk analysis to orchestrate.
turning-engineering-analytics-into-insights
Converts engineering analytics (PR / CI) data into saved PostHog insights, dashboards, and subscriptions, and explains how to query the product data directly with SQL. Covers discovering per-team GitHub warehouse tables via engineering-analytics-sources, replicating curated column semantics in HogQL, reading exposed…
managing-endpoint-versions
Work safely with endpoint versions — preview a draft in the playground, roll back to an older version, update settings on one version without bumping query history, deactivate a specific version. Use when the user asks "how do I roll back my endpoint", "preview my changes before publishing", "I want to fix v5 without…