env-setup

env-setup is a skill for Claude Code from viknesh20-20/claude-code-tool-kit. It costs 43 tokens per session (745 once invoked), scanned A, original, MIT.

A first-time project setup assistant that identifies required tools and services, documents configuration, and checks whether the development environment is ready. It can generate a template for environment variables without including their secret values.

In plain words
What is it for?
Use it when starting work on an unfamiliar project or preparing a new machine. It can inspect project files, create an environment-variable template, document prerequisites, create setup scripts, and verify installed tools.
Why use it?
It removes guesswork when a project depends on particular runtimes, databases, services, or command-line tools. It also makes setup requirements easier for other developers to reproduce.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Good fit Use it when starting work on an unfamiliar project or preparing a new machine. It can inspect project files, create an environment-variable template, document prerequisites, create setup scripts, and verify installed tools.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/viknesh20-20/claude-code-tool-kit/env-setup
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 viknesh20-20/claude-code-tool-kit --skill env-setup
Clone the repo
git clone --depth 1 https://github.com/viknesh20-20/claude-code-tool-kit

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 env-setup

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/viknesh20-20/claude-code-tool-kit/env-setup"><img src="https://agentmods.dev/badge/skills/viknesh20-20/claude-code-tool-kit/env-setup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 43 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 745 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.00043 $0.00745
Opus 5.5 $0.00017 $0.00298
Sonnet 5.5 $0.00009 $0.00149
Haiku 4.5 $0.00004 $0.00075

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

Security

Grade A, and why

env-setup 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/env-setup/SKILL.md · 96 lines

How it starts

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

Environment Setup

Detect Requirements

!ls package.json requirements.txt pyproject.toml go.mod Cargo.toml *.csproj Gemfile composer.json mix.exs 2>/dev/null !ls .env .env.example .env.sample .env.template 2>/dev/null !ls Dockerfile docker-compose* Makefile Procfile 2>/dev/null

Current Environment

!node --version 2>/dev/null || echo "Node.js: not installed" !python3 --version 2>/dev/null || echo "Python: not installed" !go version 2>/dev/null || echo "Go: not installed" !rustc --version 2>/dev/null || echo "Rust: not installed" !docker --version 2>/dev/null || echo "Docker: not installed" !git --version 2>/dev/null


Setup Process

Step 1: Identify Requirements

Scan project files to determine:

  • Runtime(s) and version(s) needed
  • Package manager(s)
  • Database(s)
  • Cache (Redis, Memcached)
  • External services (S3, email, payment, etc.)
  • Build tools
  • Required CLI tools

Step 2: Generate .env.example

Scan the codebase for environment variable references:

grep -rn "process\.env\." --include="*.ts" --include="*.js" | ...
grep -rn "os\.environ\|os\.getenv" --include="*.py" | ...
grep -rn "os\.Getenv" --include="*.go" | ...

Generate .env.example with:

# Application
APP_PORT=3000
APP_ENV=development
APP_SECRET=change-me-to-a-random-string

# Database
DATABASE_URL=postgresql://user:password@localhost:5432/dbname

# External Services
# API_KEY=your-api-key-here

Include:

  • Comments explaining each variable
  • Safe defaults for development
  • Placeholder values for secrets (never real values)
  • Grouped by category

Step 3: Check Prerequisites

Verify each requirement is met:

Requirement Status Version Required
Node.js OK/MISSING v20.x >=18
... ... ... ...

Step 4: Generate Setup Instructions

Create or update setup documentation:

  1. Prerequisites to install
  2. Clone and install steps
  3. Environment configuration
  4. Database setup (create, migrate, seed)
  5. Start development server
  6. Verify everything works

Read the full file on GitHub · 96 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. 1mo ago First seen · 96 lines · 43 tokens per session scan A 37bf5a55baf4

Subscribe to this mod's changes

env-setup is a skill published in the GitHub repository viknesh20-20/claude-code-tool-kit (7 stars, last pushed 5mo ago), licensed MIT. It adds 43 tokens to every session and 745 once invoked, about $0.0002 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-08-31.

Related

Other skills, from other repositories

paperclip

Use for Paperclip-managed tasks and heartbeats: reading task context, delivering task documents or files, updating completion or blockers, coordinating or delegating work, and following company governance. Includes control plane API operations for assignments, comments, approvals, and routines.

paperclipai/paperclip · 54 tokens

agentmail

Use your assigned AgentMail inbox to read email tasks, explicitly send or reply, and check delivery. Provided automatically by your inbox assignment.

paperclipai/paperclip · 30 tokens

cw-gates

Use before claiming any Codewhale change is done, green, or ready to land: the focused-to-broad verification ladder, the budget checks CI enforces, and the rules for what counts as a passing test.

Hmbown/Codewhale · 48 tokens

refocusing

Use when a long-running agent may have lost the product outcome, when context was compacted, when work has crossed a major boundary, or when a fresh path-based trace is needed before the next consequential action. Not for fresh-session orientation, waking an idle seat, or checkpoints.

mvschwarz/openrig · 59 tokens

oversight-team

Use when you are a seat on the oversight pod (a standing monitor-mode rig that keeps OTHER rigs healthy), configuring or running the drift detectors, or choosing whether to intervene vs escalate. Covers the pull-not-poll posture, the v0 detectors (premature-park, process-drift, off-task, token-burn), the intervention…

mvschwarz/openrig · 117 tokens

package-installer

Install third-party open-source projects (a GitHub URL or a local git directory the user provides) as external packages. The project is cloned verbatim into the per-user packages directory — never edit, normalize, or reorganize its files.

Orkas-AI/Orkas · 3 tokens