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.
npx agentmods add skills/joaquimscosta/arkhe-claude-plugins/code-env-setupnpx skills add joaquimscosta/arkhe-claude-plugins --skill code-env-setupgit clone --depth 1 https://github.com/joaquimscosta/arkhe-claude-pluginsWrote 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.
[](https://agentmods.dev/skills/joaquimscosta/arkhe-claude-plugins/code-env-setup)<a href="https://agentmods.dev/skills/joaquimscosta/arkhe-claude-plugins/code-env-setup"><img src="https://agentmods.dev/badge/skills/joaquimscosta/arkhe-claude-plugins/code-env-setup.svg" alt="Measured on agentmods" height="20"></a>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 | $0.00090 | $0.00964 |
| Opus 5 | $0.00045 | $0.00482 |
| Sonnet 5 | $0.00018 | $0.00193 |
| Haiku 4.5 | $0.00009 | $0.00096 |
Grade A, and why
code-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 5d 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.
How it starts
The opening of the file, as written. The whole thing — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Claude Code Setup Wizard
Interactive environment setup following the Claude Code Guide.
Pre-flight
Run the detection script to understand current state:
python3 ${CLAUDE_SKILL_DIR}/scripts/detect_setup.py
Two-Phase Workflow
Phase 1: Detect
-
Run the detector on the project root:
python3 ${CLAUDE_SKILL_DIR}/scripts/detect_setup.py <project-root> -
Fetch the guide via WebFetch:
https://raw.githubusercontent.com/joaquimscosta/arkhe-claude-plugins/main/docs/CLAUDE_CODE_GUIDE.mdIf WebFetch fails (network error, 404), warn the user and proceed using LLM knowledge only.
-
Cross-reference detection JSON against guide recommendations to identify what is missing or incomplete.
-
Detect MCP servers separately via Bash:
claude mcp list
Phase 2: Configure
- Present category selection using
AskUserQuestion(multiSelect: true). Show detection status for each category (configured / partially configured / not configured):
| # | Category | Guide Section | What It Configures |
|---|---|---|---|
| 1 | Global CLAUDE.md | Section 1 | ~/.claude/CLAUDE.md — security NEVER rules, account config |
| 2 | Project Scaffolding | Section 2 | .claude/ dirs, .env.example, .gitignore, CLAUDE.md |
| 3 | MCP Servers | Section 3 | Install recommended servers via claude mcp add |
| 4 | Hooks | Section 7 | ~/.claude/hooks/block-secrets.py, hooks in settings.json |
| 5 | Custom Agents | Section 10 | ~/.claude/agents/ starter agent files |
| 6 | Keybindings | Section 13 | ~/.claude/keybindings.json |
| 7 | Settings | Section 13 | Language, background tasks in settings.json |
If user passed a specific category as argument (e.g., /devtools:code-env-setup hooks), skip the selection and go directly to that category.
- Walk through each selected category with targeted
AskUserQuestioncalls. See WORKFLOW.md for per-category question flows.
What ships with it
4 files 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.
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.
- 5d ago First seen · 88 lines · 90 tokens per session scan A 1cf5c234994f
code-env-setup is a skill published in the GitHub repository joaquimscosta/arkhe-claude-plugins (21 stars, last pushed 21d ago), licensed MIT. It adds 90 tokens to every session and 964 once invoked, about $0.0005 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-30.
Other skills, from other repositories
dummy-dataset
Generate realistic dummy datasets for testing with customizable columns, constraints, and output formats (CSV, JSON, SQL, Python script). Use when creating test data, building mock datasets, or generating sample data for development and demos.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
stakeholder-map
Build a stakeholder map using a power/interest grid, identify communication strategies per quadrant, and generate a communication plan. Use when managing stakeholders, preparing for a launch, aligning cross-functional teams, or planning stakeholder engagement.
competitive-battlecard
Create sales-ready competitive battlecards comparing your product against a specific competitor — positioning, feature comparison, objection handling, and win/loss patterns. Use when preparing sales teams, creating competitive materials, or responding to 'why not competitor X?'.
pronunciation-specialist
Scans lyrics for pronunciation risks and prevents Suno mispronunciations. Use when writing lyrics with proper nouns, technical terms, homographs, or non-English words.
researchers-tech
Researches project histories, changelogs, developer interviews, and open source documentation. Use when the album subject involves technology projects or developer stories.