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 skills add desirecore/market --skill dev-environment-setupgit clone --depth 1 https://github.com/desirecore/marketWrote 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/desirecore/market/dev-environment-setup)<a href="https://agentmods.dev/skills/desirecore/market/dev-environment-setup"><img src="https://agentmods.dev/badge/skills/desirecore/market/dev-environment-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.
<a href="https://agentmods.dev/skills/desirecore/market/dev-environment-setup"><img src="https://agentmods.dev/badge/skills/desirecore/market/dev-environment-setup.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00202 | $0.02714 |
| Opus 5.5 | $0.00081 | $0.01086 |
| Sonnet 5.5 | $0.00040 | $0.00543 |
| Haiku 4.5 | $0.00020 | $0.00271 |
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 25d 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 — 184 lines — stays where its author put it; the contents beside it link to each section on GitHub.
dev-environment-setup Skill (v2.0.0 router)
L0: One-line Summary
When to use: The user needs to
- Install / troubleshoot Docker or Podman containers ("docker not found", daemon startup, registry mirror, etc.)
- Configure WSL2 (Linux Subsystem) on Windows
- One-shot install of office skill dependencies (Python packages + npm packages + system tools required by DOCX / PDF / XLSX / PPTX)
- Install system tools: LibreOffice / Poppler / Pandoc / Tesseract / qpdf / ImageMagick / Ghostscript / Git
- Uncertain whether the issue belongs to Python or Node.js, and a comprehensive diagnosis is needed first
When not to use: Use python-runtime for pure Python issues, and nodejs-runtime for pure Node.js issues.
How to do it: First run scripts/probe.sh (use probe.ps1 on Windows) to obtain a system snapshot JSON,
and route to the corresponding references or sub-skill based on the result; this skill is also the source of truth
for DesireCore's built-in Hatch / Volta / HTTP API / Socket.IO integration (references/desirecore-runtime.md).
L1: Routing Rules
Route directly to the corresponding skill or document by the keywords in the user's question:
| Keyword / Scenario | Path |
|---|---|
| python / pip / venv / pyenv / hatch / virtualenv / PEP 668 | python-runtime skill |
| node / npm / pnpm / yarn / volta / nvm / fnm / EACCES | nodejs-runtime skill |
| docker / podman / container / container daemon | references/container.md |
| WSL / WSL2 / Windows Linux Subsystem | references/wsl.md |
| DOCX / PDF / XLSX / PPTX dependencies / office skill dependencies | references/office-deps.md |
| LibreOffice / poppler / pandoc / tesseract / qpdf | references/system-tools.md |
| Unsure of category, want a quick diagnosis | First run scripts/probe.sh and inspect the JSON |
| DesireCore Hatch / Volta / HTTP API / Socket.IO | references/desirecore-runtime.md |
User edited .zshrc / an env var / proxy / setx, but tools can't see it |
POST /api/runtime/environment/refresh reloads the login environment (see references/desirecore-runtime.md §7, no app restart needed) |
| Four-tier fallback decision (API → CLI → package manager → community solution) | references/decision-tree.md |
What ships with it
11 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.
- catalog-metadata.v1.json 3.2 KB
- references/container.md 4.5 KB
- references/decision-tree.md 6.5 KB
- references/desirecore-runtime.md 8.6 KB
- references/office-deps.md 4.2 KB
- references/probe-snapshot.md 4.4 KB
- references/system-tools.md 4.5 KB
- references/wsl.md 3.1 KB
- scripts/probe.ps1 2.0 KB runs code
- scripts/probe.sh 2.3 KB runs code
- SKILL.zh-CN.md 5.7 KB
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.
- 25d ago Changed · +1 lines 4cf775a80f4a
- 1mo ago First seen · 183 lines · 202 tokens per session scan A 46237f0edc79
dev-environment-setup is a skill published in the GitHub repository desirecore/market (2 stars, last pushed 2d ago), licensed MIT. It adds 202 tokens to every session and 2,714 once invoked, about $0.0008 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.
Other skills, from other repositories
docker-compose-generator
Generate Docker Compose configurations for development environments - auto-detect project stack, configure services with dependencies, volumes, networking, and health checks.
docker-local-build
Build and test Kurtosis from source on local Docker. Compiles all components (engine, core, files-artifacts-expander), builds Docker images, installs the CLI, and restarts the engine. Use when developing Kurtosis and testing changes locally with Docker.
k8s-dev-deploy
Build, push, and deploy Kurtosis dev images to a Kubernetes cluster without creating a release. Rebuilds engine, core, and files-artifacts-expander as multi-arch Docker images with a unique tag, pushes to the logged-in user's Docker Hub, and restarts the engine. Use when testing local code changes on a k8s cluster.
docker-debug
Debug Kurtosis running on local Docker. Inspect engine, API container, and service logs. Diagnose container crashes, port conflicts, and networking issues. Use when kurtosis commands fail or services aren't reachable on Docker.
k8s-debug-pods
Debug Kurtosis pods on Kubernetes. Diagnose why pods are Pending, CrashLoopBackOff, ImagePullBackOff, or Evicted. Check node taints, tolerations, resource pressure, and pod events. Use when kurtosis engine start fails or pods aren't coming online.
k8s-clean-cluster
Force-clean all Kurtosis resources from a Kubernetes cluster when kurtosis clean hangs or fails. Removes all kurtosis namespaces, pods, daemonsets, cluster roles, and cluster role bindings. Use when kurtosis clean -a hangs or leaves behind orphaned resources.