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 skills add cboone/agent-harness-plugins --skill scaffold-rust-cligit clone --depth 1 https://github.com/cboone/agent-harness-pluginsWrote 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/skills/cboone/agent-harness-plugins/scaffold-rust-cli)<a href="https://agentmods.dev/skills/cboone/agent-harness-plugins/scaffold-rust-cli"><img src="https://agentmods.dev/badge/skills/cboone/agent-harness-plugins/scaffold-rust-cli/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/skills/cboone/agent-harness-plugins/scaffold-rust-cli"><img src="https://agentmods.dev/badge/skills/cboone/agent-harness-plugins/scaffold-rust-cli.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.00114 | $0.02624 |
| Opus 5 | $0.00057 | $0.01312 |
| Sonnet 5 | $0.00023 | $0.00525 |
| Haiku 4.5 | $0.00011 | $0.00262 |
Grade A, and why
scaffold-rust-cli 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 5d 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 — 276 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Scaffold Rust CLI
Generate the full boilerplate for a new Rust CLI project.
Workflow
1. Gather Project Information
If the user provided a project name in their request, use it as the project name and skip asking for it. Still ask for the remaining parameters unless already provided in the user's initial request.
Ask the user for these parameters:
- Project name -- kebab-case, used as the crate name, binary name, and directory name (e.g.,
my-tool) - Short description -- one sentence, used in
Cargo.tomland README - Include clap? -- whether to add clap for CLI argument parsing (adds
clapdependency withderivefeature and generates a skeleton with argument structs) - macOS-only project? -- whether this project targets only macOS (affects CI runner selection and release workflow targets). Default: no (cross-platform).
If the user already provided some or all of these in their initial request, do not re-ask. Derive what you can from context.
2. Detect User Identity
Detect the user's GitHub username and full name for use in templates:
# GitHub username (for repository URLs, Homebrew tap)
gh api user -q .login
# Full name (for LICENSE copyright, Cargo.toml authors)
git config user.name
If either command fails or produces no output, ask the user to provide the value. Use the GitHub username wherever templates reference GITHUB-USERNAME and the full name wherever they reference COPYRIGHT-HOLDER.
3. Verify the Target Directory
The project should be scaffolded in a directory named after the project. If the current directory is already named after the project and is empty (or nearly empty), use it. Otherwise, create a subdirectory.
If the directory already contains Rust files (Cargo.toml, src/), warn the user before proceeding.
4. Initialize Git
Skip if already inside a git repository.
git init
5. Generate Cargo.toml
Read ./references/cargo-toml.md for the Cargo.toml template and create Cargo.toml from it.
What ships with it
16 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- references/cargo-toml.md 1007 B
- references/ci-workflow-macos-only.md 1.5 KB
- references/ci-workflow.md 1.5 KB
- references/cliff.md 1.8 KB
- references/deny.md 1.1 KB
- references/gitignore.md 970 B
- references/license.md 1.4 KB
- references/main-rs-with-clap.md 955 B
- references/main-rs.md 284 B
- references/makefile.md 2.4 KB
- references/readme.md 986 B
- references/release-workflow-macos-only.md 1.2 KB
- references/release-workflow.md 1.6 KB
- references/rust-toolchain.md 551 B
- references/rustfmt.md 651 B
- references/typos.md 751 B
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.
- 5d ago First seen · 276 lines · 114 tokens per session scan A ccaf6dd48e48
scaffold-rust-cli is a skill published in the GitHub repository cboone/agent-harness-plugins (2 stars, last pushed today), licensed MIT. It adds 114 tokens to every session and 2,624 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-09-03.
Other skills, from other repositories
rust-crate-ci
Load before editing any Rust crate in this repo (currently runners/swarm-sandbox-runner). Covers the mandatory local validation gate, common rustfmt/clippy pitfalls, and Windows-specific Rust correctness patterns that CI enforces but are hard to catch locally without a Windows toolchain.
rust-tooling-cicd
Use when structuring a Cargo workspace or building a Rust CI pipeline — fmt, clippy, cargo-deny/audit, nextest, coverage, MSRV. Not for writing the tests themselves (rust-testing-quality).
cargo-workflows
Use when managing Cargo workspaces, feature flags, build scripts, CI caching, dependency auditing, or Cargo.lock with Rust.
cargo-workflows
Cargo workflow skill for Rust projects. Use when managing workspaces, feature flags, build scripts, cargo cache, incremental builds, dependency auditing, or CI configuration with Cargo. Activates on queries about cargo workspaces, Cargo.toml features, build.rs, cargo nextest, cargo deny, cargo check vs build, or…
rust-ci-setup
Set up a CI/CD pipeline for Rust projects. Use when: creating CI for Rust, adding Clippy/fmt/test/audit to CI. Do not use: for local development setup, non-CI automation.
scaffold-rust
Scaffold a complete Rust project with CI/CD, release pipeline, and sr.yaml. Uses cargo as the native build system. Loads on top of scaffold-project (run that first for cross-language standard files). Use when creating a new Rust CLI, library, or workspace, or when the user mentions "new Rust project", "cargo init", or…