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/sherpa-sh/Sherpa-ActionWrote 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/sherpa-sh/sherpa-action/sherpa)<a href="https://agentmods.dev/plugins/sherpa-sh/sherpa-action/sherpa"><img src="https://agentmods.dev/badge/plugins/sherpa-sh/sherpa-action/sherpa/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/sherpa-sh/sherpa-action/sherpa"><img src="https://agentmods.dev/badge/plugins/sherpa-sh/sherpa-action/sherpa.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
Sherpa 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 9d 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
{
"name": "Sherpa",
"description": "Turn any cloud into a Platform-as-a-Service using human language",
"version": "1.0.0",
"author": {
"name": "Sherpa.sh"
}
}What it installs
The manifest is a name and a version. 5 commands, 5 MCP servers travel with it, and installing the plugin installs all of them — 49 tokens a session between them. Each is measured on its own page, and each can be installed alone.
- Command deploy A 15 tokens
- Command plan-deploy A 7 tokens
- Command create-infrastructure A 9 tokens
- Command build A 12 tokens
- Command detect-build-info A 6 tokens
- MCP server aws-mcp A not measured
- MCP server aws-knowledge-mcp-server A not measured
- MCP server cloudflare A not measured
- MCP server cloudflare-docs A not measured
- MCP server next-devtools A not measured
What ships with it
15 files beside plugin.json 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.
- skills/angular-deployment.md 7.5 KB
- skills/astro-deployment.md 8.5 KB
- skills/aws.md 188 B
- skills/cdn-uploading.md 573 B
- skills/cloudflare.md 405 B
- skills/manage-infrastructure.md 2.9 KB
- skills/nextjs-deployment.md 1.4 KB
- skills/nodejs-backend.md 2.7 KB
- skills/nuxt-deployment.md 5.9 KB
- skills/react-deployment.md 4.0 KB
- skills/remix-deployment.md 9.1 KB
- skills/sherpa-github-workflow.md 867 B
- skills/sveltekit-deployment.md 7.8 KB
- skills/vm-access.md 2.0 KB
- skills/vue-deployment.md 4.5 KB
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.
- 9d ago First seen · 8 lines scan A 742b3f419700
Sherpa is a plugin published in the GitHub repository sherpa-sh/Sherpa-Action (22 stars, last pushed 7mo ago), licensed Apache-2.0. 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-30.
Other plugins, from other repositories
defang
Deploy Docker Compose apps to your own cloud account using Defang. Includes a /defang:deploy skill and Defang MCP server integration.
nable
Ask your AWS, Azure, GCP, Kubernetes, and SaaS bill, inside Claude. 180+ tools (read-only analysis; remediation drafts PRs for human approval) for cost queries, anomaly detection, rightsizing, and PRs. Runs on your machine; credentials stay on your machine.
sandy-cli
Sandy: sandboxed TypeScript execution for AWS queries via the sandy CLI.
sandy-mcp
Sandy: sandboxed TypeScript execution for AWS queries via MCP.
cloud-cost-agent
Native-first FinOps agent for AWS, GCP, and Azure. Finds cloud savings using each provider's own CLIs and recommendation engines (Cost Explorer/Compute Optimizer, GCP Recommender, Azure Advisor).
nextjs
Official Next.js skills: adopt and optimize Cache Components, adopt Partial Prefetching, and verify runtime behavior against a running dev server.