serve

serve is a skill for Claude Code from brain-bootstrap/claude-code-brain-bootstrap. It costs 34 tokens per session (340 once invoked), scanned A, original, MIT.

A workflow for starting one or more project services locally, such as a frontend or backend, using the commands defined by the project.

In plain words
What is it for?
Use it to start all services, a frontend, a backend, or one named service for local development.
Why use it?
It avoids guessing how services should be started and keeps development servers running without blocking the session.

Skill for Claude Code

Written for Claude Code: $ARGUMENTS substitution.

Good fit Use it to start all services, a frontend, a backend, or one named service for local development.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/brain-bootstrap/claude-code-brain-bootstrap/serve
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.

Any agent
npx skills add brain-bootstrap/claude-code-brain-bootstrap --skill serve
Clone the repo
git clone --depth 1 https://github.com/brain-bootstrap/claude-code-brain-bootstrap

Made for: Claude Code.

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.

agentmods badge for serve

README.md
[![agentmods](https://agentmods.dev/badge/skills/brain-bootstrap/claude-code-brain-bootstrap/serve/github.svg)](https://agentmods.dev/skills/brain-bootstrap/claude-code-brain-bootstrap/serve)
Your own site
<a href="https://agentmods.dev/skills/brain-bootstrap/claude-code-brain-bootstrap/serve"><img src="https://agentmods.dev/badge/skills/brain-bootstrap/claude-code-brain-bootstrap/serve/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.

agentmods 80×15 button for serve

Your own site · 80×15
<a href="https://agentmods.dev/skills/brain-bootstrap/claude-code-brain-bootstrap/serve"><img src="https://agentmods.dev/badge/skills/brain-bootstrap/claude-code-brain-bootstrap/serve.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 34 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 340 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00034 $0.00340
Opus 5.5 $0.00014 $0.00136
Sonnet 5.5 $0.00007 $0.00068
Haiku 4.5 $0.00003 $0.00034

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

Security

Grade A, and why

serve 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 1mo 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.

.claude/skills/serve/SKILL.md · 48 lines

What it actually says

Serve Skill

Start service(s) locally for development.

Usage

/serve                  # Start default service (or show options)
/serve all              # Start all services
/serve frontend         # Start frontend only
/serve backend          # Start backend only
/serve <service-name>   # Start a specific named service

Instructions

First: Read claude/build.md for local development setup and service definitions.

Determine scope from $ARGUMENTS:

Argument Action
<service-name> {{SERVE_CMD_SINGLE}} <service-name>
all {{SERVE_CMD_ALL}}
frontend {{SERVE_CMD_FRONTEND}}
backend {{SERVE_CMD_BACKEND}}
(empty) Show available services from claude/build.md

Rules:

  • Run services in background (async) so the session stays responsive
  • After starting, show the expected URLs (from claude/build.md)
  • If a port is already in use: report the conflict and suggest lsof -i :<port> to identify the process
  • NEVER run interactive servers in foreground — use background execution

Example (if claude/build.md has commands):

# Backend
pnpm --filter api dev &

# Frontend
pnpm --filter web dev &
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.

  1. 1mo ago First seen · 48 lines · 34 tokens per session scan A 49f115db273c

Subscribe to this mod's changes

serve is a skill published in the GitHub repository brain-bootstrap/claude-code-brain-bootstrap (11 stars, last pushed 5mo ago), licensed MIT. It adds 34 tokens to every session and 340 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-09-03.

Related

Other skills, from other repositories

implement

TRIGGER when: user asks to implement, fix, build, or work on something — whether from a docs/feat/wip plan OR a standalone task (bug fix, GitHub issue, one-off change). Examples: "work on task 1", "fix this bug", "implement feature X from the issue". Provides structured execution with profile detection, dependency…

serpro69/claude-toolbox · 81 tokens

review-spec

Use after implementing tasks or mid-feature to verify code matches design docs and ensure they are in sync. Detects spec deviations, missing implementations, doc inconsistencies, and outdated docs in design and implementation documentation.

serpro69/claude-toolbox · 44 tokens

chain-of-verification

Apply Chain-of-Verification (CoVe) prompting to improve response accuracy through self-verification. Use when complex questions require fact-checking, technical accuracy, or multi-step reasoning.

serpro69/claude-toolbox · 41 tokens

review-design

Review design, implementation, and task documents produced by design. Evaluates document quality, internal consistency, and technical soundness. Use after design completes and before starting implement.

serpro69/claude-toolbox · 37 tokens

review-architecture

Review a written architecture artifact — an ADR (docs/adr/), a broader architecture doc, the architecture section of a design doc, or a domain-reference kit (glossary + traps pages, reviewed as one composite artifact) — against the system it claims to describe. Verifies the EXISTENCE and TOPOLOGY of declared…

serpro69/claude-toolbox · 183 tokens

model

Produce or update a domain-reference kit — the durable glossary + divergences/traps pages for a bounded context. Use for domain modelling, information architecture, building a domain glossary or domain model, mapping domain concepts to code (bindings), or surfacing the decidable questions stakeholders must close…

serpro69/claude-toolbox · 129 tokens