- Home
- Skills
- DevOps & Cloud
- Serverless Framework Check
More screenshots
Works with the AI Agents you already use
Serverless Framework Check
This skill finds those and nine other Serverless Framework mistakes before you deploy, and tells you how to fix each one.
$5
Serverless Framework Check
Example session with this skill installed
Check this project with serverless-framework-check.
- Read your context and instructions
- Compiled the serverless framework check
$ python3 scripts/check_serverless.py examples/risky BLOCK config/prod.yml:4 L04 SECRET_IN_INCLUDED_FILE paymentApiToken: <redacted> (pulled in by serverless.yml) Why: A YAML or JSON file that the Serverless config pulls in with ${file(...)} holds a literal password, token or key, and .gitignore does not exclude it, so it is committed with the project (or will be on the next git add). Safer: Rotate the secret. Add the file to .gitignore and commit an example copy without real values, or move the value to SSM Parameter Store or Secrets Manager and reference it with ${ssm:...}. BLOCK serverless.yml:12 L01 SECRET_IN_ENVIRONMENT BLOCK serverless.yml:19 L03 SECRET_IN_CONFIG BLOCK serverless.yml:24 L02 ADMIN_IAM_PERMISSIONS BLOCK serverless.yml:33 L03 SECRET_IN_CONFIG REVIEW serverless.yml:7 L13 DEPRECATED_RUNTIME REVIEW serverless.yml:9 L15 TIMEOUT_ABOVE_API_LIMIT REVIEW serverless.yml:13 L17 SECRET_RESOLVED_INTO_ENVIRONMENT REVIEW serverless.yml:15 L12 CORS_ALLOWS_ANY_ORIGIN REVIEW serverless.yml:27 L16 BROAD_IAM_PERMISSIONS REVIEW serverless.yml:40 L11 API_ROUTE_WITHOUT_AUTH REVIEW serverless.yml:43 L12 CORS_ALLOWS_ANY_ORIGIN REVIEW serverless.yml:47 L11 API_ROUTE_WITHOUT_AUTH REVIEW serverless.yml:52 L13 DEPRECATED_RUNTIME REVIEW serverless.yml:54 L14 PUBLIC_FUNCTION_URL (Each finding also has Why and Safer lines, as in the first one.) **Verdict:** BLOCK. Checked 2 files, 2 with Serverless content. This is a static check of file text. NOT FLAGGED is not a guarantee.
Connects securely to your tools. The creator never sees your data.
About this skill
A literal DB_PASSWORD under provider.environment ends up in git, in the CloudFormation template Serverless uploads and in the Lambda console, and one IAM statement with Action '*' on Resource '*' gives every function the whole AWS account. This skill finds those and nine other Serverless Framework mistakes before you deploy, and tells you how to fix each one. Your agent runs a scanner on your serverless.yml, serverless.yaml and serverless.json files (stage copies such as serverless.prod.yml too) and on the YAML and JSON files they pull in with ${file(...)}. Paths with ${sls:stage} in them match every stage file, and files your .gitignore excludes are left alone. It knows Serverless variables (${ssm:...}, ${env:...}, ${self:...}), CloudFormation tags such as !Ref and !GetAtt under resources, and the framework's own defaults: cors: true means every origin, url: true means a function URL with no auth, a function without a timeout gets 6 seconds, and a runtime is reported once it is past its AWS deprecation date. It never runs serverless, calls AWS or deploys anything. It returns BLOCK, REVIEW, or NOT FLAGGED, with the file, line, reason, and a safer approach. Secrets are never printed. What it checks BLOCK - L01: passwords, tokens and keys written in provider or function environment (also passwords inside URLs) - L02: IAM statements with Action * (or iam:*) on Resource *, AdministratorAccess and IAMFullAccess - L03: secrets in custom, params, plugin settings, API key values and CloudFormation properties under resources - L04: secrets in files pulled in with ${file(...)} that .gitignore does not exclude REVIEW - L11: http and httpApi routes without an authorizer - L12: CORS open to every origin on http events, HTTP APIs and function URLs - L13: Lambda runtimes past their AWS deprecation date (nodejs18.x, nodejs20.x, python3.9 and others) - L14: function URLs with no auth (url: true) - L15: timeouts longer than API Gateway waits (29 seconds for REST APIs, 30 for HTTP APIs) - L16: whole-service IAM wildcards such as dynamodb:* on *, iam:PassRole on *, NotAction and PowerUserAccess - L17: secrets copied from SSM or the environment into Lambda environment variables at deploy time What's included - The scanner (Python 3.9+, standard library only) - A rules guide with the reason and safer approach for each rule - A risky and a safe example service, and the real report the scanner produces on the risky one Limits It reads your config files as written. serverless.ts and serverless.js configs, values passed at deploy time (--param, environment variables, SSM contents) and plugin defaults are not evaluated, and functions defined in files pulled in with ${file(...)} are checked for secrets only. Buckets, security groups and databases under resources need a CloudFormation checker. The runtime deprecation dates come from the AWS Lambda runtimes page as of November 2026; AWS calls them projected dates that may change. NOT FLAGGED is not a guarantee.
Static check of Serverless config text. serverless.ts and serverless.js configs, deploy-time values and plugin behaviour are not evaluated; CloudFormation resources are checked for secrets and IAM only. NOT FLAGGED is not a guarantee.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 5 days ago
Permissions
Runs one local Python script in the terminal. It reads your project's files, writes nothing, and makes no network calls. The example service includes clearly fake, inert passwords and tokens (not-a-real-..., NOTREAL) for the scanner to find. Nothing is deployed.