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 claude-dev-suite/claude-dev-suite --skill rocketgit clone --depth 1 https://github.com/claude-dev-suite/claude-dev-suiteWrote 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/claude-dev-suite/claude-dev-suite/rocket)<a href="https://agentmods.dev/skills/claude-dev-suite/claude-dev-suite/rocket"><img src="https://agentmods.dev/badge/skills/claude-dev-suite/claude-dev-suite/rocket.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.1 | $0.00119 | $0.01261 |
| Opus 5 | $0.00060 | $0.00630 |
| Sonnet 5 | $0.00024 | $0.00252 |
| Haiku 4.5 | $0.00012 | $0.00126 |
Grade A, and why
rocket 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 — 180 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Rocket Core Knowledge
Full Reference: See advanced.md for custom guards (authentication, API key), fairings (CORS, timing), database state, error catchers, and testing patterns.
Deep Knowledge: Use
mcp__documentation__fetch_docswith technology:rocketfor comprehensive documentation.
Basic Setup
# Cargo.toml
[dependencies]
rocket = { version = "0.5", features = ["json"] }
serde = { version = "1", features = ["derive"] }
serde_json = "1"
tokio = { version = "1", features = ["full"] }
#[macro_use] extern crate rocket;
#[get("/")]
fn index() -> &'static str {
"Hello, World!"
}
#[launch]
fn rocket() -> _ {
rocket::build().mount("/", routes![index])
}
Routing
#[get("/users/<id>")]
fn get_user(id: u32) -> String {
format!("User {}", id)
}
#[post("/users", data = "<user>")]
fn create_user(user: Json<CreateUser>) -> Json<User> {
Json(User::from(user.into_inner()))
}
#[get("/files/<path..>")]
fn get_file(path: PathBuf) -> Option<NamedFile> {
NamedFile::open(Path::new("static/").join(path)).ok()
}
// Query parameters
#[derive(FromForm)]
struct Pagination { page: Option<u32>, per_page: Option<u32> }
#[get("/users?<pagination..>")]
fn list_users(pagination: Pagination) -> Json<Vec<User>> {
let page = pagination.page.unwrap_or(1);
Json(fetch_users(page, pagination.per_page.unwrap_or(20)))
}
// Mounting
#[launch]
fn rocket() -> _ {
rocket::build()
.mount("/", routes![index])
.mount("/api/v1", routes![list_users, get_user, create_user])
}
Request Guards
// JSON body
#[post("/users", data = "<user>")]
fn create_user(user: Json<CreateUser>) -> Json<User> {
Json(User::from(user.into_inner()))
}
// Form data
#[post("/login", data = "<login>")]
fn login(login: Form<LoginForm>) -> String {
format!("Welcome, {}", login.username)
}
// Cookies
#[get("/session")]
fn session(cookies: &CookieJar<'_>) -> Option<String> {
cookies.get("session_id").map(|c| c.value().to_string())
}
What ships with it
1 file 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.
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 · 180 lines · 119 tokens per session scan A 3632a042f594
rocket is a skill published in the GitHub repository claude-dev-suite/claude-dev-suite (30 stars, last pushed yesterday), licensed MIT. It adds 119 tokens to every session and 1,261 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
mcp-builder
Guide the creation of high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when the user wants to build an MCP server to integrate an external API or service, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).
rust-programming-expert
Expert-level skill for Rust programming (Rust 2024 / v1.85+). Covers memory safety, async, Axum/SQLx, CLI, and optimization in English and Indonesian.
rust-ops
Rust development patterns, ownership, async, error handling, and ecosystem. Use for: rust, cargo, ownership, borrow checker, lifetime, tokio, serde, trait, Result, Option, async rust, crate, derive, impl, enum, pattern matching, Arc, Mutex, Send, Sync, thiserror, anyhow, clap, axum, sqlx, reqwest, rayon, tracing.
go-microservice-architecture
Design, review, or explain a new product's Go backend/microservice architecture using Kitex or similar RPC, Hertz or similar HTTP gateway, protobuf IDL, MySQL/GORM storage, Redis cache/locks/limits, service discovery, dynamic config, message queues, observability, DI, and code generation. Also owns multi-tenant…
go-microservice-dev
Use when implementing, modifying, scaffolding, generating, or testing a new product's Go microservice, backend feature, or standalone Go CLI/tooling binary using protobuf IDL, Kitex or similar RPC, Hertz or similar HTTP, Wire/DI, MySQL/GORM-style DAL, Redis, MQ, dynamic config, code generation, and focused tests. For…
python-service-architecture
A guide for designing Python backend services and deciding how their parts should be separated. It covers FastAPI projects, Celery workers, microservices, message queues, data ownership, APIs, reliability and scaling.