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/plugins/ashlrai/ashlr-stack/plugin)<a href="https://agentmods.dev/plugins/ashlrai/ashlr-stack/plugin"><img src="https://agentmods.dev/badge/plugins/ashlrai/ashlr-stack/plugin/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/plugins/ashlrai/ashlr-stack/plugin"><img src="https://agentmods.dev/badge/plugins/ashlrai/ashlr-stack/plugin.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
stack 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 today.
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
{
"name": "stack",
"version": "0.1.0",
"description": "Plan and configure supported project services from Claude Code with Stack's CLI and MCP bridge.",
"author": {
"name": "Mason Wyatt",
"url": "https://github.com/ashlrai"
},
"homepage": "https://stack.ashlr.ai/",
"repository": "https://github.com/ashlrai/ashlr-stack",
"license": "MIT",
"keywords": ["claude-code", "plugin", "mcp", "stack", "devops", "ashlr"],
"mcpServers": {
"ashlr-stack": {
"command": "bash",
"args": ["${CLAUDE_PLUGIN_ROOT}/scripts/mcp-entrypoint.sh"]
}
}
}
What it installs
The manifest is a name and a version. 6 commands, 1 hook travel with it, and installing the plugin installs all of them — 95 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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.
- today Changed 9fc639af2336
- 1mo ago First seen · 20 lines scan A 6566df047126
stack is a plugin published in the GitHub repository ashlrai/ashlr-stack (2 stars, last pushed today), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
cloud-infrastructure
Cloud architecture design for AWS/Azure/GCP/OCI, Kubernetes cluster configuration, Terraform infrastructure-as-code, hybrid cloud networking, and multi-cloud cost optimization.
database-cloud-optimization
Database query optimization, cloud cost optimization, and scalability improvements.
deployment-strategies
Deployment patterns, rollback automation, and infrastructure templates.
deployment-validation
Pre-deployment checks, configuration validation, and deployment readiness assessment.
claude-plugin
Route IDE and agent prompts through Duel Agents: concurrent model routing with a single API key.
trelly
Trello CLI + MCP tools — boards, lists, cards, search, and raw API via trelly-mcp.