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/landinggit clone --depth 1 https://github.com/paiml/rust-mcp-sdkWrote 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/commands/paiml/rust-mcp-sdk/landing)<a href="https://agentmods.dev/commands/paiml/rust-mcp-sdk/landing"><img src="https://agentmods.dev/badge/commands/paiml/rust-mcp-sdk/landing.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.00000 | $0.00656 |
| Opus 5 | $0.00000 | $0.00328 |
| Sonnet 5 | $0.00000 | $0.00131 |
| Haiku 4.5 | $0.00000 | $0.00066 |
Grade A, and why
landing 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 — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
cargo pmcp landing
Manage landing pages for MCP servers.
Usage
cargo pmcp landing <SUBCOMMAND>
Description
Create, develop, and deploy landing pages that showcase your MCP server. Landing pages help users discover and install MCP servers.
Subcommands
| Subcommand | Description |
|---|---|
init |
Initialize a new landing page |
dev |
Run the landing page locally for development |
build |
Build the landing page for production |
deploy |
Deploy the landing page to a target |
landing init
Initialize a new landing page for your MCP server.
cargo pmcp landing init [OPTIONS]
Options
| Option | Default | Description |
|---|---|---|
--template <TEMPLATE> |
nextjs |
Template to use |
--output <DIR> |
./landing |
Output directory for landing page |
--server-name <NAME> |
auto-detected | MCP server name (reads from pmcp.toml if not provided) |
Example
cargo pmcp landing init
cargo pmcp landing init --template nextjs --output ./my-landing
landing dev
Run the landing page locally for development.
cargo pmcp landing dev [OPTIONS]
Options
| Option | Default | Description |
|---|---|---|
--dir <DIR> |
./landing |
Landing page directory |
--port <PORT> |
3001 |
Port to run on |
--watch |
- | Watch for changes in pmcp-landing.toml |
Example
cargo pmcp landing dev --watch
cargo pmcp landing dev --port 4000
landing build
Build the landing page for production.
Note: This subcommand is not yet implemented. Use
cd ./landing && npm run buildas a workaround.
cargo pmcp landing build [OPTIONS]
Options
| Option | Default | Description |
|---|---|---|
--dir <DIR> |
./landing |
Landing page directory |
--output <DIR> |
./landing/.next |
Build output directory |
landing deploy
Deploy the landing page to a target.
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 · 122 lines · 0 tokens per session scan A 1f8c58eb8c60
landing is a command published in the GitHub repository paiml/rust-mcp-sdk (53 stars, last pushed 4d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 656 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.
cargo-metadata
Command "cargo-metadata" from olorehq/olore, covering cargo-metadata(1), name, synopsis, description and output format.
new-op
Guide for adding a new variant to the Op enum (e.g. Op::Tag, Op::Link). Covers every place that needs to change.
cargo-bench
Command "cargo-bench" from olorehq/olore, covering cargo-bench(1), name, synopsis, description and working directory of benchmarks.
cargo-build
Command "cargo-build" from olorehq/olore, covering cargo-build(1), name, synopsis, description and options.