setup-project-config

setup-project-config is a skill for Claude Code from jamesyang124/agent-skills. It costs 123 tokens per session (3,318 once invoked), scanned C, original, MIT.

A one-time setup tool that creates a shared project configuration file. It scans the codebase and lists project-specific settings for installed agent connections, without storing credentials.

In plain words
What is it for?
Use it to create or update .agent-settings/project-config.md after starting a project, adding agent connections, or changing the project's development tools.
Why use it?
It removes the need to manually work out which project settings each agent connection needs. Secrets remain in the global environment file instead of the project config.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: reads .claude/ paths; mentions CLAUDE.md.

Good fit Use it to create or update .agent-settings/project-config.md after starting a project, adding agent connections, or changing the project's development tools.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/jamesyang124/agent-skills/setup-project-config
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 jamesyang124/agent-skills --skill setup-project-config
Clone the repo
git clone --depth 1 https://github.com/jamesyang124/agent-skills

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 setup-project-config

README.md
[![agentmods](https://agentmods.dev/badge/skills/jamesyang124/agent-skills/setup-project-config.svg)](https://agentmods.dev/skills/jamesyang124/agent-skills/setup-project-config)
Your own site
<a href="https://agentmods.dev/skills/jamesyang124/agent-skills/setup-project-config"><img src="https://agentmods.dev/badge/skills/jamesyang124/agent-skills/setup-project-config.svg" alt="Measured on agentmods" height="20"></a>
Per session 123 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,318 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 2 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.00123 $0.03318
Opus 5 $0.00062 $0.01659
Sonnet 5 $0.00025 $0.00664
Haiku 4.5 $0.00012 $0.00332

Measured 7d ago against content hash 8fabb3a5e62a, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade C, and why

setup-project-config scanned grade C with 2 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 7d 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.

Reads agent configuration directoriesmediumAgent snooping

.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.

cat .mcp.json .claude/mcp.json 2>/dev/null

Reads MCP configurationmediumAgent snooping

mcp.json carries server URLs and auth tokens; reading it lets a mod discover and abuse other integrations.

cat .mcp.json .claude/mcp.json 2>/dev/null
.agent-settings/skills/tools/setup-project-config/SKILL.md · 303 lines

How it starts

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

Setup Project Config

Install this skill globally

Install once — available in all projects.

# Claude
mkdir -p ~/.claude/skills/setup-project-config
cp <agent-settings-repo>/.agent-settings/skills/tools/setup-project-config/SKILL.md \
   ~/.claude/skills/setup-project-config/SKILL.md
# Add to ~/.claude/CLAUDE.md: - **setup-project-config** (`~/.claude/skills/setup-project-config/SKILL.md`)

# Copilot
mkdir -p ~/.copilot/skills/setup-project-config
cp <agent-settings-repo>/.agent-settings/skills/tools/setup-project-config/SKILL.md \
   ~/.copilot/skills/setup-project-config/SKILL.md

Dependencies

No external skills or MCPs required. Only needs read access to the project codebase.


Generates .agent-settings/project-config.md — the shared per-project config file. Consumers and the sections they read are listed authoritatively in references/config-output-format.md (currently sync-api-spec, ado-open-pr, tech-plan-to-wiki, sdd-qa-to-ticket, install-external-skills).

Detect mode automatically based on whether .agent-settings/project-config.md already exists:

  • No file → Mode A: Initial Setup
  • File exists, legacy schema (has a top-level ## Confluence or ## Jira section) → Mode M: Migrate first, then Mode B
  • File exists, current schema (## MCP: <name> sections) → Mode B: Re-calibration

Always run the legacy check on any existing file before Mode B. Older configs (pre per-MCP schema) used flat ## Confluence / ## Jira sections that upgraded consumers no longer read — so they break silently. Migrate them before anything else.


Arguments

None. The mode is detected from .agent-settings/project-config.md: missing file → Mode A (initial setup); legacy schema → Mode M (migrate) then Mode B; current schema → Mode B (re-calibration).


Trigger phrases

  • Initial setup: "set up project config", "init project config", "configure skills"
  • Re-calibrate: "recalibrate project config", "update project config", "my framework changed", "rescan project structure"
  • Update Atlassian only: "update confluence settings", "change jira project key"

Read the full file on GitHub · 303 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. 7d ago First seen · 303 lines · 123 tokens per session scan C 8fabb3a5e62a

Subscribe to this mod's changes

setup-project-config is a skill published in the GitHub repository jamesyang124/agent-skills (2 stars, last pushed 1mo ago), licensed MIT. It adds 123 tokens to every session and 3,318 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it C with 2 findings (reads agent configuration directories, reads mcp configuration). 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

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens

chronicle

Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…

microsoft/vscode · 72 tokens

babysit-pr

Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…

openai/codex · 114 tokens