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.
git clone --depth 1 https://github.com/dp-web4/SAGEWrote 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/dp-web4/sage/repo-analyze)<a href="https://agentmods.dev/commands/dp-web4/sage/repo-analyze"><img src="https://agentmods.dev/badge/commands/dp-web4/sage/repo-analyze.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.00157 |
| Opus 5 | $0.00000 | $0.00078 |
| Sonnet 5 | $0.00000 | $0.00031 |
| Haiku 4.5 | $0.00000 | $0.00016 |
Grade A, and why
repo-analyze 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.
The source is not reproduced here
Licensed AGPL-3.0
The repository is licensed AGPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
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 · 26 lines · 0 tokens per session scan A 7c57c22d09ee
repo-analyze is a command published in the GitHub repository dp-web4/SAGE (25 stars, last pushed today), licensed AGPL-3.0. It costs nothing until one of its globs matches a file; then it loads 157 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-30.
Other commands, from other repositories
hatch3r-pr-resolve
Read open PR comments, evaluate each against current code via the rigor contract, implement accepted findings, reply inline. Multi-platform.
hatch3r-rework
User-guided rework planning for agent-implemented code in a fresh context window. Reconstructs what was delivered from the git diff, interviews the user for feedback, triages findings, validates them read-only against the code, and ends at a rework plan (docs/rework/) plus an execute-now-or-defer choice (copy-paste…
code-review
Code review — local uncommitted changes or GitHub PR (pass PR number/URL for PR mode).
python-review
Comprehensive Python code review for PEP 8 compliance, type hints, security, and Pythonic idioms. Invokes the python-reviewer agent.
santa-loop
Adversarial dual-review convergence loop — two independent model reviewers must both approve before code ships.
pr
Create a GitHub PR from current branch with unpushed commits — discovers templates, analyzes changes, pushes.