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.
git clone --depth 1 https://github.com/ashlrai/ashlr-stackWrote 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/commands/ashlrai/ashlr-stack/doctor)<a href="https://agentmods.dev/commands/ashlrai/ashlr-stack/doctor"><img src="https://agentmods.dev/badge/commands/ashlrai/ashlr-stack/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/commands/ashlrai/ashlr-stack/doctor"><img src="https://agentmods.dev/badge/commands/ashlrai/ashlr-stack/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.00011 | $0.00115 |
| Opus 5.5 | $0.00004 | $0.00046 |
| Sonnet 5.5 | $0.00002 | $0.00023 |
| Haiku 4.5 | $0.00001 | $0.00012 |
Grade A, and why
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 3d 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
Call stack_doctor in the intended project context. Without all, a directory with no .stack.toml returns an error, not a healthy report; offer stack_init or { all: true }. Summarize the returned checks, including failures and adapters without a health check. Offer { fix: true } only after explaining the requested repair effects. Fix can skip entries whose vault names already exist; it does not rotate credentials or prove every service and consumer works.
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.
- 3d ago Changed 964748f46b48
- 4d ago Changed · +1 tokens per session 61a034351623
- 1mo ago First seen · 6 lines · 10 tokens per session scan A c324ab332550
doctor is a command published in the GitHub repository ashlrai/ashlr-stack (2 stars, last pushed yesterday), licensed MIT. It adds 11 tokens to every session and 115 once invoked, about $0.0000 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 commands, from other repositories
assert
Validate implementation completeness, correctness, and compliance before testing phase through static analysis and requirements verification.
performance-optimization
Orchestrate end-to-end application performance optimization from profiling to monitoring.
refactor-clean
Refactor provided code for cleanliness, maintainability, and alignment with SOLID principles and modern best practices — no over-engineering.
config-validate
Validate application configuration with schemas, per-environment rules, runtime checks, and secure handling of sensitive values.
smart-debug
AI-assisted smart debugging — parse error messages, stack traces, and failure patterns to identify root causes and produce a fix with automated observability steps.
team-debug
Debug issues using competing hypotheses with parallel investigation by multiple agents.