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/openshift-online/agent-control-plane/gerrit-createnpx skills add openshift-online/agent-control-plane --skill gerrit-creategit clone --depth 1 https://github.com/openshift-online/agent-control-planeWrote 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/openshift-online/agent-control-plane/gerrit-create)<a href="https://agentmods.dev/skills/openshift-online/agent-control-plane/gerrit-create"><img src="https://agentmods.dev/badge/skills/openshift-online/agent-control-plane/gerrit-create.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.1 | $0.00063 | $0.00679 |
| Opus 5 | $0.00032 | $0.00340 |
| Sonnet 5 | $0.00013 | $0.00136 |
| Haiku 4.5 | $0.00006 | $0.00068 |
Grade A, and why
gerrit-create 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 6d 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.
This is a copy
100% identical to gerrit-create — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Creating and Updating Gerrit Changes
Guide for pushing code changes to Gerrit for review.
Prerequisites
The Gerrit MCP server must be available and git must be configured with the appropriate remote.
Creating a new change
Gerrit changes are created by pushing commits to a special ref:
git push origin HEAD:refs/for/<target-branch>
Before pushing
-
Commit message format: Gerrit requires a
Change-Idfooter in the commit message. If the Gerrit commit-msg hook is installed, it adds this automatically. If not:Subject line (50 chars max) Body explaining what and why (wrapped at 72 chars). Change-Id: I<40-char-hex> -
Single commit per change: Each commit becomes one Gerrit change. Squash work-in-progress commits before pushing.
-
Target branch: Usually
mainormaster, but verify the project's default branch.
Push options
Add metadata via push options:
git push origin HEAD:refs/for/main \
-o topic=my-feature \
-o [email protected] \
-o [email protected] \
-o wip
topic=<name>— group related changesr=<email>— add reviewercc=<email>— add CCwip— mark as work-in-progressready— mark as ready for reviewhashtag=<tag>— add hashtag
Updating an existing change
To upload a new patch set for an existing change:
-
Amend the commit (keep the same Change-Id):
git commit --amend -
Push again:
git push origin HEAD:refs/for/main
Gerrit matches the Change-Id to the existing change and creates a new patch set.
Managing change metadata
After a change exists, use mcp__gerrit__submit_gerrit_review to:
- Add comments explaining what changed in the new patch set
- Vote on your own change (if allowed by project settings)
- Reply to reviewer comments
Use mcp__gerrit__fetch_gerrit_change to verify the change was created/updated correctly.
Common issues
- Missing Change-Id: Install the commit-msg hook:
gitdir=$(git rev-parse --git-dir); scp -p -P 29418 <user>@<host>:hooks/commit-msg ${gitdir}/hooks/ - Push rejected (not permitted): Check project permissions and target branch
- Merge conflict on push: Rebase on the target branch first
- Change already merged: The Change-Id was reused — create a new commit with a fresh Change-Id
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.
- 6d ago First seen · 86 lines · 63 tokens per session scan A 06de6248f173
gerrit-create is a skill published in the GitHub repository openshift-online/agent-control-plane (11 stars, last pushed 2d ago), licensed MIT. It adds 63 tokens to every session and 679 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to gerrit-create, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
interview
Ask one useful structured question at a time only when material product/implementation choices are genuinely missing; remember answers and produce a brief/spec. Discoverable facts should be investigated instead of asked.
ppt-review
Read this skill only after current officereview structural output and relevant rendered images exist. Do not use source code, a tool success flag, or the first-slide preview as a substitute for deck evidence.
package-installer
Install third-party open-source projects (a GitHub URL or a local git directory the user provides) as external packages. The project is cloned verbatim into the per-user packages directory — never edit, normalize, or reorganize its files.
cog-knowledge-consolidation
Build structured knowledge frameworks from scattered vault notes with source attribution.
helmor-debug-operate
Operate, reproduce, and debug a running local Helmor desktop development build through the Tauri MCP bridge. Use when the user asks to use Tauri MCP, towery MCP, the local dev build, the Tauri webview, visual end-to-end validation, UI automation, screenshots, DOM/accessibility snapshots, IPC or log tracing…
review
5-pass structured code review — correctness, security, performance, readability, consistency.