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/hi0001234d/coding-agent-mcp-toolsWrote 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/hi0001234d/coding-agent-mcp-tools/predict)<a href="https://agentmods.dev/commands/hi0001234d/coding-agent-mcp-tools/predict"><img src="https://agentmods.dev/badge/commands/hi0001234d/coding-agent-mcp-tools/predict/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/hi0001234d/coding-agent-mcp-tools/predict"><img src="https://agentmods.dev/badge/commands/hi0001234d/coding-agent-mcp-tools/predict.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.00029 | $0.00549 |
| Opus 5.5 | $0.00012 | $0.00220 |
| Sonnet 5.5 | $0.00006 | $0.00110 |
| Haiku 4.5 | $0.00003 | $0.00055 |
Grade A, and why
autoresearch:predict 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
EXECUTE IMMEDIATELY — do not deliberate, do not ask clarifying questions before reading the protocol.
Argument Parsing (do this FIRST)
Extract these from $ARGUMENTS — the user may provide extensive context alongside flags. Ignore prose and extract ONLY flags/config:
--scope <glob>orScope:— file globs to analyze--chain <targets>orChain:— comma-separated: debug,security,fix,ship,scenario--depth <level>orDepth:— shallow (3 personas, 1 round), standard (5, 2), deep (8, 3)--personas N— number of personas (3-8)--rounds N— debate rounds (1-3)--adversarial— use red team personas--budget <N>— max total findings across all personas (default: 40)--fail-on <severity>— CI/CD gate--incremental— reuse existing knowledge files, update only changed files--goal <text>orGoal:— focus area for analysisIterations:or--iterations N— integer for bounded mode (CRITICAL: run exactly N iterations then stop)
If Iterations: N or --iterations N is found, set max_iterations = N. Track current_iteration starting at 0. After iteration N, print final summary and STOP.
All remaining text not matching flags is the goal/focus description.
Execution
- Read the predict workflow:
.claude/skills/autoresearch/references/predict-workflow.md - If scope or goal is missing — use
AskUserQuestionwith batched questions per predict-workflow.md - Execute the 8-phase predict workflow
- If bounded: after each iteration, check
current_iteration < max_iterations. If not, STOP and print summary. - If
--chainis set, hand off to each chained command sequentially
Stream all output live — never run in background.
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 · 38 lines · 29 tokens per session scan A 3e3cdc66d3ca
autoresearch:predict is a command published in the GitHub repository hi0001234d/coding-agent-mcp-tools (11 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 29 tokens to every session and 549 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-08-31.
Other commands, from other repositories
refactor
Systematic code refactoring with smart scope detection.
review-branch
Review the current branch's diff against base by dispatching atomic-reviewer. No orchestration loop, no spec required — pre-flight before /commit pr or /commit merge.
init
Install the formatters this repository needs, with every command visible before it runs.
spec-trace-requirements
You are verifying that implementation changes trace back to specification requirements.
merge-conflict-analysis
You are analyzing merge conflicts for PR #${{ pr-number }}.
boot
Start a new PromptKit prompt assembly session (alias for /bootstrap).