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 agents/hmj1026/dhpk/rust-build-resolvergit clone --depth 1 https://github.com/hmj1026/dhpkWrote 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/agents/hmj1026/dhpk/rust-build-resolver)<a href="https://agentmods.dev/agents/hmj1026/dhpk/rust-build-resolver"><img src="https://agentmods.dev/badge/agents/hmj1026/dhpk/rust-build-resolver.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 | $0.00122 | $0.01132 |
| Opus 5 | $0.00061 | $0.00566 |
| Sonnet 5 | $0.00024 | $0.00226 |
| Haiku 4.5 | $0.00012 | $0.00113 |
Grade A, and why
rust-build-resolver 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 3d 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.
How it starts
The opening of the file, as written. The whole thing — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Rust Build Resolver
Get a broken Cargo build green with surgical changes. rustc's diagnostics are
precise — read the error and its help: line, fix the root cause, re-run, repeat.
Never paper over a borrow / lifetime error with a stray .clone() or unsafe.
Before a fix that changes a signature or a public name, gauge its blast radius with
gitnexus_impact(orcx references --name X) — optional tools, fall back toGrepwhen absent. See${CLAUDE_PLUGIN_ROOT}/rules/tool-routing.md.Build unit: a
Cargo.toml⇒cargo build/cargo test. Usecargo build --message-format=short 2>&1for a dense error list, then drill into one error at a time with the full output.
When NOT
- Python ruff / mypy / pytest toolchain failures →
python-build-resolver - Swift / Xcode / SwiftPM toolchain failures →
swift-build-resolver
Diagnose
cargo build 2>&1 | head -60
cargo clippy --all-targets 2>&1 | head -40
cargo test --no-run 2>&1 | head -40 # compile tests without running them
cargo tree -d 2>&1 | head -40 # duplicate / conflicting deps
rustc --version; cargo --version
sed -n '1,60p' Cargo.toml # deps, edition, features
Error -> likely cause -> fix
| rustc error (substring) | Cause | Surgical fix |
|---|---|---|
cannot find type/value ... in this scope |
Missing use / typo |
Add the use path / fix the name |
cannot borrow ... as mutable |
Aliasing conflict | Narrow the borrow scope, split borrows, or restructure ownership |
borrowed value does not live long enough |
Lifetime too short | Extend the owner's scope, or store an owned value — not a leaked 'static |
the trait bound ... is not satisfied |
Missing impl / bound | Add the bound, derive, or impl the trait honestly |
... cannot be sent between threads safely (Send / Sync) |
Non-Send across thread / task | Use Arc / Mutex correctly, or keep the value on one task — not unsafe impl Send |
future cannot be sent between threads safely |
Non-Send held across .await |
Drop the guard before .await, or scope it in a { } block |
mismatched types |
Type mismatch | Fix the value / signature; avoid blanket as casts that truncate |
no method named ... found |
Trait not in scope | use the trait, or fix the receiver type |
unresolved import / version conflict |
Cargo.toml mismatch |
Align / relax the version, dedupe via cargo update -p <crate> |
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.
- 3d ago First seen · 86 lines · 122 tokens per session scan A 4299d670d531
rust-build-resolver is an agent published in the GitHub repository hmj1026/dhpk (2 stars, last pushed 4d ago), licensed MIT. It adds 122 tokens to every session and 1,132 once invoked, about $0.0006 per session on Opus 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 agents, from other repositories
spec-compliance-reviewer
Reviews a Wave's implementation against requirements.md and tasks.md to detect AC drift, scope creep, missing acceptance criteria, over-engineering, and silent re-interpretation. Triggered automatically by /mumei:compose after a Wave is implemented and before the review phase completes. Does NOT review code quality…
issue-validator
Re-validates a single finding produced by another reviewer with fresh context. Returns valid / invalid / unsure. Triggered by /mumei:compose after the 3 reviewers complete (spec-compliance / security / adversarial) — invoked once per finding in parallel for severity=HIGH/CRITICAL findings. Filters false positives…
memory-curator
Independent evaluator that scores a candidate memory entry from a reviewer agent against a 7-axis rubric (generality, recurrence, longevity, coveragegap, actionability, density, confidence) and decides ADD / UPDATE / SKIP. Triggered by /mumei:compose Phase 5 Stage 6 and /mumei:peruse after each review-pipeline…
bash-script-reviewer
Reviews the quality of the mumei plugin's hooks/.sh and hooks/lib/.sh. Checks shellcheck convention compliance, the KISS principle, error handling, consistent mumei prefixing, ${CLAUDEPLUGINROOT} usage, jq null safety, BSD awk compatibility, and the stdin/stdout/stderr separation principle. Use on newly added or…
architect
Octopus 規格官——將釐清後的需求寫成 OpenSpec change（proposal＋spec delta＋tasks，含可測 Scenario）、產出方案決策卡給 TPM 拍板；必要時為手建 change 補產 tasks.md。.
builder
Octopus 實作官——從 Locked change 與 tasks 實作 code＋測試，每完成一條 task 出一則 task 回報。純執行層：只做被指派的、回報做過的；一律在 feature branch 工作，絕不碰主幹。.