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/commands/sherpa-sh/sherpa-action/deploy)<a href="https://agentmods.dev/commands/sherpa-sh/sherpa-action/deploy"><img src="https://agentmods.dev/badge/commands/sherpa-sh/sherpa-action/deploy.svg" alt="Measured on agentmods" 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.00015 | $0.00380 |
| Opus 5 | $0.00008 | $0.00190 |
| Sonnet 5 | $0.00003 | $0.00076 |
| Haiku 4.5 | $0.00002 | $0.00038 |
Grade A, and why
deploy 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
Take the user context into account when building and deploying the project: "$ARGUMENTS"
Be vocal, share the steps you are taking.
Step 1: Prep
- If
.sherpa.sh/build-info.mddoesn't exist run the plugin command/Sherpa/detect-build-info. - If
.sherpa.sh/deployment-plan.mddoesn't exist run the plugin command/Sherpa/plan-deployment.
Step 2: Build
3. Run /Sherpa/build to build the project
4. Run /Sherpa/create-infrastructure to ensure the needed infrastructure exists
Step 3: Deployment:
- Read the files
.sherpa.sh/build-info.mdand.sherpa.sh/deployment-plan. - Execute the deployment plan by uploading and running the application code and static assets based on the deployment plan. Always use the provider skill. Always use the MCP server. Never use Terraform.
Step 4: Document (REQUIRED - DO NOT SKIP) You MUST complete this step before finishing.
-
Write the commands that worked to build and deploy into
.sherpa.sh/executionlog.md(overwrite what's existing) for later use so you can repeat the process. Include:- Build commands used
- Deployment commands and API calls made
- Any configuration changes applied
- Timestamp of this deployment
-
Verify
.sherpa.sh/infrastructure.mdexists and is up to date (created by/Sherpa/create-infrastructure).
IMPORTANT! NEVER write secrets, credentials, passwords, or API keys into these documents. Refer to them by UPPERCASE variable names (e.g., $CLOUDFLARE_API_TOKEN).
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 · 35 lines · 15 tokens per session scan A be6a6d22f578
deploy is a command published in the GitHub repository sherpa-sh/Sherpa-Action (22 stars, last pushed 7mo ago), licensed Apache-2.0. It adds 15 tokens to every session and 380 once invoked, about $0.0001 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-30.
Other commands, from other repositories
review_pr
Review as a Principal AWS Solutions Architect. You have deep expertise in AWS CDK and TypeScript, serverless and container compute, security/IAM least-privilege, cost, and operational excellence. You hold a high bar: correctness and long-term maintainability over short-term convenience. You are direct, specific, and…
scan
Scan AWS account for cost optimization.
oma:modernize
A command that starts a six-stage process for updating an existing legacy workload on AWS. It coordinates workload assessment, strategy selection, target architecture, container packaging, and production cutover, with risk checks and an audit trail between stages.
oma-platform-bootstrap
A command-based process for deploying an agentic AI platform on Amazon EKS, a managed Kubernetes service. It follows five checkpoints from gathering context through validation.
aws-kb
Read-only AWS knowledge lookup — query docs, CLI reference, SOPs, comparisons, onboarding pointers, and next-step recommendations from the kb MCP server. Stateless per turn; never writes spec artefacts.
checklist
Generate a custom checklist for the current feature based on user requirements.