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/shyftlabs/continuumWrote 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/shyftlabs/continuum/pr-enhance)<a href="https://agentmods.dev/commands/shyftlabs/continuum/pr-enhance"><img src="https://agentmods.dev/badge/commands/shyftlabs/continuum/pr-enhance/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/commands/shyftlabs/continuum/pr-enhance"><img src="https://agentmods.dev/badge/commands/shyftlabs/continuum/pr-enhance.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.00000 | $0.00156 |
| Opus 5.5 | $0.00000 | $0.00062 |
| Sonnet 5.5 | $0.00000 | $0.00031 |
| Haiku 4.5 | $0.00000 | $0.00016 |
Grade A, and why
pr-enhance 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.
This is a copy
100% identical to pr-enhance — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
pr-enhance
AI-powered pull request enhancements.
Usage
npx claude-flow github pr-enhance [options]
Options
--pr-number <n>- Pull request number--add-tests- Add missing tests--improve-docs- Improve documentation--check-security- Security review
Examples
# Enhance PR
npx claude-flow github pr-enhance --pr-number 123
# Add tests
npx claude-flow github pr-enhance --pr-number 123 --add-tests
# Full enhancement
npx claude-flow github pr-enhance --pr-number 123 --add-tests --improve-docs
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 · 27 lines · 0 tokens per session scan A b295761f0a6f
pr-enhance is a command published in the GitHub repository shyftlabs/continuum (84 stars, last pushed 13d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 156 tokens. A static security scan graded it A with 0 findings. It is 100% identical to pr-enhance, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
align
Context-aware alignment. In plan mode it audits the active plan and folds the amendments in. Otherwise it reviews the branch, a named branch, or a pull request against Ion's principles, authors a fix plan, and after approval implements and commits the fixes.
resolve-dependabot-prs
Triage open Dependabot PRs, return a quick risk/action summary table, then enter planning mode with an ordered rebase→merge→follow-up→resume resolution plan.
review-branch
Review an existing branch holistically before merging — blast radius, conventions, security, and spec compliance.
work-pr
Creates a complete and well-documented Pull Request.
review-pr-staging
Staging review mode — comprehensive review of staging branch before deploy to main.
review-issue
Review and respond to a GitHub issue.