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/sigistry/marketplace/dev-env-bootstrapgit clone --depth 1 https://github.com/sigistry/marketplaceWrote 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/sigistry/marketplace/dev-env-bootstrap)<a href="https://agentmods.dev/commands/sigistry/marketplace/dev-env-bootstrap"><img src="https://agentmods.dev/badge/commands/sigistry/marketplace/dev-env-bootstrap.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.00013 | $0.00851 |
| Opus 5 | $0.00006 | $0.00426 |
| Sonnet 5 | $0.00003 | $0.00170 |
| Haiku 4.5 | $0.00001 | $0.00085 |
Grade A, and why
dev-env-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 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 — 46 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Get this repository running on your machine, detect what it needs, run the setup, fix what breaks, and write down only the steps that actually worked. Use this on day one of a new codebase, or when a stale README leaves you with a red build. $ARGUMENTS may be a subdirectory to bootstrap (a specific service/package in a monorepo); default to the repo root.
Process
Step 1: Discover the declared requirements
Read, do not guess. Scan for the signals that tell you the runtime, tooling, and services this repo expects (see the setup-diagnosis skill's setup-signals.md for the full map):
| Signal | What it declares |
|---|---|
package.json (engines, packageManager), .nvmrc |
Node version + package manager |
.tool-versions, mise.toml, asdf |
Multi-runtime pins (Node/Python/Ruby/Go/…) |
.python-version, pyproject.toml, requirements*.txt, Pipfile, poetry.lock |
Python version + resolver |
.ruby-version, Gemfile, go.mod, pom.xml, build.gradle, Cargo.toml |
Runtime + dependency manifest |
Dockerfile, docker-compose.yml, .devcontainer/ |
Containerized runtime + backing services (DB, cache, queue) |
.env.example, .env.sample, config/*.example |
Required environment variables |
Makefile, justfile, Taskfile.yml, scripts/ |
Project-authored setup/bootstrap targets |
README, CONTRIBUTING, docs/ |
The human instructions (verify, they drift) |
Step 2: Reconcile and plan
- Prefer a project-authored setup target (
make setup,just bootstrap,./scripts/setup) over hand-assembling steps, repos usually encode the real path there. - If manifests disagree with the README (e.g.
.nvmrcsays 18 but the README says 16), trust the machine-readable pin and note the discrepancy. - List the backing services
docker-compose.ymlprovides and whether they must be up before install/migrate/seed.
Step 3: Execute and diagnose
Launch the env-doctor agent to run the setup end-to-end. It installs the correct runtime versions, runs the install/build/migrate/seed steps, and diagnoses failures (wrong runtime version, missing system libraries, missing env vars, native build errors, port conflicts, OS-specific breakage), fixing what it can safely fix. It never invents credentials or secret values, it flags them as required and leaves them blank.
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 · 46 lines · 13 tokens per session scan A 0febdd86fa8b
dev-env-bootstrap is a command published in the GitHub repository sigistry/marketplace (3 stars, last pushed today), licensed MIT. It adds 13 tokens to every session and 851 once invoked, about $0.0001 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 commands, from other repositories
battlecard
Create a sales-ready competitive battlecard — positioning, feature comparison, objection handling, and win strategies.
release
Generate changelog, bump version, and create git tag.
bootstrap
Scaffold test, lint, and CI infrastructure for projects that lack it.
typescript-dev
Start TypeScript development workflow with architecture, implementation, review, and testing phases.
validate
Mechanically validate the sonu plugin repo before a PR — manifest sync, YAML frontmatter, shell-fence syntax, named-source and AI-attribution scans, cross-reference integrity, skill reachability. Only meaningful inside the claude-plugins repo; in any other repo, say so and stop.
ideal-customer-profile
Build, enrich, or audit your ICP — trigger events, buyer map, JTBD, disqualifiers.