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 vladkesler/initrunner --skill environment-diagnosticsgit clone --depth 1 https://github.com/vladkesler/initrunnerWrote 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/vladkesler/initrunner/environment-diagnostics)<a href="https://agentmods.dev/skills/vladkesler/initrunner/environment-diagnostics"><img src="https://agentmods.dev/badge/skills/vladkesler/initrunner/environment-diagnostics/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/vladkesler/initrunner/environment-diagnostics"><img src="https://agentmods.dev/badge/skills/vladkesler/initrunner/environment-diagnostics.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 5 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Prompt Injection · line 156 This pattern attempts to override system instructions or ignore safety constraints. Without LLM analysis, manual review is recommended.Fix: Remove or rewrite any text that instructs the agent to ignore prompts, override safety rules, or trust unverified content. Ensure skill content cannot be injected to alter agent behavior.
- high Privilege Escalation · line 153 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- high Privilege Escalation · line 156 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- medium Tool Misuse · line 125 Tool defaults are unsafe or overly permissive (e.g. disabled TLS verification, no authentication, world-writable permissions). Unsafe defaults widen the attack surface.Fix: Override unsafe defaults with secure settings (verify=True, auth required, restrictive permissions). Review and harden all tool configurations.
- medium Data Exfiltration · line 139 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
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.00034 | $0.01232 |
| Opus 5.5 | $0.00014 | $0.00493 |
| Sonnet 5.5 | $0.00007 | $0.00246 |
| Haiku 4.5 | $0.00003 | $0.00123 |
Grade A, and why
environment-diagnostics scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s -o /dev/null -w '%{http_code}' --max-time 5 https://api.example.com/health How it starts
The opening of the file, as written. The whole thing — 170 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Environment diagnostics skill for validating configuration and system state.
When to activate
Use this skill when tests fail with configuration or environment errors, when setting up a new development or staging environment, when a deployment fails with missing config or dependency issues, or when onboarding a new developer who needs to verify their local setup.
Environment variables
Check that required variables are set and non-empty:
python -c "
import os, sys
required = ['DATABASE_URL', 'API_KEY', 'SECRET_KEY']
missing = [v for v in required if not os.environ.get(v)]
if missing:
print('Missing or empty:', ', '.join(missing))
sys.exit(1)
print('All required variables present')
"
Common patterns to check:
- DATABASE_URL -- connection string for the primary database
- API_KEY / API_SECRET -- external service credentials
- SECRET_KEY / JWT_SECRET -- application signing keys
- REDIS_URL / CACHE_URL -- cache connection strings
- LOG_LEVEL -- logging configuration
- NODE_ENV / FLASK_ENV / RAILS_ENV -- runtime environment designation
For each variable, verify not just presence but also basic format validity (e.g., DATABASE_URL starts with a known scheme like postgres:// or mysql://).
Config files
Verify expected configuration files exist and parse correctly:
- Existence -- check that each expected config file is present.
- Syntax -- attempt to parse the file in its format:
python -c "import json; json.load(open('config.json'))" # JSON
python -c "import yaml; yaml.safe_load(open('config.yaml'))" # YAML
python -c "import tomllib; tomllib.load(open('pyproject.toml','rb'))" # TOML
- Required fields -- after parsing, verify that mandatory keys exist in the config structure.
- Value validation -- check that numeric values are in expected ranges, URLs are well-formed, and enum values match allowed options.
Port conflicts
Check if expected ports are available or already bound:
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.
- 1mo ago First seen · 170 lines · 34 tokens per session scan A 1081c4b6f528
environment-diagnostics is a skill published in the GitHub repository vladkesler/initrunner (40 stars, last pushed 5d ago), licensed Apache-2.0. It adds 34 tokens to every session and 1,232 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
skill-conflict-detector
Detects skill name shadowing and description-overlap conflicts that cause OpenClaw to trigger the wrong skill or silently ignore one when two skills compete for the same intent.
skill-portability-checker
Validates that a skill's companion scripts declare their OS and binary dependencies correctly, and checks whether those dependencies are actually present on the current machine.
mcp-health-checker
Monitors MCP server connections for health, latency, and availability — detects stale connections, timeouts, and unreachable servers before they cause silent tool failures.
skill-doctor
Diagnoses silent skill discovery failures — YAML parse errors, path violations, schema mismatches — so broken skills don't disappear without a trace.
loop-circuit-breaker
Detects infinite tool-call retry loops from deterministic errors and breaks them before they drain context or budget.
openclaw-config-advisor
Diagnoses OpenClaw provider, fallback, channel, MCP, and gateway config issues with read-only scans and stateful summaries.