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 ashlrai/ashlr-plugin --skill ashlr-codex-doctorgit clone --depth 1 https://github.com/ashlrai/ashlr-pluginWrote 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/ashlrai/ashlr-plugin/ashlr-codex-doctor)<a href="https://agentmods.dev/skills/ashlrai/ashlr-plugin/ashlr-codex-doctor"><img src="https://agentmods.dev/badge/skills/ashlrai/ashlr-plugin/ashlr-codex-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/ashlrai/ashlr-plugin/ashlr-codex-doctor"><img src="https://agentmods.dev/badge/skills/ashlrai/ashlr-plugin/ashlr-codex-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.00044 | $0.00184 |
| Opus 5 | $0.00022 | $0.00092 |
| Sonnet 5 | $0.00009 | $0.00037 |
| Haiku 4.5 | $0.00004 | $0.00018 |
Grade A, and why
ashlr-codex-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 8d 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
Ashlr Codex Doctor
Run:
ashlr codex-doctor --json
Read the JSON before changing files. Focus on:
pluginManifest.present,hasSkills,hasMcpServers, andhasHooksmcp.serverandmcp.binhooks.defaultMode, which should normally benudgeworkspaceAccess.allowProjectPathswhen tools refuse paths outside cwd
If workspace access is the issue, set ASHLR_ALLOW_PROJECT_PATHS to the absolute project root before launching Codex or pass explicit cwd arguments to Ashlr MCP tools.
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.
- 8d ago First seen · 22 lines · 44 tokens per session scan A dd44ce7e2cdb
ashlr-codex-doctor is a skill published in the GitHub repository ashlrai/ashlr-plugin (3 stars, last pushed yesterday), licensed MIT. It adds 44 tokens to every session and 184 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
diagnosing-bugs
Diagnosis loop for hard bugs and performance regressions. Builds a red-capable feedback loop and runs it before hypothesising — complements static code review (which finds bugs by reading) by running actual repros. Use when the user says 'diagnose'/'debug this', or reports something broken/throwing/failing/slow.
issue-debugging
Systematic methodology for issue debugging including root cause analysis, impact mapping, tiered validation plans, and confidence assessment. Use when analyzing bugs, fixing issues, or validating fixes.
fix-bug
Run the Fix Validation pipeline to investigate, fix, and validate a bug. Ensures deterministic pipeline execution with IssueAnalyzer, FixWriter, TestWriter (conditional), TestAudit (conditional), and FixValidator stages.
ccc-systematic-debugging
Root-cause debugging via the Iron Law: no fix without confirmed root cause. Reproduce → hypothesize → verify → fix. Use when investigating bugs, test failures, or…
debug
Analyze errors and apply fixes. Use when you have an error message, traceback, or failing log to diagnose.
fable-recover
Diagnose repeated command failures, stale build caches, branch drift, or contradictory evidence before attempting further code edits. Use when commands fail repeatedly, tests stay red after attempted fixes, build output contradicts source code, or the execution path is confused — even if the user does not explicitly…