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/paiml/rust-mcp-sdk/newgit clone --depth 1 https://github.com/paiml/rust-mcp-sdkWhat 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.00000 | $0.00347 |
| Opus 5 | $0.00000 | $0.00173 |
| Sonnet 5 | $0.00000 | $0.00069 |
| Haiku 4.5 | $0.00000 | $0.00035 |
Grade A, and why
new 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.
What it actually says
cargo pmcp new
Create a new MCP workspace.
Usage
cargo pmcp new <NAME> [OPTIONS]
Description
Creates a workspace with server-common template and scaffolding for building multiple MCP servers. The workspace pattern allows sharing common code (like HTTP bootstrap) across all servers.
The generated workspace includes:
Cargo.tomlworkspace manifestcrates/directory for server cratesscenarios/directory for test scenarioslambda/directory for Lambda deployment wrappersserver-commonshared library crate
Arguments
| Argument | Required | Description |
|---|---|---|
NAME |
Yes | Name of the workspace to create |
Options
| Option | Description |
|---|---|
--path <DIR> |
Directory to create workspace in (defaults to current directory) |
Examples
Create a workspace in the current directory:
cargo pmcp new my-mcp-workspace
cd my-mcp-workspace
Create in a specific directory:
cargo pmcp new my-workspace --path ~/projects
What's Generated
my-mcp-workspace/
Cargo.toml # Workspace manifest
crates/ # Server crates go here
scenarios/ # Test scenario YAML files
lambda/ # Lambda deployment wrappers
server-common/ # Shared HTTP bootstrap library
Related Commands
cargo pmcp add- Add a server to the workspacecargo pmcp dev- Start a development server
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 · 62 lines · 0 tokens per session scan A dc149df67411
new is a command published in the GitHub repository paiml/rust-mcp-sdk (53 stars, last pushed 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 347 tokens. 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-30.
Other commands, from other repositories
wrap-snarkvm
Automates wrapping a SnarkVM type in wasm-bindgen bindings for the Provable SDK.
update-linear-schema
Update the Linear GraphQL schema and fix any resulting breakage.
rust-features
Get Rust version changelog and new features.
cargo-metadata
Command "cargo-metadata" from olorehq/olore, covering cargo-metadata(1), name, synopsis, description and output format.
rust-review
Rust code review for ownership, safety, and idiomatic patterns.
cargo-bench
Command "cargo-bench" from olorehq/olore, covering cargo-bench(1), name, synopsis, description and working directory of benchmarks.