More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    Ship-Safe — Production-Readiness Audit for AI-Built Apps

    1

    Run 151 production-readiness checks across 11 dimensions. Get a 0–100 scorecard, file:line evidence, prioritized fixes, and a SHIP / FIX FIRST / DO NOT SHIP verdict before deploying your AI-built app.

    $9

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Ship-Safe — Production-Readiness Audit for AI-Built Apps

    Ship-Safe — Production-Readiness Audit for AI-Built Apps

    Example session with this skill installed

    Audit sample-app for production readiness using the full 151-check checklist.

    • Read your context and instructions
    • Compiled the ship-safe

    Production-Readiness Report

    Repo: sample-app · Stack: Node.js/Express, raw pg client, Redis dep (unused), Docker · Date: 2026-11-01

    Verdict: DO NOT SHIP

    Overall score: 40 / 100 (capped — critical findings present; raw mean 73)

    One-sentence summary: a working Express CRUD app with SQL injection on multiple routes, committed and hardcoded secrets, plaintext passwords, an unsigned webhook, and no observability, deploy, or recovery story.

    Scorecard

    CategoryScoreFindingsNotes
    Resilience & Timeouts746no timeouts on outbound calls, unbounded in-memory queue
    Data Layer6511N+1, no pool, no migrations, unbounded selects, check-then-insert
    Security019SQLi, secrets in repo/code/Dockerfile/logs, no auth, SSRF, XSS
    Observability7210console.log only, no health endpoint, no metrics
    Deployment709floating deps, no lockfile/CI, secret in image, no rollback
    Scaling & Performance857in-process queue/state, sequential awaits, no cache
    Concurrency738check-then-act races, no distributed-lock story for cron
    Async & Messaging5311unsigned webhook, ack-before-process, no DLQ, in-process cron
    Reliability & DR697no backups, no failover, SPOFs everywhere
    Infrastructure757root container, latest tags, secret in ENV, no IaC
    Deployment & Ops Context6713no LB/proxy/runbook/on-call/postmortem evidence

    Checks skipped as N/A: R3, R4, D11, D12, S12, S17, O8, X3, X4, X5, X7, X10, X11, C4, C5, A4, A13, A14, A15, V5, V8, I5, I7, I9, I10, I12, I13, I15, T4, T9, T14
    Checks UNVERIFIABLE statically: V2 (prove restores work — run a drill), T8 (verify replica config in cloud console), T18 (org-level on-call), S22 (edge config outside repo)

    Findings

    SevCheckFindingEvidenceFix
    criticalS1.env committed with credentialssample-app/.envRemove from history, rotate values, gitignore — security-infrastructure
    criticalS3SQL injection via template literals on 6+ routesserver.js:28, server.js:45, server.js:70, db.js:18, db.js:26, server.js:76Parameterize all queries — application-security
    criticalS7Mutating routes have no auth at allserver.js:60 /admin/reset, server.js:65 /charge, server.js:70 /webhookAuth middleware + authz — application-security
    criticalS9Plaintext password comparisonserver.js:29bcrypt/argon2 + never store plaintext — security-infrastructure
    criticalS20Passwords and Stripe key written to logsserver.js:27, server.js:82Remove; scrub log sinks — observability
    criticalA10Webhook processes body with no signature checkserver.js:70-73Verify HMAC + timestamp, dedupe by event ID — realtime-apis
    criticalI8Secret baked into image via ENVDockerfile:6Runtime secret injection — containers-and-iac
    criticalR1Outbound calls have no timeoutserver.js:50, server.js:66axios.create({ timeout }) + AbortSignal — resilience-patterns
    criticalV1No backup mechanism for the datastoresearched — absentAutomated backups + restore drills — disaster-recovery
    highS2Secrets hardcoded in sourceserver.js:16-17Env/manager injection — security-infrastructure
    highS4ORDER BY built from request inputserver.js:77Allowlist sort columns — application-security
    highS5Reflected XSS — req.query.name into HTMLserver.js:76Encode output / CSP — application-security
    highS8No ownership check on /orders/:idserver.js:44Authorize by user ID — application-security
    highS10JWT secret hardcoded + admin:true for all usersserver.js:31Env secret, least-privilege claims, full validation — security-infrastructure
    highS11Access-Control-Allow-Origin: * + credentialsserver.js:21-22Explicit origin allowlist — application-security
    highS14Server fetches arbitrary user URL (SSRF)server.js:49-50Scheme/host allowlist, block private IPs — application-security
    highS18No rate limiting on /loginsearched — absentLimiter on auth + public mutations — traffic-and-edge
    highS19req.body used unvalidated in queries/logicserver.js throughoutzod/joi schema validation — application-security
    highD1N+1: per-user orders query in a loopserver.js:39-41Eager load/join — database-performance
    highD4Unbounded SELECT * FROM users endpointserver.js:38Limit/paginate — database-performance
    highD6Single ad-hoc client, no pooldb.js:7-12pg.Pool with sizing — database-performance
    highD8Read-modify-write with no transactiondb.js:26-30Atomic UPDATE ... WHERE stock >= $1 or tx — concurrency-and-memory
    highD10No migrations at allsearched — absentVersioned migration tool — versioning-and-migrations
    highO7No health endpointsearched — absent/healthz + /ready — deployment-and-release
    highO12Request data (incl. passwords) loggedserver.js:27Structured logs, PII-safe fields — observability
    highP1Floating deps + no lockfilepackage.json (*, latest, >=)Pin + lockfile — versioning-and-migrations
    highP3No rollback pathsearched — absentArtifact retention + revert plan — deployment-and-release
    highP8No CI — nothing gates deploysno CI config foundCI with test/lint gate — containers-and-iac
    highP10Secret baked into image (ENV STRIPE_KEY)Dockerfile:6Runtime injection — containers-and-iac
    highX1Queue/jobs live in process memoryworker.js:3-8Durable queue — messaging-and-async
    highC1/C2Check-then-act races (createUser, decrementStock)db.js:16-30Unique constraint + atomic statements — concurrency-and-memory
    highA1Consumers process with no dedupeworker.jsIdempotency by message ID — messaging-and-async
    highA2ack() before processingworker.js:12-13Ack after success — messaging-and-async
    highA3No DLQ for poison messagesworker.jsDLQ + redrive — messaging-and-async
    highA8In-process setInterval cron — double-runs per replica, dies on restartworker.js:29External scheduler or leader lock — messaging-and-async
    highA11Webhook dedupe missingserver.js:70Event-ID idempotency — realtime-apis
    highI1Container runs as rootDockerfile — no USERUSER node — containers-and-iac
    highV4Single instance, no failoversearched — absentReplica/standby — disaster-recovery
    highT5Stripe charge never recorded locallyserver.js:65-68Persist + outbox — distributed-systems
    medium+—40 further findings: no CSP, no graceful shutdown, unbounded selects, no eager load, CORS redirect-follow on user URLs, no runbook/on-call/postmortem, node:latest, no .dockerignore, no CDN, SELECT *see checklist—

    Unverifiable — check manually

    CheckWhy static analysis can't decideHow to verify
    V2Can't prove backups restoreRestore drill or PITR in cloud console
    T8Replica config may live outside repoCheck DB provider's console for read replicas
    T18On-call is an org decisionConfirm escalation path exists
    S22Edge/WAF layer outside the repoConfirm CDN/WAF in front of the app

    Top 5 Fixes

    1. Parameterize every SQL query + remove committed/hardcoded secrets — Security, S — both are live compromise vectors today

    Verify webhook signatures + dedupe by event ID — Async, S — forged payment confirmations are free money for an attacker
    3.

    Auth middleware on all mutating routes + ownership checks — Security, M — currently anyone can reset sessions or read any order
    4.

    Add /healthz, structured logging, and a CI test gate — Observability/Deployment, M — you currently can't detect or safely roll back an incident
    5. Timeouts on outbound calls + bounded queue + ack-after-process — Resilience/Async, S — the worker silently loses jobs and hung deps hang requests forever

    What you're doing right

    • Async route handlers throughout — no sync blocking on the request path
    • Single shared DB client rather than connection-per-request (db.js)
    • express.json() default body limit in place
    • Code is small and readable — fixes are all local changes, no architecture surgery needed

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Your app works locally. Is it ready for production?

    Ship-Safe gives your AI agent a structured checklist for reviewing an app before deployment. Built for solo developers, vibe coders, and small teams, it turns a broad “review my code” request into an evidence-backed production-readiness report.

    What you get

    • 151 checks across 11 audit dimensions
    • A 0–100 scorecard
    • A SHIP / FIX FIRST / DO NOT SHIP verdict
    • File:line evidence for findings, or an explicit note when a required artifact is missing
    • Prioritized fixes, including the top five actions to take next
    • Checks marked PASS, FAIL, N/A, or UNVERIFIABLE, so missing evidence is not mistaken for a pass

    What it reviews

    Resilience and timeouts, data access, security, observability, deployment, scaling and performance, concurrency, async processing and messaging, reliability and disaster recovery, infrastructure, and operational readiness.

    It looks for issues such as missing outbound timeouts, unsafe queries, exposed secrets, unbounded retries, missing health checks, and absent rollback procedures.

    How it works

    1. Ask your agent: “Audit my app for production readiness.”
    2. The local prescan gathers signals for 88 grep-able checks, including counter-signals that may indicate an existing control.
    3. Your agent reviews the evidence against the full 151-check checklist.
    4. You receive a scored report with findings, limitations, and prioritized fixes.

    Prescan matches are candidates for review—not confirmed vulnerabilities. The final audit requires agent judgment.

    Included in the pack

    • The Ship-Safe audit skill
    • The 151-check production-readiness checklist
    • A structured report template
    • The local prescan.mjs script
    • 20 supporting engineering topic skills

    Requirements and permissions

    Use with a compatible SKILL.md-capable agent that can read your project files. The deterministic prescan requires Node.js 18+; without Node.js, the agent can review the checklist manually.

    The audit workflow reads repository files and runs the local prescan. It does not require access to external accounts or services. The prescan makes no network calls.

    What it does not do

    Ship-Safe does not automatically patch code, deploy your app, or execute the audited application's code. It is not a penetration test, compliance certification, or guarantee of production safety.

    The prescan is deterministic; the full audit depends on your agent's judgment and the evidence available. Runtime behavior and external controls may require separate verification.

    See the evidence

    The public repository includes audit reports for an intentionally broken demo app and a cleaner reference app, showing both DO NOT SHIP and SHIP outcomes.

    Use the report to decide what to fix before release—not as a substitute for tests, monitoring, or human review.

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Security.

    Static review cannot verify every runtime behavior or external control. Prescan matches require agent judgment, and detection coverage varies by language and framework. A SHIP verdict is not a security certification or guarantee of production safety.

    How to use

    1. 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. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before buying a skill.

    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 15 days ago

    Permissions

    Terminal / Shell
    Read Files
    Listed15 days ago

    What's inside

    Frequently Asked Questions

    Ship-Safe gives your agent a defined 151-check checklist across 11 production-readiness dimensions, an evidence-gathering prescan, and a consistent report format. Findings include file:line evidence or identify missing artifacts. You get a scorecard and prioritized fixes rather than an open-ended review. Results still depend on the agent's judgment and available evidence.

    The pack includes the Ship-Safe audit skill, the 151-check checklist, a report template, the local prescan.mjs script, and 20 supporting engineering topic skills. The prescan gathers signals for 88 grep-able checks; your agent reviews the full checklist and resolves those signals into findings.

    You need a SKILL.md-compatible agent with access to your project files. The optional local prescan also needs terminal access and Node.js 18+. Without Node.js, your agent can review the checklist manually. Detection coverage varies by language and framework; runtime behavior and external controls may need separate verification.

    New in Security