configure-project

configure-project is a skill for Claude Code, Codex from CaptainMe-AI/lead-dev-os. It costs 26 tokens per session (951 once invoked), scanned A, original, MIT.

A setup procedure for adding the lead-dev-os framework to a project. It creates shared agent context, a specifications folder, and project instructions in `CLAUDE.md`.

In plain words
What is it for?
Use it when starting lead-dev-os in a project to check existing setup, configure the technology stack, and create or preserve the required files.
Why use it?
It gives coding agents the project structure and instructions they need before feature work begins.

Skill for Claude CodeCodex

Installs and runs on its own, but its text points at files inside its plugin — anything it tells you to read at a ${CLAUDE_PLUGIN_ROOT} path is only there once the plugin is installed. Installing the plugin gets both.

Part of the lead-dev-os plugin — 9 skills shipped together

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.

agentmods
npx agentmods add skills/captainme-ai/lead-dev-os/configure-project
Any agent
npx skills add CaptainMe-AI/lead-dev-os --skill configure-project
Clone the repo
git clone --depth 1 https://github.com/CaptainMe-AI/lead-dev-os

Made for: Claude Code, Codex.

Or install lead-dev-os, the plugin that ships this one along with the rest of its 9 skills.

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 configure-project

README.md
[![agentmods](https://agentmods.dev/badge/skills/captainme-ai/lead-dev-os/configure-project.svg)](https://agentmods.dev/skills/captainme-ai/lead-dev-os/configure-project)
Your own site
<a href="https://agentmods.dev/skills/captainme-ai/lead-dev-os/configure-project"><img src="https://agentmods.dev/badge/skills/captainme-ai/lead-dev-os/configure-project.svg" alt="Measured on agentmods" height="20"></a>
Per session 26 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 951 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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.00026 $0.00951
Opus 5 $0.00013 $0.00476
Sonnet 5 $0.00005 $0.00190
Haiku 4.5 $0.00003 $0.00095

Measured 5d ago against content hash d8632207afd6, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-05, from the pricing page.

Security

Grade A, and why

configure-project 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 5d ago.

The scan reads SKILL.md. This mod also ships 1 executable file (scripts/setup.sh), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

lead-dev-os/skills/configure-project/SKILL.md · 111 lines

How it starts

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

Configure Project

Configure the lead-dev-os framework in the current project.

Instructions

You are a project setup assistant. Configure the lead-dev-os framework by running the bundled setup script, then configuring the project's CLAUDE.md.

Phase 1: Check Existing Setup

Check if any lead-dev-os artifacts already exist:

  • agents-context/ directory
  • lead-dev-os/specs/ directory
  • CLAUDE.md with ## lead-dev-os Framework section

If any exist, inform the user what was found and ask: "Some lead-dev-os artifacts already exist. Should I skip existing files (preserve your changes) or overwrite them with fresh defaults?" Use the AskUserQuestion tool when available — two options: "Skip existing (Recommended)" and "Overwrite with defaults" — falling back to a plain-text question otherwise.

Remember their choice — you will pass it to the setup script.

Phase 2: Ask About Technology Stack

Ask the user: "What technology stacks does your project use? Select all that apply:" Use the AskUserQuestion tool when available with multiSelect: true (one question per category below, or grouped sensibly); fall back to a plain-text list otherwise.

Present these categories:

  • Languages: Python, Ruby, TypeScript, JavaScript
  • Backend frameworks: FastAPI, Django, Rails, Express
  • Databases: PostgreSQL, MySQL, MongoDB, Redis
  • Frontend frameworks: React, Next.js, Vue
  • Infrastructure: Nginx, Gunicorn, Uvicorn, Docker

This determines which stack-specific standard directories to create. Global standards (coding style, conventions, error handling, commenting, validation) and testing standards are always included.

Phase 3: Run Setup Script

Resolve the plugin root path:

echo ${CLAUDE_PLUGIN_ROOT}

Determine the project name from the current directory name or ask the user.

Run the setup script with the collected arguments:

bash ${CLAUDE_PLUGIN_ROOT}/skills/configure-project/scripts/setup.sh \
  --project "<project-name>" \
  --stacks "<comma-separated-stacks>" \
  --plugin-root "${CLAUDE_PLUGIN_ROOT}" \
  [--overwrite]

Read the full file on GitHub · 111 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.

  1. 5d ago First seen · 111 lines · 26 tokens per session scan A d8632207afd6

Subscribe to this mod's changes

configure-project is a skill published in the GitHub repository CaptainMe-AI/lead-dev-os (2 stars, last pushed 15d ago), licensed MIT. It adds 26 tokens to every session and 951 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.

Related

Other skills, from other repositories

evolution-auditor

Run a structured organizational design health check — operationalizing the governance learning loop and decision ledger by collecting operational evidence, measuring gate effectiveness, detecting genome drift, and producing an evolution audit with routed recommendations saved to $HOME/.ai-first-kit/. Maintains the…

synaptiai/synapti-marketplace · 236 tokens

nci-manipulation-analysis

Use when asked to analyze content for manipulation, propaganda, disinformation patterns, or when user provides a URL or text asking "is this manipulative?", "analyze this for bias", "check for propaganda", or similar requests. Detects emotional manipulation, suspicious timing, uniform messaging, tribal division, and…

synaptiai/synapti-marketplace · 75 tokens

ai-first-kit

Navigate organizational redesign for AI with a structured 13-skill toolkit that produces persistent artifacts in $HOME/.ai-first-kit/. Routes founders and leaders to the right specialist skill — coordination audit, organizational genome, specification writing, quality gates, governance, role design, political…

synaptiai/synapti-marketplace · 293 tokens

coordination-audit

Produce a structured organizational diagnostic that quantifies time spent on specification vs coordination vs execution, saved as a persistent audit artifact to $HOME/.ai-first-kit/. Conducts a guided 5-question interview, classifies every workflow structure by actual function, and identifies highest-ROI automation…

synaptiai/synapti-marketplace · 182 tokens

evidence-ledger

Record every material claim as a row in 00-control/evidence-ledger.md carrying a source-authority level and a claim state (verified, corroborated, reported, inferred, unknown, not applicable), and keep observed, interpreted, unknown, and recommended content in visibly separate blocks. Use when inventorying sources…

synaptiai/synapti-marketplace · 137 tokens

criterion-verification-map

Transform acceptance criteria into plan-time runnable verification commands (behavioral, API, UI, error, config, data, contract types) with expected evidence shapes, then execute at verify time and assemble evidence bundles with honest completeness subsections (untested paths, known limitations, adversarial cases…

synaptiai/synapti-marketplace · 105 tokens