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 Arnosdeus/agent-toolkit --skill git-reviewgit clone --depth 1 https://github.com/Arnosdeus/agent-toolkitWrote 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/arnosdeus/agent-toolkit/git-review)<a href="https://agentmods.dev/skills/arnosdeus/agent-toolkit/git-review"><img src="https://agentmods.dev/badge/skills/arnosdeus/agent-toolkit/git-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/arnosdeus/agent-toolkit/git-review"><img src="https://agentmods.dev/badge/skills/arnosdeus/agent-toolkit/git-review.svg" alt="Reviewed on agentmods" width="80" 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.00030 | $0.00177 |
| Opus 5.5 | $0.00012 | $0.00071 |
| Sonnet 5.5 | $0.00006 | $0.00035 |
| Haiku 4.5 | $0.00003 | $0.00018 |
Grade A, and why
git-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.
What it actually says
Git Review
Procedure and output
Review status, staged and unstaged diffs, tracked paths, and the final commit
boundary. Report BLOCKER, MAJOR, MINOR, or NOTE findings as
path — issue — evidence — action, then state whether the tree is safe to commit.
Inspect status, staged and unstaged diffs, changed files, ignored files, and history relevant to the task. Check for secrets, generated output, unrelated changes, dependency or lockfile changes, migrations, tests, and documentation. Never reset work, force-push, rewrite history, or delete unrelated changes unless explicitly instructed. Report any remaining uncertainty.
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 · 19 lines · 30 tokens per session scan A 6b3233c084be
git-review is a skill published in the GitHub repository Arnosdeus/agent-toolkit (2 stars, last pushed 1mo ago), licensed MIT. It adds 30 tokens to every session and 177 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-31.
Other skills, from other repositories
changes-report
Report all repository changes that entered a target branch during one required date or period, grouped by product change and written as plain English for a broad audience. Use for daily, weekly, date-range, or relative-period change summaries rather than explaining one known diff.
coderabbit-triage
Triage unresolved CodeRabbit feedback on the current GitHub pull request. Use for read-only disposition and, only when separately authorized, scoped remediation and remote thread closure.
roadmap-task-deliver
Deliver the first eligible unfinished roadmap task through implementation, review, green CI, PR merge, and a task-status update. Use for autonomous delivery from local roadmap and task files. Files can be outside the code repository or outside Git.
jira-issue-deliver
Autonomously deliver one Jira issue from intake to a ready GitHub pull request. Use only when the user authorizes implementation, commits, pushes, PR state changes, CI remediation, and resolution of requested automated review feedback.
plan-deliver
Autonomously deliver an approved implementation plan to a ready GitHub pull request. Use when the user supplies a plan in the conversation or a file and authorizes implementation, commits, pushes, PR state changes, CI remediation, and resolution of requested automated review feedback; use jira-issue-deliver when the…
pr-draft
Publish confirmed local changes as a monitored GitHub draft pull request. Use only when the user authorizes branch creation, scoped staging, commit, push, draft PR creation, and CI follow-up.