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.
npx skills add Benja-Pauls/SerpentStack --skill deploygit clone --depth 1 https://github.com/Benja-Pauls/SerpentStackWrote 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/skills/benja-pauls/serpentstack/deploy)<a href="https://agentmods.dev/skills/benja-pauls/serpentstack/deploy"><img src="https://agentmods.dev/badge/skills/benja-pauls/serpentstack/deploy/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/skills/benja-pauls/serpentstack/deploy"><img src="https://agentmods.dev/badge/skills/benja-pauls/serpentstack/deploy.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.00043 | $0.00997 |
| Opus 5.5 | $0.00017 | $0.00399 |
| Sonnet 5.5 | $0.00009 | $0.00199 |
| Haiku 4.5 | $0.00004 | $0.00100 |
Grade A, and why
deploy scanned grade A with 1 finding 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 1mo 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -sf $APP_URL/api/v1/health | jq . How it starts
The opening of the file, as written. The whole thing — 134 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Deploy
Build, push, and deploy SerpentStack to AWS using Docker and Terraform.
Environments
dev-- automatic deploys from main, auto-approve on applystaging-- manual trigger, shows plan for review before applyprod-- manual trigger, requires plan review before apply
All Terraform config lives in infra/environments/{env}/.
Quick Deploy
make deploy # Deploy to dev (default)
make deploy env=staging # Deploy to staging
make deploy env=prod # Deploy to production
Or use the GitHub Actions CD pipeline — it runs automatically on push to main when AWS credentials are configured as repository secrets.
Step-by-Step Manual Deploy
Step 1: Build Docker Images
docker build -t serpentstack-backend:latest ./backend
docker build -t serpentstack-frontend:latest ./frontend
Tag with the git SHA for traceability:
GIT_SHA=$(git rev-parse --short HEAD)
docker tag serpentstack-backend:latest serpentstack-backend:$GIT_SHA
docker tag serpentstack-frontend:latest serpentstack-frontend:$GIT_SHA
Step 2: Push to ECR
Authenticate with ECR (replace ACCOUNT_ID and REGION):
aws ecr get-login-password --region $AWS_REGION | \
docker login --username AWS --password-stdin $AWS_ACCOUNT_ID.dkr.ecr.$AWS_REGION.amazonaws.com
Tag and push both images:
docker tag serpentstack-backend:$GIT_SHA $AWS_ACCOUNT_ID.dkr.ecr.$AWS_REGION.amazonaws.com/serpentstack-backend:$GIT_SHA
docker push $AWS_ACCOUNT_ID.dkr.ecr.$AWS_REGION.amazonaws.com/serpentstack-backend:$GIT_SHA
docker tag serpentstack-frontend:$GIT_SHA $AWS_ACCOUNT_ID.dkr.ecr.$AWS_REGION.amazonaws.com/serpentstack-frontend:$GIT_SHA
docker push $AWS_ACCOUNT_ID.dkr.ecr.$AWS_REGION.amazonaws.com/serpentstack-frontend:$GIT_SHA
Step 3: Terraform Plan
cd infra/environments/{env}
terraform init
terraform plan -var="app_image_tag=$GIT_SHA" -out=tfplan
Review the plan output carefully. Look for:
- Resources being destroyed: unexpected destroys indicate a config drift. Investigate before proceeding.
- Security group changes: verify no ports are being opened unintentionally.
- Database modifications: any RDS changes should be treated as high-risk.
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.
- 1mo ago First seen · 134 lines · 43 tokens per session scan A d3ce51340f91
deploy is a skill published in the GitHub repository Benja-Pauls/SerpentStack (2 stars, last pushed 6mo ago), licensed MIT. It adds 43 tokens to every session and 997 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
deployment
Use when taking an app from source to live: choosing the deploy target from requirements (Hetzner+Coolify vs Vercel vs a third), then wiring container → CI → registry → host with build secrets, healthchecks and rollback. NOT one platform's mechanics (that is coolify, vercel, railway, render), NOT the Dockerfile alone…
yaml
Skill "yaml" from dhaupin/vant, covering yaml, when to use, what to do, 1. syntax and 2. anchors.
securing-cloud-and-supply-chain
A guide to protecting cloud infrastructure and the software supply chain, the systems and dependencies used to build and deliver software.
provisioning-infrastructure
Cloud-native infrastructure knowledge reference covering Kubernetes, Helm, Kustomize, Operators, CRDs, GitOps (ArgoCD, Flux), and IaC (Terraform, Pulumi, CDK). Use when provisioning infrastructure, managing clusters, or working with GitOps workflows.
devops
CI/CD, container orchestration, cloud architecture, monitoring, infrastructure security, and platform automation skills. Docker, Kubernetes, Terraform, GitHub Actions. Triggers on: CI/CD, Docker, Kubernetes, Terraform, deploy, monitoring, infra, GitOps, observability, SRE.
devops
Deploy and manage infrastructure with Docker, Kubernetes, CI/CD pipelines, and cloud services. Use when containerizing, deploying, or managing production infrastructure.