A project setup workflow that detects a project's technology stack and creates configuration with default commands for testing, linting, formatting, and format checks.

It helps initialise projects that use Python, Rust, Go, Node.js, or standard Makefile conventions.

It removes the need to configure common development commands by hand when starting a project.

init — Skill for Claude Code by navapbc

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 navapbc/digital-service-orchestra --skill init

Clone the repo

git clone --depth 1 https://github.com/navapbc/digital-service-orchestra

Made for: Claude Code.

Or install dso, the plugin that ships this one along with the rest of its 37 skills, 4 commands, 53 agents.

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/skills/navapbc/digital-service-orchestra/init/github.svg)](https://agentmods.dev/skills/navapbc/digital-service-orchestra/init)

Your own site

<a href="https://agentmods.dev/skills/navapbc/digital-service-orchestra/init"><img src="https://agentmods.dev/badge/skills/navapbc/digital-service-orchestra/init/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/skills/navapbc/digital-service-orchestra/init"><img src="https://agentmods.dev/badge/skills/navapbc/digital-service-orchestra/init.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 9 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 911 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.00009	$0.00911
Opus 5	$0.00005	$0.00456
Sonnet 5	$0.00002	$0.00182
Haiku 4.5	$0.00001	$0.00091

Measured 6d ago against content hash 734ab3937187, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

init 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 6d 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/dso/skills/init/SKILL.md · 110 lines

How it starts

The opening of the file, as written. The whole thing — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Initialize Project with Digital Service Orchestra

Set up a new project to use Digital Service Orchestra by auto-detecting the stack and writing a .claude/dso-config.conf with sensible defaults.

Usage

/dso:init              # Initialize current directory
/dso:init [project-dir] # Initialize a specific directory

Steps

Step 1: Detect Stack

Run detect-stack.sh to identify the project type:

STACK=$(bash ".claude/scripts/dso detect-stack.sh" "${PROJECT_DIR:-.}")

The script inspects marker files and returns one of:

python-poetry — pyproject.toml found
rust-cargo — Cargo.toml found
golang — go.mod found
node-npm — package.json found
convention-based — Makefile with ≥2 standard targets
unknown — no recognized markers

Step 2: Map Stack to Default Commands

Use the detected stack to populate sensible command defaults:

Stack	`test`	`lint`	`format`	`format_check`
`python-poetry`	`make test`	`make lint`	`make format`	`make format-check`
`node-npm`	`npm test`	`npm run lint`	`npm run format`	—
`rust-cargo`	`cargo test`	`cargo clippy`	`cargo fmt`	`cargo fmt --check`
`golang`	`go test ./...`	`golangci-lint run`	`gofmt -l .`	—
`convention-based`	`make test`	`make lint`	`make format`	—

Additional defaults for python-poetry:

validate: .claude/scripts/dso validate.sh --ci

Step 3: Check for Existing Config

Before proposing, check if .claude/dso-config.conf already exists using read-config.sh:

EXISTING_STACK=$(bash ".claude/scripts/dso read-config.sh" stack "${PROJECT_DIR:-.}/.claude/dso-config.conf")

If the file exists, warn the user and ask for confirmation before overwriting.

Step 4: Show Proposed Config

Present the proposed .claude/dso-config.conf to the user before writing:

# .claude/dso-config.conf — generated by /dso:init
stack=<detected-stack>

commands.test=<default-test-command>
commands.lint=<default-lint-command>
commands.format=<default-format-command>
# commands.format_check=<default-format-check-command>  # if applicable
# commands.validate=<validate-command>                  # if applicable

Read the full file on GitHub · 110 lines

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.

6d ago First seen · 110 lines · 9 tokens per session scan A 734ab3937187

Subscribe to this mod's changes

init is a skill published in the GitHub repository navapbc/digital-service-orchestra (6 stars, last pushed today), licensed Apache-2.0. It adds 9 tokens to every session and 911 once invoked, about $0.0000 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.

Productivity Project management

things-mac

Manage Things 3 via the things CLI on macOS (add/update projects+todos via URL scheme; read/search/list from the local Things database). Use when a user asks Otto to add a task to Things, list inbox/today/upcoming, search tasks, or inspect projects/areas/tags.

elizaOS/eliza · 67 tokens

gsd-ns-manage

Route to the appropriate management skill based on the user's intent. gsd-config (settings + advanced + integrations + profile) and gsd-workspace (new + list + remove) are post-#2790 consolidated entries.

open-gsd/gsd-core · 16 tokens

slack-tools

Slack workspace management and automation specialist.

RightNow-AI/openfang · 10 tokens

triage-inbox

Triage academic email and calendar (Gmail / Google Calendar via the session's MCP) into a prioritized digest plus a referee-obligations tracker — classifying referee requests, R&R and editor correspondence, co-author threads, seminar and conference invites, and grant/admin deadlines, and proposing a human-gated action…

pedrohcgs/claude-code-my-workflow · 132 tokens

ceo-setup

One-time onboarding for the executive/manager commitment workflow — delegation-heavy, meeting prep, decision capture, morning and evening digests. Creates a commitments project and installs two dashboard widgets. After successful setup this skill is excluded from selection until the marker file is deleted.

suyoumo/ClawProBench · 60 tokens

service-desk

Runs the IT service desk — intake, triage, prioritization, escalation, knowledge, and the metrics that improve service rather than distort it. Use this to set up or fix a service desk, design ticket priority and escalation, reduce repeat contacts, structure a knowledge base, or work out why a desk hitting its targets…

cbrock84/headcount · 73 tokens