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/pealmeida/anymodel-plugin/resultgit clone --depth 1 https://github.com/pealmeida/anymodel-pluginWhat 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 | $0.00014 | $0.00145 |
| Opus 5 | $0.00007 | $0.00072 |
| Sonnet 5 | $0.00003 | $0.00029 |
| Haiku 4.5 | $0.00001 | $0.00015 |
Grade A, and why
result 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 yesterday.
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
75% identical to result — 7 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
!node "${CLAUDE_PLUGIN_ROOT}/scripts/companion.mjs" result "$ARGUMENTS"
Present the full command output to the user. Do not summarize or condense it. Preserve all details including:
- Job ID and status
- The complete result payload, including verdict, summary, findings, details, artifacts, and next steps
- File paths and line numbers exactly as reported
- Any error messages or parse errors
- Follow-up commands such as
/anymodel:status <id>and/anymodel:review
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.
- yesterday First seen · 15 lines · 14 tokens per session scan A cca1adba01a8
result is a command published in the GitHub repository pealmeida/anymodel-plugin (0 stars, last pushed 24d ago), licensed Apache-2.0. It adds 14 tokens to every session and 145 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 75% identical to result, differing in 7 lines, and is treated as a copy.
Other commands, from other repositories
design
Design-space exploration tree. Wraps /cc-tree:tree with the design preset preselected — enumerates options × trade-offs × reversibility × cost × fit-with-constraints for an engineering / product / process decision. Produces a comparison table and a RECOMMENDED short-list. 中文触发：设计空间探索、方案对比与取舍、给出推荐短名单。.
step-research
Always research before proposing a fix. The Untether bug you're chasing is often a known upstream engine quirk, a previously-fixed regression, or a documented config gotcha.
step-classify
This is the canonical Untether issue-class table. Pick exactly one primary class per issue (the area where the root cause lives). If behaviour crosses boundaries, note a secondary class.
README
This directory is the canonical source for each step of Untether's 8-step deep debugging protocol. The parent command file at ../debug.md orchestrates the steps; each file here owns the detail for one step (or one shared output).
axstream-teach
Compile a UI task into a fast replayable macro (do it once, instant forever).
auto
AI auto strategy executor. Analyzes task and automatically selects and executes the best strategy: direct execution, hybrid-auto PRD generation, hybrid-worktree isolated development, or mega-plan multi-feature orchestration.