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 agentmods add commands/ip-dz/universal-change-review/review-changesgit clone --depth 1 https://github.com/IP-DZ/universal-change-reviewWrote 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/commands/ip-dz/universal-change-review/review-changes)<a href="https://agentmods.dev/commands/ip-dz/universal-change-review/review-changes"><img src="https://agentmods.dev/badge/commands/ip-dz/universal-change-review/review-changes.svg" alt="Measured on agentmods" 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.00000 | $0.00115 |
| Opus 5 | $0.00000 | $0.00057 |
| Sonnet 5 | $0.00000 | $0.00023 |
| Haiku 4.5 | $0.00000 | $0.00012 |
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 5d 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 the current repository changes using the Universal Change Review MCP tools.
Call changes_open_panel and provide its localhost URL for visual inspection. Then call changes_summary and inspect every behaviorally relevant or risky file with changes_diff. If a task snapshot id is available, call changes_since and separate task changes from pre-existing work. Report actionable findings first, ordered P0 through P3, with file and line evidence. Then summarize changed behavior, validation actually performed, and remaining risks. Do not edit files unless I explicitly ask you to fix a finding.
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.
- 5d ago First seen · 4 lines · 0 tokens per session scan A 18f9ea29121f
review-changes is a command published in the GitHub repository IP-DZ/universal-change-review (0 stars, last pushed 18d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 115 tokens. 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 commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
constitution
Create or update the project constitution from interactive or provided principle inputs.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.