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 ambient-code/platform --skill gerrit-submitgit clone --depth 1 https://github.com/ambient-code/platformWrote 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/ambient-code/platform/gerrit-submit)<a href="https://agentmods.dev/skills/ambient-code/platform/gerrit-submit"><img src="https://agentmods.dev/badge/skills/ambient-code/platform/gerrit-submit/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/ambient-code/platform/gerrit-submit"><img src="https://agentmods.dev/badge/skills/ambient-code/platform/gerrit-submit.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.00058 | $0.00578 |
| Opus 5.5 | $0.00023 | $0.00231 |
| Sonnet 5.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 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.
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.
Copies of this mod
1 near-identical copy found in the catalogue:
- gerrit-submit — 100% identical, 0 lines differ
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.
- 1mo ago First seen · 66 lines · 58 tokens per session scan A 399e6b8dfc71
gerrit-submit is a skill published in the GitHub repository ambient-code/platform (131 stars, last pushed yesterday), licensed MIT. It adds 58 tokens to every session and 578 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
triage
Gatekeep and review GitHub issues and pull requests for Qwen Code maintainers. Use for GitHub Action issue triage, PR admission checks, product-direction review, KISS-focused PR review, and staged bilingual GitHub comments.
05-review
Review a diff read-only on three axes, code, behavior versus the plan, and relevancy, into one verdict report. Use before shipping a change. Not for fixing findings or auditing a codebase.
review
Use when operating as the Fabrik Review stage agent. This skill guides code review of an implementation, finding and fixing issues, and ensuring the PR is ready for human review.
review-comment
Use when operating as the Fabrik Review comment reviewer. This skill guides applying user decisions on review findings — fixing issues, dismissing false positives, or deferring items — then committing and pushing without signaling stage completion.
pr-gates
This skill should be used when the user asks to "open a PR", "prepare for review", "address review comments", "run gates", or "verify before pushing" in this repository. Enforces preflight/gate workflow, migration safety, and review-evidence closure.
pull-request-automation
Audits and improves the pull request workflow for a GitHub repository. Covers PR description templates, auto-labelling, CODEOWNERS, PR size checks, and branch protection rules. Invoked when the user asks to improve the PR process, set up PR automation, or add a PR template.