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/yeaight7/agent-powerupsWrote 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/yeaight7/agent-powerups/trace-regression)<a href="https://agentmods.dev/commands/yeaight7/agent-powerups/trace-regression"><img src="https://agentmods.dev/badge/commands/yeaight7/agent-powerups/trace-regression/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/yeaight7/agent-powerups/trace-regression"><img src="https://agentmods.dev/badge/commands/yeaight7/agent-powerups/trace-regression.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.00018 | $0.00200 |
| Opus 5.5 | $0.00007 | $0.00080 |
| Sonnet 5.5 | $0.00004 | $0.00040 |
| Haiku 4.5 | $0.00002 | $0.00020 |
Grade A, and why
trace-regression 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
Trace Regression
You are a regression analysis expert. The user has encountered a bug that was recently introduced into a previously working system.
Context
$ARGUMENTS
Investigation Strategy
- Understand the Regression: Compare the expected correct behavior with the new flawed behavior.
- Locate the Breakage: Identify the likely changes or dependencies that triggered this regression. Look for side effects, changed assumptions, or modified interfaces.
- Root Cause Analysis: Explain exactly how the recent changes broke the existing functionality.
- Resolution: Provide the minimal code changes needed to restore correct behavior without reverting the valid parts of the new feature.
- Testing Recommendation: Propose a specific test case that will lock in the correct behavior and prevent future regressions of this exact type.
Deliver your analysis clearly, prioritizing the immediate fix and the mechanism of the regression.
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 · 22 lines · 18 tokens per session scan A 372b766ae203
trace-regression is a command published in the GitHub repository yeaight7/agent-powerups (6 stars, last pushed 19d ago), licensed Apache-2.0. It adds 18 tokens to every session and 200 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-09-14.
Other commands, from other repositories
fix-issue
Fixes GitHub issues using parallel analysis agents for root cause investigation, code exploration, and regression detection. Reads issue context from gh CLI, searches codebase and memory for related patterns, generates a fix with tests, and links the resolution back to the issue via PR. Includes prevention analysis to…
hotfix
Emergency fix workflow. Manages a fast, safe patching process for production errors.
smart-commit
Generate and create a commit with a conventional commit message based on staged changes.
aidd-pr
Review a PR, resolve addressed comments, and generate /aidd-fix delegation prompts for remaining issues.
t800-fix
A command for making a narrow, predefined fix to existing agents, skills, commands, rules, or hooks. A fix-pack is a file listing the exact changes to make.
code-review
Code review — local uncommitted changes or GitHub PR (pass PR number/URL for PR mode).