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 J-Pster/Psters_AI_Workflow --skill deploy-lambdagit clone --depth 1 https://github.com/J-Pster/Psters_AI_WorkflowWrote 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/j-pster/psters_ai_workflow/deploy-lambda)<a href="https://agentmods.dev/skills/j-pster/psters_ai_workflow/deploy-lambda"><img src="https://agentmods.dev/badge/skills/j-pster/psters_ai_workflow/deploy-lambda/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/j-pster/psters_ai_workflow/deploy-lambda"><img src="https://agentmods.dev/badge/skills/j-pster/psters_ai_workflow/deploy-lambda.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.00041 | $0.00772 |
| Opus 5.5 | $0.00016 | $0.00309 |
| Sonnet 5.5 | $0.00008 | $0.00154 |
| Haiku 4.5 | $0.00004 | $0.00077 |
Grade A, and why
aws-lambda-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 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.
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.
How it starts
The opening of the file, as written. The whole thing — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AWS Lambda Deploy
Lambdas are deployed only via the project's deploy scripts, using AWS CLI. No CDK deploy, no IAC apply.
Step 1: Detect guaranteed scripts before deploy
From the Lambda repo root, inspect ./scripts/ for guaranteed deploy scripts.
Preferred script names:
- Single function:
deploy-lambda-guaranteed.sh - All functions:
deploy-all-lambdas-guaranteed.sh
Accept equivalent variants only if they are clearly the same guaranteed flow.
Rule: Use the guaranteed deploy scripts
Each Lambda repo that has deploy scripts must use them:
- Single function:
./scripts/deploy-lambda-guaranteed.sh <lambda-name> [--profile PROFILE] [--region REGION] - All functions in repo:
./scripts/deploy-all-lambdas-guaranteed.sh [--profile PROFILE] [--region REGION]
Script names may vary by repo (e.g. deploy-lambda-guaranteed.sh, deploy-all-lambdas-guaranteed.sh). Look in that repo's scripts/ folder.
Step 2: Mandatory fallback when scripts do not exist
If no guaranteed deploy script exists, do not deploy manually.
Instead, pause and ask the user before creating defaults. Use this message pattern:
No guaranteed deploy script was found in ./scripts. I suggest creating standard deploy scripts now (single Lambda and deploy-all), based on the plugin defaults. Should I create them for this repo?
If the user approves, create these files in the target Lambda repo:
./scripts/deploy-lambda-guaranteed.sh./scripts/deploy-all-lambdas-guaranteed.sh
Template source (inside plugin):
assets/lambda-deploy/deploy-lambda-guaranteed.template.shassets/lambda-deploy/deploy-all-lambdas-guaranteed.template.sh
After creation:
- Make scripts executable (
chmod +x). - Review placeholders/TODO values with the user.
- Run deploy through the guaranteed script only.
Prerequisite: AWS SSO login
Before any AWS CLI command (including deploy):
aws sso login --profile <aws-profile>
Replace <aws-profile> with the project's AWS profile. If you skip this, deploy will fail with credential/session errors.
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 · 83 lines · 41 tokens per session scan A 050bf2129ebb
aws-lambda-deploy is a skill published in the GitHub repository J-Pster/Psters_AI_Workflow (289 stars, last pushed 7mo ago), licensed MIT. It adds 41 tokens to every session and 772 once invoked, about $0.0002 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-30.
Other skills, from other repositories
flow-nexus-swarm
Cloud-based AI swarm deployment and event-driven workflow automation with Flow Nexus platform.
infrastructure
A guide for cloud-native infrastructure: software and configuration used to run applications in containers and manage cloud resources. It covers Kubernetes, Helm, Kustomize, GitOps tools such as ArgoCD and Flux, and infrastructure-as-code tools such as Terraform and Pulumi.
remote-compute-modal
Run GPU jobs on the user's own Modal account via host.compute.create('byoc:modal', ...). Covers the create→submit→waitfornotification flow, the computeprovider kernel for env setup, image/volume resolution, and the two approval cards. Load once you've decided to dispatch to Modal.
compute-env-setup
Set up a compute environment on a remote provider so Claude Science jobs can run there. Covers direct SSH/conda hosts, Slurm clusters, container-via-bridge runners, and managed-API providers (Modal, GCP, RunPod). Use when standing up a new provider, porting an env to a different backend, adding a tool that needs its…
managed-model-endpoints
Register a model service in the managed family — a local model server container the daemon starts/stops on demand, or a remote upstream model API (https). Read the runbook, allocate a port (local only), compose idempotent start/stop scripts (local only), register once. Load when the user wants a model service…
vs-project
Create Viking web projects, start and verify a local preview, or deploy a generated project to Volcengine IGA Pages when explicitly requested. Includes agent-guided feature, eligible application, dataset, scene, and authentication choices. Use only after confirming the installed CLI exposes vs project; otherwise stop…