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 find-dependenciesgit 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/find-dependencies)<a href="https://agentmods.dev/skills/gerritcodereview/gerrit-mcp-server/find-dependencies"><img src="https://agentmods.dev/badge/skills/gerritcodereview/gerrit-mcp-server/find-dependencies.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Prompt Injection · line 22 Large whitespace padding was detected (a block of blank lines or a long run of spaces). This can push injected instructions below or to the right of the visible area so a human reviewer never sees them while the agent still reads them. Manual review of the hidden content is recommended.Fix: Remove the large whitespace padding (blank-line blocks or long space runs) and review any content hidden below or to the right of it. Keep skill files compact and reviewable so no instructions can be
- medium Prompt Injection · line 98 Large whitespace padding was detected (a block of blank lines or a long run of spaces). This can push injected instructions below or to the right of the visible area so a human reviewer never sees them while the agent still reads them. Manual review of the hidden content is recommended.Fix: Remove the large whitespace padding (blank-line blocks or long space runs) and review any content hidden below or to the right of it. Keep skill files compact and reviewable so no instructions can be
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.00071 | $0.01130 |
| Opus 5 | $0.00036 | $0.00565 |
| Sonnet 5 | $0.00014 | $0.00226 |
| Haiku 4.5 | $0.00007 | $0.00113 |
Grade A, and why
find-dependencies 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 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.
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.
How it starts
The opening of the file, as written. The whole thing — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
find-dependencies
Find and interpret the full dependency picture for one or more Gerrit changes.
The tools get_depends_on and get_dependents are provided by the
gerrit_mcp_server_depends_on extension. They are available whenever
gerrit-mcp-server is running with the depends-on extension installed and a
configured Gerrit host that has the depends-on plugin enabled.
Dependency types
| Type | Source | Tool |
|---|---|---|
| Depends-on | Explicit Depends-on: annotation in the change message, parsed by the depends-on plugin |
get_depends_on |
| Git-chain parent | Implicit: this change's commit has a parent commit that is also an open Gerrit change | get_git_parent_changes |
A dependency can be resolved (mapped to a numeric change ID) or
unresolved (only has an I... change key ("Change-Id") that couldn't be
matched to a change in the configured deliverables).
Quick reference
| Goal | What to do |
|---|---|
| What does change X depend on? | get_depends_on(X) + get_git_parent_changes(X) in parallel |
| Which changes depend on X? | get_dependents(X) |
| Are all dependencies merged? | Get deps, then get_change_details on each; check status |
| Full dependency chain | Recurse: get deps, then get deps-of-deps (track visited IDs) |
| Set of changes | Call both tools for each change ID in parallel, deduplicate |
Workflow: single change
- Call
get_depends_on(change_id)andget_git_parent_changes(change_id)in parallel. - Merge the results:
- From
get_depends_on: each entry withresolved: truehas achange_number; unresolved entries have a Change-Id inunresolved. - From
get_git_parent_changes: each entry is an open parent change (or null if the parent commit is not a tracked Gerrit change, e.g. a merged branch tip).
- From
- For each resolved dependency, optionally call
get_change_detailsto show its status (open / merged / abandoned) and subject. - Present as a structured list grouping Depends-on and git-chain deps separately.
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 · 103 lines · 71 tokens per session scan A 88457d89ed0a
find-dependencies is a skill published in the GitHub repository GerritCodeReview/gerrit-mcp-server (20 stars, last pushed 4d ago), licensed Apache-2.0. It adds 71 tokens to every session and 1,130 once invoked, about $0.0004 per session on Opus 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
review-implement-phase
Implements triaged review actions, commits focused fixes, and posts Done plus resolves threads. Use when the user wants only the implementation phase of the review-framework workflow.
engram-branch-pr
PR creation workflow for Engram following the issue-first enforcement system. Trigger: When creating a pull request, opening a PR, or preparing changes for review.
verify-behavior
Verify or reproduce visible product behavior by driving the real UI with pi-computer-use's checked tools, requiring verified expect postconditions and durable state evidence for meaningful UI flows. Use when triage needs visual reproduction, implementation needs behavioral proof, review needs interactive confirmation…
github-contributor
End-to-end playbook for shipping high-quality pull requests to open-source projects you don't maintain — discovery, CONTRIBUTING compliance, PR-size check, minimal-diff implementation, PR description with AI-assisted disclosure, conflict resolution, and post-submission maintainer interaction. Use whenever creating…
revdiff
Review diffs, files, and documents with inline annotations in a TUI overlay, or answer questions about revdiff usage, configuration, themes, and keybindings. Opens revdiff in agterm/tmux/zellij/herdr/kitty/wezterm/cmux/ghostty/iterm2/emacs-vterm, captures annotations, and addresses them. Works in git, hg, and jj repos…
write-pr
Reference standards for writing pull request titles and descriptions in the tldraw repository, plus the pre-flight comment sweep over the diff. Use as supporting guidance when another skill or workflow needs PR content standards, not as the user-facing create/update PR workflow.