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 alexei-led/cc-thingz --skill installation-doctorgit clone --depth 1 https://github.com/alexei-led/cc-thingzWrote 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/alexei-led/cc-thingz/installation-doctor)<a href="https://agentmods.dev/skills/alexei-led/cc-thingz/installation-doctor"><img src="https://agentmods.dev/badge/skills/alexei-led/cc-thingz/installation-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/alexei-led/cc-thingz/installation-doctor"><img src="https://agentmods.dev/badge/skills/alexei-led/cc-thingz/installation-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.00058 | $0.00503 |
| Opus 5 | $0.00029 | $0.00251 |
| Sonnet 5 | $0.00012 | $0.00101 |
| Haiku 4.5 | $0.00006 | $0.00050 |
Grade A, and why
installation-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 2d 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 — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Installation Doctor
Inspect installed resources without a repository checkout. The helper compares files against its bundled release catalog; it does not execute hooks or modify installations.
Run
- Locate
scripts/doctor.pyrelative to this installedSKILL.md. - Use an existing Python 3.12+ interpreter with
-B. If using uv, runuv run --no-project python -B <skill-directory>/scripts/doctor.py --json. uv may populate its own cache; use an existing interpreter directly when the entire invocation must be read-only. - Select roots for the requested runtime. Without root options the helper
inspects the Codex cc-thingz marketplace cache and user flat skill directories.
For Claude or a specific installation, pass
--plugin-root <directory>. Repeat--plugin-rootor--skill-rootfor multiple locations. Any explicit root option restricts inspection to supplied roots. - Optionally pass
--config-root <.codex-directory>to check agent profile presence, or--repo <cc-thingz-checkout>for comparison with source manifests. - Summarize failed checks with paths, migration suggestions, and verification gaps. Exit 1 means findings; exit 2 means invalid arguments.
Interpretation
- Cached copies do not prove enabled plugins or duplicate execution. Inspect the runtime's enabled-plugin list before recommending removal.
- Versions are compared with the release containing this helper, not an online latest release. Without a containing native manifest, version checks are skipped.
- Hook support, helper dependencies, active plugins, and effective permissions remain unsupported by static inventory; exit 0 does not verify them.
- Report missing Python or unreadable metadata precisely. Do not install tools, change configuration, or delete caches as part of this diagnostic run.
Output
Report the inspected roots, baseline release, confirmed findings with paths, skipped or unsupported checks, and the next corrective action. Keep hook commands and credential contents out of the response.
What ships with it
2 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.
- 2d ago First seen · 49 lines · 58 tokens per session scan A a0477653d5b5
installation-doctor is a skill published in the GitHub repository alexei-led/cc-thingz (35 stars, last pushed today), licensed MIT. It adds 58 tokens to every session and 503 once invoked, about $0.0003 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-09-09.
Other skills, from other repositories
systemic-issue-triage
Trigger: new issue, bug report, triage, backlog, issue flood, community report, root cause, dead-end, blocked user. Attack issues by root class, never one-by-one; fixes must shrink the system, not grow it.
issue-root-resolution
Trigger: root audit, atacar la raíz, issue roots, backlog roots, mechanism map, deletion-driven fix, resolver issues de raíz, close outdated issues. Audit and resolve issue clusters by verified root cause.
rdd-defect-workflow
Trigger: RDD, receipt-driven development, review authority, receipt/lineage, correction/recovery, delivery gate/kill switch, bounded review defects. Guide work.
qa
Use to verify that code works correctly — browser-based testing with Playwright, native app testing with computer use, CLI testing, API testing, or root-cause debugging. Supports --quick, --standard, --thorough modes. Triggers on /qa.
ring:searching-code
Forensic code search and analysis with optional Chain of Draft (CoD) ultra-concise mode. Five-phase methodology (clarification, planning, execution, analysis, synthesis) with severity assessment. Use for targeted investigation of specific patterns, bugs, or vulnerabilities. Skip for broad architecture mapping (use…
ring:test-driven-development
Enforcing the RED-GREEN-REFACTOR loop: write one failing test and watch it fail, write minimal code to pass, then refactor green. Use when starting implementation of a new feature or bugfix, or writing any new production code. Requires pasted failure output as proof of RED; code written before its test must be…