Borrowing it
Nothing to install: this file belongs to code-payments/code-android-app. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/code-payments/code-android-app/code/cash/.claude/skills/dep-review/SKILL.mdgit clone --depth 1 https://github.com/code-payments/code-android-appWrote 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/code-payments/code-android-app/dep-review)<a href="https://agentmods.dev/skills/code-payments/code-android-app/dep-review"><img src="https://agentmods.dev/badge/skills/code-payments/code-android-app/dep-review/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/code-payments/code-android-app/dep-review"><img src="https://agentmods.dev/badge/skills/code-payments/code-android-app/dep-review.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.00031 | $0.01489 |
| Opus 5.5 | $0.00012 | $0.00596 |
| Sonnet 5.5 | $0.00006 | $0.00298 |
| Haiku 4.5 | $0.00003 | $0.00149 |
Grade A, and why
dep-review 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.
How it starts
The opening of the file, as written. The whole thing — 181 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dependency Update Review
Review a Dependabot pull request to evaluate the dependency update for breaking changes, deprecations, and required code modifications.
Input
Parse $ARGUMENTS for a PR reference:
#803or803— PR numberhttps://github.com/code-payments/code-android-app/pull/803— full URL (extract the number)
If no argument is provided, stop and ask the user for a PR number.
Steps
Step 1 — Fetch PR details
gh pr view <number> --repo code-payments/code-android-app --json title,body,files,headRefName,baseRefName,diff
Extract:
- Title — Dependabot titles follow:
Bump <group-or-artifact> from X.Y.Z to A.B.C - Body — Contains Dependabot's auto-generated release notes, changelog links, and compatibility scores
- Changed files — Typically
gradle/libs.versions.tomland possiblybuild.gradle.ktsfiles - Diff — The actual version change
If the PR is not a Dependabot PR (author is not dependabot[bot] or title doesn't match the pattern), warn the user but continue — they may want to review a manual dependency bump.
Step 2 — Parse the version change
From the diff of gradle/libs.versions.toml, identify:
- Catalog key — the version alias (e.g.,
grpc = "1.68.0"→grpc) - Old version — the version being replaced
- New version — the version being introduced
- Affected libraries — all
[libraries]entries that reference this version alias
If multiple versions are bumped (grouped Dependabot PR), repeat the analysis for each.
Present a summary table:
| Catalog Key | Library | Old Version | New Version | Bump Type |
|---|---|---|---|---|
grpc |
io.grpc:grpc-okhttp |
1.68.0 | 1.69.0 | minor |
Bump type classification:
- patch (0.0.x) — bug fixes, lowest risk
- minor (0.x.0) — new features, backward compatible
- major (x.0.0) — potential breaking changes, highest risk
Step 3 — Fetch release notes / changelog
For each dependency being bumped:
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 Changed 6542ca95a6b1
- 2mo ago First seen · 181 lines · 31 tokens per session scan A 42e66e7b2359
dep-review is a skill published in the GitHub repository code-payments/code-android-app (23 stars, last pushed today), licensed MIT. It adds 31 tokens to every session and 1,489 once invoked, about $0.0001 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
autoreview
Structured code review through the shared OpenClaw agent-skills installation.
omh-code-review
This is an OMH code-review workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
revdiff-plan
Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…
explore-unknowns
Guide the user through a quadrant walk that maps the unknowns of a task — open by listing the known knowns, then work through known unknowns, unknown knowns, and unknown unknowns one stage at a time, ending with a complete four-quadrant map in the user's hands. Use when a request is ambiguous or underspecified, the…
re0-merge
Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…
asplos-writing-style
Use when drafting or revising ASPLOS prose — engineering the first two pages that rapid review actually reads, stating the cross-layer insight as one quotable sentence, structuring per-layer mechanism sections, writing bounded claims, and fitting everything into 11 self-contained pages that include figures and…