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/tpavanipradeep/everything-claude-code/rust-buildgit clone --depth 1 https://github.com/tpavanipradeep/everything-claude-codeWhat 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.00008 | $0.00456 |
| Opus 5 | $0.00004 | $0.00228 |
| Sonnet 5 | $0.00002 | $0.00091 |
| Haiku 4.5 | $0.00001 | $0.00046 |
Grade A, and why
rust-build 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 2d 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 rust-build — 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
Rust Build Command
Fix Rust build, clippy, and dependency errors: $ARGUMENTS
Your Task
- Run cargo check:
cargo check 2>&1 - Run cargo clippy:
cargo clippy -- -D warnings 2>&1 - Fix errors one at a time
- Verify fixes don't introduce new errors
Common Rust Errors
Borrow Checker
cannot borrow `x` as mutable because it is also borrowed as immutable
Fix: Restructure to end immutable borrow first; clone only if justified
Type Mismatch
mismatched types: expected `T`, found `U`
Fix: Add .into(), as, or explicit type conversion
Missing Import
unresolved import `crate::module`
Fix: Fix the use path or declare the module (add Cargo.toml deps only for external crates)
Lifetime Errors
does not live long enough
Fix: Use owned type or add lifetime annotation
Trait Not Implemented
the trait `X` is not implemented for `Y`
Fix: Add #[derive(Trait)] or implement manually
Fix Order
- Build errors - Code must compile
- Clippy warnings - Fix suspicious constructs
- Formatting -
cargo fmtcompliance
Build Commands
cargo check 2>&1
cargo clippy -- -D warnings 2>&1
cargo fmt --check 2>&1
cargo tree --duplicates
cargo test
Verification
After fixes:
cargo check # Should succeed
cargo clippy -- -D warnings # No warnings allowed
cargo fmt --check # Formatting should pass
cargo test # Tests should pass
IMPORTANT: Fix errors only. No refactoring, no improvements. Get the build green with minimal changes.
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.
- 2d ago First seen · 79 lines · 8 tokens per session scan A d658182c79fb
rust-build is a command published in the GitHub repository tpavanipradeep/everything-claude-code (103 stars, last pushed 5mo ago), licensed MIT. It adds 8 tokens to every session and 456 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to rust-build, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.