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 skills/onsager-ai/dev-skills/rust-node-bootstrapnpx skills add onsager-ai/dev-skills --skill rust-node-bootstrapgit clone --depth 1 https://github.com/onsager-ai/dev-skillsWhat 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.00104 | $0.01144 |
| Opus 5 | $0.00052 | $0.00572 |
| Sonnet 5 | $0.00021 | $0.00229 |
| Haiku 4.5 | $0.00010 | $0.00114 |
Grade A, and why
rust-node-bootstrap 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.
How it starts
The opening of the file, as written. The whole thing — 119 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Rust+Node.js Bootstrap
Scaffold a Rust+Node.js hybrid project with all infrastructure in one pass.
When to Use This Skill
Activate when any of the following are true:
- User says "bootstrap", "scaffold", "new project", "set up from scratch"
- Repo has
Cargo.tomlorpackage.jsonbut is missing the other - Missing
.github/workflows/,scripts/, orpublish.config.ts - Incrementally adding forge infrastructure to an existing project
Decision Tree
Starting from scratch?
YES → Full scaffold (all steps in order below)
NO → Incremental setup ↓
Has package.json? → NO: Create root package.json + pnpm-workspace.yaml
Has Cargo.toml? → NO: Create Cargo workspace
Has .github/workflows/? → NO: Generate from rust-node-ci skill templates
Has scripts/? → NO: Generate from rust-npm-publish skill templates
Has publish.config.ts? → NO: Create from rust-npm-publish skill examples
Has specs/? → NO: Initialize LeanSpec
Gather Project Info
| Field | Example | Required |
|---|---|---|
| Project name | my-tool |
Yes |
| npm scope | @myorg |
Yes |
| Rust binary name(s) | my-cli |
Yes |
| Cargo package name(s) | my-cli-rs |
Yes |
| Main npm packages | packages/cli |
Yes |
| Repository URL | github.com/myorg/my-tool |
Yes |
| Platforms | darwin-x64, darwin-arm64, linux-x64, windows-x64 |
No (default: all 4) |
Scaffold Structure
See references/project-structure.md for the full annotated tree.
my-tool/
├── .github/workflows/ ← CI + publish workflows
├── .lean-spec/config.json ← LeanSpec configuration
├── specs/ ← Spec-driven development
├── packages/cli/ ← Main npm package (thin JS wrapper)
│ ├── package.json ← bin + optionalDependencies
│ └── bin.js ← Resolves platform binary, spawns it
├── rust/ ← Rust workspace
├── scripts/ ← Publish & version scripts
├── publish.config.ts ← Publish pipeline configuration
├── package.json ← Root (version source of truth)
├── pnpm-workspace.yaml ← pnpm workspace definition
└── Cargo.toml ← Rust workspace manifest
What ships with it
11 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/checklist.md 2.4 KB
- references/project-structure.md 5.0 KB
- templates/.gitignore 322 B
- templates/.lean-spec/config.json 74 B
- templates/AGENTS.md 1.5 KB
- templates/bootstrap/Cargo.toml 206 B
- templates/bootstrap/package.json 413 B
- templates/bootstrap/pnpm-workspace.yaml 102 B
- templates/bootstrap/publish.config.ts 889 B runs code
- templates/bootstrap/turbo.json 272 B
- templates/specs/README.md 165 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.
- 2d ago First seen · 119 lines · 104 tokens per session scan A e936927f23e8
rust-node-bootstrap is a skill published in the GitHub repository onsager-ai/dev-skills (5 stars, last pushed 20d ago), licensed MIT. It adds 104 tokens to every session and 1,144 once invoked, about $0.0005 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-08-31.
Other skills, from other repositories
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
dsh-web-pre-push-checks
Use before pushing, opening or updating a pull request, or claiming dsh-web checks pass. Selects the required repository gates and diff-specific generation, build, and GUI evidence.
babysit
Same-session monitoring loop for PRs, CI runs, tickets, and deployments using the monitorstart / monitorupdate / autonudgestop MCP tools. The loop re-injects your check instructions into THIS session on an idle interval — same context, same tools — and works from dashboard chat, Slack threads, and Discord DMs. Use…
azsdk-common-pipeline-analysis
Analyze Azure SDK CI/CD pipeline failures into a structured diagnosis, and define the required output format. Load this skill before calling azsdkanalyzepipeline, which returns raw failure data that this skill interprets and formats. USE FOR: "pipeline failed", "build failure", "CI check failing", "tests failing in…
teamcity-cli
Use when working with TeamCity CI/CD or when user provides a TeamCity build URL. Use teamcity CLI for builds, logs, jobs, queues, agents, and pipelines.
harness-setup
HAR: Project init, tool setup, agent config, memory setup, skill mirror sync. Trigger: setup, init, new project, CI/Codex setup, harness-mem, mirror. Do NOT load for: implementation, review, release, planning.