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-submitnpx skills add openshift-online/agent-control-plane --skill gerrit-submitgit 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-submit)<a href="https://agentmods.dev/skills/openshift-online/agent-control-plane/gerrit-submit"><img src="https://agentmods.dev/badge/skills/openshift-online/agent-control-plane/gerrit-submit.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.00058 | $0.00578 |
| Opus 5 | $0.00029 | $0.00289 |
| Sonnet 5 | $0.00012 | $0.00116 |
| Haiku 4.5 | $0.00006 | $0.00058 |
Grade A, and why
gerrit-submit 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 5d 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-submit — 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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Gerrit Change Submission
Guide for preparing and submitting Gerrit changes for merge.
Prerequisites
The Gerrit MCP server must be available and the user must have submit permissions on the target project.
Pre-submission checklist
Before submitting, verify all requirements are met using mcp__gerrit__fetch_gerrit_change:
-
Labels satisfied — All required labels have sufficient votes:
- Code-Review: typically needs +2
- Verified: typically needs +1
- Any project-specific labels (check the change's
submit_requirements)
-
No unresolved comments — All inline comments must be resolved or addressed
-
Mergeable — The change can be merged without conflicts (check the
mergeablefield) -
Up to date — The change is based on the current branch head (rebase if needed)
Workflow
1. Check readiness
Fetch the change and examine:
submittablefield — true if all requirements are metsubmit_requirements— list of conditions and their statuslabels— current votes- Unresolved comment count
If not submittable, report what's missing and stop.
2. Rebase if needed
If the change is not based on the current branch head:
- The Gerrit MCP server's submit operation may auto-rebase depending on project settings
- If conflicts exist, the change owner must resolve them manually and upload a new patch set
3. Submit
Use mcp__gerrit__submit_gerrit_review with the appropriate approval labels if you need to add final votes before submitting.
Submission itself happens through the Gerrit REST API. If the MCP server provides a submit tool, use it. Otherwise, inform the user to submit via the Gerrit web UI.
4. Post-submit
After successful submission:
- Verify the change shows status MERGED
- Check if there are dependent changes that can now be submitted (submitted_together)
- Notify the user of the merge commit hash if available
Common issues
- Missing votes: Check which labels are blocking and who can provide them
- Merge conflicts: The owner needs to rebase and resolve conflicts locally
- Submit rules: Some projects have custom submit rules (e.g., require Verified from CI)
- Permission denied: The user may not have submit permissions — check with project admin
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.
- 5d ago First seen · 66 lines · 58 tokens per session scan A 399e6b8dfc71
gerrit-submit is a skill published in the GitHub repository openshift-online/agent-control-plane (11 stars, last pushed 2d ago), licensed MIT. It adds 58 tokens to every session and 578 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-submit, 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.