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/add)<a href="https://agentmods.dev/commands/ashlrai/ashlr-stack/add"><img src="https://agentmods.dev/badge/commands/ashlrai/ashlr-stack/add/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/add"><img src="https://agentmods.dev/badge/commands/ashlrai/ashlr-stack/add.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.00019 | $0.00279 |
| Opus 5.5 | $0.00008 | $0.00112 |
| Sonnet 5.5 | $0.00004 | $0.00056 |
| Haiku 4.5 | $0.00002 | $0.00028 |
Grade A, and why
add 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 yesterday.
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
Run stack_add via the ashlr-stack MCP server. If the user didn't specify a service, list available providers first with stack_providers and ask which to add. (stack_list shows services already configured in this stack.)
Service names are lowercase provider ids (anthropic, auth0, aws, braintrust, clerk, cloudflare, convex, datadog, deepseek, digitalocean, firebase, fly, gcp, github, grafana, hetzner, launchdarkly, linear, mailgun, mixpanel, modal, neon, openai, plausible, posthog, postmark, railway, render, replicate, resend, sendgrid, sentry, stripe, supabase, turso, upstash, vercel, workos, xai). stack_providers is the authoritative list.
If Phantom setup is missing or refused, report that boundary and point to https://phm.dev/secrets for the installed-version setup guidance. Do not initialize a vault or grant permissions automatically. Confirm the selected provider and its create/attach and credential effects before calling. The server needs the intended project cwd, Stack CLI and runtime; tool metadata does not prove an installed client exposes the tool or that provider setup succeeds.
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.
- yesterday Changed 1ef8f617a990
- 1mo ago First seen · 10 lines · 19 tokens per session scan A 889f84b714da
add is a command published in the GitHub repository ashlrai/ashlr-stack (2 stars, last pushed today), licensed MIT. It adds 19 tokens to every session and 279 once invoked, about $0.0001 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
setup
Set up Duel Agents routing with your Duel API key.
generate-docs
Generate comprehensive technical documentation across infrastructure, backend, and frontend domains using a 7-stage pipeline.
assert
Validate implementation completeness, correctness, and compliance before testing phase through static analysis and requirements verification.
commit
Analyze changes and create atomic, conventional commits with intelligent message generation, version management, changelog updates, and quality insights.
gather-knowledge
Analyze codebase, dependencies, patterns, and constraints to build comprehensive technical context for planning or implementation.
refine-task
Clarify task requirements, acceptance criteria, and implementation details before planning phase.