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/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/commands/j-pster/psters_ai_workflow/pwf-aws-lambda-deploy)<a href="https://agentmods.dev/commands/j-pster/psters_ai_workflow/pwf-aws-lambda-deploy"><img src="https://agentmods.dev/badge/commands/j-pster/psters_ai_workflow/pwf-aws-lambda-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/commands/j-pster/psters_ai_workflow/pwf-aws-lambda-deploy"><img src="https://agentmods.dev/badge/commands/j-pster/psters_ai_workflow/pwf-aws-lambda-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.00869 |
| Opus 5.5 | $0.00017 | $0.00348 |
| Sonnet 5.5 | $0.00009 | $0.00174 |
| Haiku 4.5 | $0.00004 | $0.00087 |
Grade A, and why
pwf-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 2mo 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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Deploy AWS Lambda with Guaranteed Scripts
Use this command to deploy Lambda changes safely through project-approved deploy scripts (default AWS CLI flow, no CDK/IaC deploy path unless project overrides allow).
Operational guardrails source: rules/operational-guardrails.mdc
Optional project override source: docs/workflow/operational-overrides.md
Step 1: Detect script availability
From the target Lambda repo root, inspect ./scripts/ and find the guaranteed deploy script(s):
deploy-lambda-guaranteed.shdeploy-all-lambdas-guaranteed.sh
Do not continue until script availability is clear.
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: If scripts are missing, suggest bootstrap first
If no guaranteed deploy script exists, stop deploy execution and ask for user approval to scaffold defaults.
Use this prompt:
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 approved, create in the target repo:
./scripts/deploy-lambda-guaranteed.sh./scripts/deploy-all-lambdas-guaranteed.sh
Bootstrap templates:
assets/lambda-deploy/deploy-lambda-guaranteed.template.shassets/lambda-deploy/deploy-all-lambdas-guaranteed.template.sh
Then:
chmod +xboth scripts.- Validate placeholder values and lambda list with the user.
- Execute deploy using the guaranteed script path only.
Prerequisite (default policy): AWS SSO login
Before AWS CLI command(s), run:
aws sso login --profile <aws-profile>
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.
- 2mo ago First seen · 93 lines · 43 tokens per session scan A b0e0a82e49eb
pwf-aws-lambda-deploy is a command published in the GitHub repository J-Pster/Psters_AI_Workflow (289 stars, last pushed 7mo ago), licensed MIT. It adds 43 tokens to every session and 869 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 commands, from other repositories
deploy
Deploy a frontend (React, Next.js, or static HTML) to a live URL on Butterbase.
link-project
Set up symlink from repo to vault folder.
env
Manage Vercel environment variables. Commands include list, pull, add, remove, and diff. Use to sync environment variables between Vercel and your local development environment.
firebase-publish
Create or reuse a Firebase project, configure Hosting, and deploy the current static site. Never deletes.
scan
Scan AWS account for cost optimization.
migration
Generate Prisma database migration.