A project-scanning command that proposes a proc-compose.yml file, a configuration describing the processes a project should run.

Use it to inspect Node, Go, or Python projects and preview, verify, or explicitly write a process configuration.

It saves the initial work of finding project entry points, development servers, runners, missing tools, and possible port or readiness problems.

bootstrap — Command for Claude Code by anivaryam/anivaryam-plugins

Install

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.

Clone the repo

git clone --depth 1 https://github.com/anivaryam/anivaryam-plugins

Made for: Claude Code.

Or install proc-compose, the plugin that ships this one along with the rest of its 1 skill, 3 commands, 1 agent.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/anivaryam/anivaryam-plugins/bootstrap/github.svg)](https://agentmods.dev/commands/anivaryam/anivaryam-plugins/bootstrap)

Your own site

<a href="https://agentmods.dev/commands/anivaryam/anivaryam-plugins/bootstrap"><img src="https://agentmods.dev/badge/commands/anivaryam/anivaryam-plugins/bootstrap/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/commands/anivaryam/anivaryam-plugins/bootstrap"><img src="https://agentmods.dev/badge/commands/anivaryam/anivaryam-plugins/bootstrap.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 16 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 217 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00016	$0.00217
Opus 5.5	$0.00006	$0.00087
Sonnet 5.5	$0.00003	$0.00043
Haiku 4.5	$0.00002	$0.00022

Measured 2mo ago against content hash 3eb52770942f, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

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 2mo 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.

plugins/proc-compose/commands/bootstrap.md · 16 lines

What it actually says

Run proc-compose bootstrap $ARGUMENTS in the current directory.

Default behaviour (no args) is read-only — proc-compose scans Node/Go/Python project layouts, detects runners, dev servers, and main entrypoints, then prints the proposed YAML. Nothing is written.

When the user asks for the file to be created, append --write. Refuse to add --force unless they have explicitly asked to overwrite an existing config — bootstrap will not clobber an existing proc-compose.yml/proc-compose.yaml without it.

Use --verify to round-trip the generated config through proc-compose's parser without writing.

After running, summarise the detected processes, any flagged gaps (missing binaries, port conflicts, readiness gaps, restart loops), and the recommended next step (up, validate, edit a specific field, etc.).

Changes

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.

2mo ago First seen · 16 lines · 16 tokens per session scan A 3eb52770942f

Subscribe to this mod's changes

bootstrap is a command published in the GitHub repository anivaryam/anivaryam-plugins (2 stars, last pushed 5mo ago), licensed MIT. It adds 16 tokens to every session and 217 once invoked, about $0.0001 per session on Opus 5.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.

DevOps and cloud

bootstrap next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
bootstrapanivaryam/anivaryam-plugins	Command	2	5mo ago	MIT	A	16	Claude Code
checklistgithub/spec-kit	Command	148k	today	MIT	A	13	Claude Code
clarifygithub/spec-kit	Command	148k	today	MIT	A	27	Claude Code
specifygithub/spec-kit	Command	148k	today	MIT	A	13	Claude Code
analyzegithub/spec-kit	Command	148k	today	MIT	A	26	Claude Code
convergegithub/spec-kit	Command	148k	today	MIT	A	35	Claude Code
implementgithub/spec-kit	Command	148k	today	MIT	A	14	Claude Code