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 hoatv2211/GameStudio-CodexKIT --skill multi-service-local-environment-doctorgit clone --depth 1 https://github.com/hoatv2211/GameStudio-CodexKITWrote 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/hoatv2211/gamestudio-codexkit/multi-service-local-environment-doctor)<a href="https://agentmods.dev/skills/hoatv2211/gamestudio-codexkit/multi-service-local-environment-doctor"><img src="https://agentmods.dev/badge/skills/hoatv2211/gamestudio-codexkit/multi-service-local-environment-doctor/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/hoatv2211/gamestudio-codexkit/multi-service-local-environment-doctor"><img src="https://agentmods.dev/badge/skills/hoatv2211/gamestudio-codexkit/multi-service-local-environment-doctor.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.00039 | $0.00807 |
| Opus 5 | $0.00019 | $0.00404 |
| Sonnet 5 | $0.00008 | $0.00161 |
| Haiku 4.5 | $0.00004 | $0.00081 |
Grade A, and why
multi-service-local-environment-doctor 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 11d 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 — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Multi-Service Local Environment Doctor
Overview
Build a read-only topology of services, processes, ports, and configuration, then identify collisions without starting or stopping anything.
When to use
Use for local server startup failures, port 27000 conflicts, MySQL 3306/3307 isolation, Redis or web listener issues, config drift, or multiple game stacks on one workstation.
When NOT to use
Do not use to kill processes, start services, edit configs, import databases, or claim a runtime is healthy from static config alone.
Required inputs and context discovery
Collect service names, executable or script paths, expected and configured hosts/ports, dependency order, process snapshot, listener snapshot, config files, project ownership, and forbidden service-control actions.
Safety and risk level
Read-only only. Process and port inspection is allowed; start, stop, kill, firewall, registry, database, and config changes require explicit approval and another workflow.
Workflow
- Inventory declared services and configuration sources. Completion criterion: each service has an owner, config path, expected host, and expected port.
- Capture active processes and listeners without controlling them. Completion criterion: observed listeners are a timestamped Snapshot.
- Compare expected, configured, and observed ports and dependencies. Completion criterion: collisions, missing listeners, and mismatches are separated.
- Identify cross-project ownership such as Project Alpha versus Project Beta and database port isolation. Completion criterion: no proposed fix crosses a project boundary silently.
- Recommend the smallest safe next action and label service-control work BLOCKED pending approval. Completion criterion: the report does not mutate the environment.
Evidence and output contract
Produce environment-report.json with services, configs, expected/observed listeners, conflicts, mismatches, ownership, limitations, and recommended next checks.
What ships with it
3 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.
- 11d ago First seen · 79 lines · 39 tokens per session scan A e82e14d42f09
multi-service-local-environment-doctor is a skill published in the GitHub repository hoatv2211/GameStudio-CodexKIT (3 stars, last pushed 4d ago), licensed MIT. It adds 39 tokens to every session and 807 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
vibe-gap-analysis
Assesses production readiness or audits a codebase against its specs. Supports quick static mode, deep 17-dimension audit, or single-dimension focus.
vibe-gap-closure-loop
Closes production readiness gaps from a gap analysis document. Autonomously loops dependency analysis, parallel agent dispatch, test gate, re-audit, and repeats until target dimensions reach target score.
vibe-debugging-journal
Records resolved bugs in a persistent journal — symptom, root cause, difficulty, fix, prevention. Organized by category for future reference.
vibe-production-mindset
Sets quality expectations for implementation — "imagine this serves 1 million users." Checks for observability, error handling, input validation, graceful degradation.
vibe-wave-based-remediation
Systematically fixes large backlogs of issues using prioritized waves. Use when facing 10+ issues, bugs, or gaps to address.
agent-performance-optimizer
Agent skill for performance-optimizer - invoke with $agent-performance-optimizer.