setup

A project setup assistant for new or existing software projects. It detects the project type and can add development rules and checks such as tests, secret scanning, file-size limits, and Git hooks.

In plain words
What is it for?
Use it to bootstrap a project or add quality and security checks to an existing one.
Why use it?
It helps establish consistent project safeguards without setting them up manually from scratch.

Skill for Claude CodeCodex

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/jrenaldi79/harness-engineering/setup
Any agent
npx skills add jrenaldi79/harness-engineering --skill setup
Clone the repo
git clone --depth 1 https://github.com/jrenaldi79/harness-engineering

Made for: Claude Code, Codex.

Per session 67 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,431 The whole file, excluding the scripts and references it only reads on demand.
Security scan D 2 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 $0.00067 $0.02431
Opus 5 $0.00034 $0.01215
Sonnet 5 $0.00013 $0.00486
Haiku 4.5 $0.00007 $0.00243

Measured 2d ago against content hash c7c020fb76b8, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade D, and why

setup scanned grade D 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 2d ago.

The scan reads SKILL.md. This mod also ships 11 executable files (scripts/generate-claude-md.js, scripts/init-project.js, scripts/install-enforcement.js, …), 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.

Reads agent configuration directoriesmediumAgent snooping

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

SKILL_DIR=$(find ~/.claude/plugins -path "*/setup/SKILL.md" -print -quit | xargs dirname)

Recursive force deletehighDestructive command

rm -rf with a variable or a broad path is one typo away from removing the wrong tree.

- `.claude/settings.json` with pre-approved commands (test, lint, build, git) and a deny list blocking destructive operations (rm -rf /, git push --force, etc.). Normal file removal still works — Claude prompts for appro
skills/setup/SKILL.md · 203 lines

How it starts

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

Resource Resolution Preamble

Before any other step, resolve the skill's install directory:

SKILL_DIR=$(find ~/.claude/plugins -path "*/setup/SKILL.md" -print -quit | xargs dirname)
SCRIPTS_DIR=$SKILL_DIR/scripts
TEMPLATES_DIR=$SKILL_DIR/templates
REFERENCES_DIR=$SKILL_DIR/references

If SKILL_DIR is empty, halt and tell the user: "Could not locate the setup plugin directory under ~/.claude/plugins. Verify the plugin is installed."


Phase 1: Detect Environment

Check the working directory for these manifest files: package.json, pyproject.toml, CMakeLists.txt, go.mod, Cargo.toml, Makefile.

Also check for: .git/, src/, existing CLAUDE.md.

Determine:

  • New project — no manifest, no .git/, effectively an empty directory
  • Existing project — manifest file present; infer language and stack from it

For existing projects, record the detected stack so Phase 2 questions can be skipped where answers are already known.


Phase 2: Socratic Questions

Use the AskUserQuestion tool for each question, one at a time. Adapt or skip questions based on what was detected in Phase 1.

Q1 — Purpose (always ask): "What are you building?" — understand whether this is a web app, REST API, CLI tool, data pipeline, ML project, firmware, mobile app, etc.

Q2 — Language/stack (skip if inferred from manifest): "What language/stack would you like to use?"

Recommend based on the answer to Q1:

  • UI/web app → Node/TypeScript (default recommendation)
  • Backend API → Node/TypeScript or Python
  • Data science / ML → Python
  • Firmware / embedded → C/C++
  • Systems programming or CLI → Go or Rust

Q3 — Framework (skip if inferred; options depend on stack chosen):

  • Node/TS: Express, Fastify, Next.js, NestJS, or none
  • Python: FastAPI, Flask, Django, or none
  • Go: net/http, Gin, Echo, or none
  • C/C++: ask about build system (CMake, Make, Meson) instead of framework

Q4 — Project name (new projects only): "What should the project be called?" — suggest the current directory name as the default.

Read the full file on GitHub · 203 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. 2d ago First seen · 203 lines · 67 tokens per session scan D c7c020fb76b8

Subscribe to this mod's changes

setup is a skill published in the GitHub repository jrenaldi79/harness-engineering (66 stars, last pushed 5mo ago), licensed MIT. It adds 67 tokens to every session and 2,431 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it D with 2 findings (reads agent configuration directories, recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

nv-context

Set up state-of-the-art context engineering for any repository. Analyzes codebase, generates multi-level CLAUDE.md/AGENTS.md hierarchy, hooks, session management, and token budgets. Based on 200+ sources including ETH Zurich, Anthropic, Google DeepMind, and Manus production data. For engineers who ship with AI agents.

johnnichev/nv-context · 73 tokens

talk-like-scarletkc

按 scarletkc 本人的自然表达习惯撰写、改写、润色和翻译文本,覆盖推文、微博、评论、聊天消息、技术观点、项目介绍、GitHub 文本(README、issue、PR、发布说明)和正式通信。当用户要求用自己的口吻写东西、把 AI 腔文字改自然、发推、回评论、点评模型或开发工具、写项目公告、写礼貌但直接的客服或正式邮件,或要求翻译时保留语气和立场,都使用本 skill,即使用户没有点名 scarletkc 或提出风格要求。.

scarletkc/agents · 141 tokens

marketing-copy

Write outbound promotional copy for a product or project: launch and update posts for community platforms and social media, store page descriptions and short blurbs, landing page headlines and calls to action, press-style announcements, and the naming of a product for another language or market. Covers what may be…

scarletkc/agents · 121 tokens

scoped-change

Judgment rules for locating the correct boundary of a requested change: staying inert outside it while completing every required site inside it. Use when scope is ambiguous, a diff touches neighboring surfaces, required dependent edits are unclear, or a proposed compatibility layer, migration, fallback, flag…

scarletkc/agents · 69 tokens

agentic-code-review

Use when reviewing a diff, pull request, branch, or AI-generated code for correctness, security, regression, test, performance, and maintainability risks before merge.

DominikTobureto/awesome-grok-build · 38 tokens

hooksmith

Use when designing or reviewing safe Grok Build hooks for linting, tests, formatting, notifications, command guards, lifecycle automation, or project hook trust decisions.

DominikTobureto/awesome-grok-build · 35 tokens