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/ccivlcid/vibeharness/dev-environment-setupnpx skills add ccivlcid/VibeHarness --skill dev-environment-setupgit clone --depth 1 https://github.com/ccivlcid/VibeHarnessWrote 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/ccivlcid/vibeharness/dev-environment-setup)<a href="https://agentmods.dev/skills/ccivlcid/vibeharness/dev-environment-setup"><img src="https://agentmods.dev/badge/skills/ccivlcid/vibeharness/dev-environment-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.00043 | $0.00390 |
| Opus 5 | $0.00022 | $0.00195 |
| Sonnet 5 | $0.00009 | $0.00078 |
| Haiku 4.5 | $0.00004 | $0.00039 |
Grade A, and why
dev-environment-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 4d 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.
What it actually says
Setup — Dev Environment
Guide non-developers through installing necessary tools. All instructions must be completable via copy-paste.
Node.js Installation
- Go to https://nodejs.org
- Click the green button (LTS) to download
- Run the installer
- Close and reopen the terminal after installation
Python Installation
- Go to https://www.python.org/downloads/
- Click the yellow "Download Python" button
- Windows: CHECK the "Add Python to PATH" checkbox at the bottom
- Run the installer
- Close and reopen the terminal after installation
Git Installation
- Mac: Run
xcode-select --installin terminal - Windows: Download from https://git-scm.com and install
How to Open Terminal
- Mac: Press Command + Space, type "Terminal", click the app
- Windows: Press the Windows key, type "cmd" or "Command Prompt", click it
Verify Installation
After installing a tool, always run the verification command:
node --version # Node.js
python --version # Python
git --version # Git
If a version number appears, it worked.
Guidance Principles
- List every step with numbers (1, 2, 3...)
- Provide commands that can be completed via copy-paste
- Tell them what to expect ("if you see a number, it worked")
- Install one tool at a time
- Always remind to close and reopen the terminal after installation
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.
- 4d ago First seen · 56 lines · 43 tokens per session scan A 31d71d2374e0
dev-environment-setup is a skill published in the GitHub repository ccivlcid/VibeHarness (5 stars, last pushed 4mo ago), licensed MIT. It adds 43 tokens to every session and 390 once invoked, about $0.0002 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.
Other skills, from other repositories
article-writing
Write articles, guides, blog posts, tutorials, newsletter issues, and other long-form content in a distinctive voice derived from supplied examples or brand guidance. Use when the user wants polished written content longer than a paragraph, especially when voice consistency, structure, and credibility matter.
ljg-learn
Deep concept anatomist that deconstructs any concept through 8 exploration dimensions (history, dialectics, phenomenology, linguistics, formalization, existentialism, aesthetics, meta-philosophy) and compresses insights into an epiphany. Use when user asks to explain, dissect, or deeply understand a concept, term, or…
eli5
Explain research, papers, or technical ideas in plain English with minimal jargon, concrete analogies, and clear takeaways. Use when the user says "ELI5 this", asks for a simple explanation of a paper or research result, wants jargon removed, or asks what something technically dense actually means.
code-documenter
Use when adding docstrings, creating API documentation, or building documentation sites. Invoke for OpenAPI/Swagger specs, JSDoc, doc portals, tutorials, user guides.
deck-course-module
暖纸背景 + Playfair, 左侧学习目标常驻, 含 MCQ 自测页.
grid-ctf-ops
Operational knowledge for the gridctf scenario including strategy playbook, lessons learned, and resource references. Use when generating, evaluating, coaching, or debugging gridctf strategies.