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 amplifthq/oh-my-dsh --skill review-changesgit clone --depth 1 https://github.com/amplifthq/oh-my-dshWrote 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/amplifthq/oh-my-dsh/review-changes)<a href="https://agentmods.dev/skills/amplifthq/oh-my-dsh/review-changes"><img src="https://agentmods.dev/badge/skills/amplifthq/oh-my-dsh/review-changes/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/amplifthq/oh-my-dsh/review-changes"><img src="https://agentmods.dev/badge/skills/amplifthq/oh-my-dsh/review-changes.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.00022 | $0.00157 |
| Opus 5 | $0.00011 | $0.00078 |
| Sonnet 5 | $0.00004 | $0.00031 |
| Haiku 4.5 | $0.00002 | $0.00016 |
Grade A, and why
review-changes 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 10d 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
Review changes
- Establish the intended behavior from the request and repository guidance.
- Inspect the complete relevant diff, including staged, unstaged, and newly added files.
- Trace changed data and control flow into callers and tests.
- Report only actionable findings caused by the change. Rank them by impact and cite exact files and lines.
- Verify suspected bugs against code or a focused reproduction; do not report style preferences as defects.
- If there are no findings, state that directly and name any verification gap that remains.
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.
- 10d ago First seen · 15 lines · 22 tokens per session scan A 4b010df267ff
review-changes is a skill published in the GitHub repository amplifthq/oh-my-dsh (15 stars, last pushed 4d ago), licensed MIT. It adds 22 tokens to every session and 157 once invoked, about $0.0001 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
code-review-cn
A Chinese-language guide for reviewing code changes, pull requests, and diffs. It prioritizes correctness, resource cleanup, security, matching documentation, and tests before style.
refactor-safely
A safe code-refactoring guide for changing code structure while keeping its external behavior the same. Refactoring means reorganizing code without changing what it does.
pr-description
A writing guide for pull request descriptions. A pull request is a proposed set of code changes for review and merging.
dsh-code-review
Use when reviewing a pull request in the deepseek-harness repo — orients the reviewer to this codebase's standards (AGENTS.md conventions, defensive patterns, ADRs, quality gates) and the review-specific checks that code alone can't show.
dsh-find-simplifications
Use when working in the deepseek-harness repo to find non-obvious simplification candidates, remove redundant comments or implementation-heavy documentation, write proposed Agent Notes or inline TODO/FIXME/XXX notes, audit or coalesce superseded Agent Notes, or fold worthwhile simplification ideas from another PR…
modsearch
Plug-in web search, X (Twitter) search, and page fetch for models without native web access. Use whenever the task needs current information, external facts, source links, posts from X, or the content of a specific URL, and the active model/harness has no native search or fetch tool. Runs the modsearch CLI to return…