Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Web App Hygiene Audit

    1

    A meticulous, breadth-first review of a web project that surfaces **obvious holes, misconfigurations and sloppy implementations of core components** - not exotic exploit chains.

    $6

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Web App Hygiene Audit

    Web App Hygiene Audit

    Example session with this skill installed

    Audit this repo before we launch. It's a Django/DRF backend with a Next.js frontend, Postgres, Stripe checkout and S3 uploads. Two test accounts are available on staging. Focus on access control on the org APIs and the checkout flow.

    • Read your context and instructions
    • Compiled the web app hygiene
    • Generated the data export

    Summary

    Depth: standard. Stack: Django 4.2 + DRF (api/) and Next.js 14 (web/), audited per pack. Coverage: 132 of 146 applicable checks answered (90%) - 14 UNVERIFIED need staging runtime access.

    Top findings

    SevIDFindingEvidence
    CriticalAC-04Org endpoints lack tenant predicate: any authenticated user can read/write any org's objectsapi/views/org.py:38
    HighAC-02Checkout price accepted from client body and trusted server-sideapi/serializers/checkout.py:22
    HighSEC-03Stripe webhook signature not verified; replay possibleapi/views/webhooks.py:11
    MediumINJ-05Upload filename joined into filesystem path without sanitizationapi/services/files.py:57
    MediumQ-BLOCKERConcurrent coupon redemption can double-apply discount (no select_for_update)api/models/coupon.py:81

    Coverage ledger

    • Generic checklist: 98 checks - auth 12/12, access 9/11, injection 14/14, browser/http 16/18, config/secrets 15/15, robustness 21/22 answered
    • django-drf pack: 30 checks answered; nextjs pack: 22 answered; boundary stated in report appendix

    Next steps

    1. Add org membership predicate to every org queryset (canonical fix in report F-1)
    2. Compute price server-side from product IDs; verify webhook signatures
    3. Hand the 14 UNVERIFIED items to a human with the staging instructions in the report

    Full report: audit/AUDIT-REPORT.md - ledger: audit/coverage.csv

    coverage.csv

    CSV · data export

    Generated

    Example file from a real run - the skill writes it into your workspace.

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

    About this skill

    A meticulous, breadth-first review of a web project that surfaces obvious holes, misconfigurations and sloppy implementations of core components - not exotic exploit chains. It reads like a nitpicky senior appsec + backend reviewer: nothing is safe until it is seen in code, config, or an actual response.

    What you get

    • audit/AUDIT-REPORT.md - summary, fix-first list, severity-ranked findings with exact file:line evidence, coverage ledger and an unverified list
    • coverage.csv - one row per check ID with status (PASS / FAIL / N/A / UNKNOWN) and evidence location
    • findings.json + evidence/ - machine-readable findings and redacted raw evidence for tracking and CI
    • Security findings (Critical to Info) separated from quality findings (Q-BLOCKER / Q-MAJOR / Q-MINOR)

    How it works

    1. Inventory & trust map - routes, forms, roles, jobs, webhooks, storage and admin surfaces, plus a stack fingerprint and trust-boundary map
    2. Stack pack - loads a framework pack before the sweep: Next.js/React, Express/Fastify/NestJS, Django/DRF, Laravel, FastAPI or WordPress/WooCommerce, each with idiomatic greps and a "do not flag" list that prevents false positives
    3. Checklist sweep - auth, sessions, access control/IDOR, input validation, injection sinks, XSS/CSRF/CORS, headers, secrets, debug endpoints, uploads, SSRF, caching, data layer, concurrency, business logic - every check answered, never silently skipped
    4. Per-endpoint cards - 12 questions per endpoint: authn actually applied, ownership predicates, mass assignment, validation, sinks, encoding, rate limits, idempotency, failure modes, caching, logging, contract match
    5. Core-flow edge matrix - 10 edge cases per critical flow (signup, login, reset, checkout, upload, admin): duplicates, concurrency, replays, boundaries - where double charges and lost updates actually live
    6. Report - dedupe by root cause, false-positive guards applied, severity + confidence, partial coverage stated explicitly

    Guardrails

    Non-intrusive by design: no exploitation, no brute force, no attack payloads, no destructive or state-changing requests outside a disposable test environment. Runtime probes are limited to read-only GET/HEAD/OPTIONS at max 2 requests per second, with benign markers and owned test accounts only. Secrets and PII are redacted. Intrusive checks are marked UNVERIFIED with exact instructions for a human instead of performed. Your code is not modified - patches are proposed, applied only if you ask.

    Requirements

    • Repo access to the web project (white-box mode needs nothing else)
    • curl for the optional grey-box probe script
    • Optional: a staging URL and two owned test accounts for runtime confirmation

    Known limitations

    • Static-first: most checks are answered from code; runtime observation confirms but never replaces reading the code
    • Black-box mode (URL only) has limited coverage, stated explicitly in the report
    • No-match stacks (Rails, Spring, Go...) get the generic checklist with reduced precision, honestly noted
    • Finds obvious holes and broken core components - it is not an exhaustive exploitation exercise

    Not a penetration test: no exploitation, brute force, fuzzing or destructive requests - intrusive checks are marked UNVERIFIED with human instructions instead of performed. Black-box mode (URL only) has limited coverage, stated in the report. Runtime probes obey a fixed budget: read-only GET/HEAD/OPTIONS, max 2 requests per second and about 200 per run. Stack packs cover Next.js, Node, Django, Laravel, FastAPI and WordPress; other stacks get the generic checklist with reduced precision, honestly noted. The audit does not modify your project - patches are proposed in the report and applied only if you ask.

    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 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 today

    Requires

    Python
    curl
    Repo access to the web project

    Permissions

    Terminal / Shell
    Network Access
    Read Files
    Write Files

    Allowed Hosts

    staging.example.com
    host

    File Scopes

    audit/**

    White-box mode only reads your repo and writes the report to ./audit/. Grey-box mode additionally runs passive_probe.sh: low-rate read-only GET/HEAD/OPTIONS requests (max 2 req/s, about 200 per run) against a host you own, plus at most one login to an owned test account. No exploitation, no payloads, no brute force.

    Listedtoday

    What's inside

    Frequently Asked Questions

    This skill performs a 'pedantic' audit that scans for logic-level flaws like Insecure Direct Object References (IDOR) and business logic race conditions, which standard linters typically miss. It uses framework-specific 'packs' to understand the context of your code rather than just flagging syntax errors.

    The skill is optimized for modern full-stack environments including Next.js, Node.js (Express/NestJS/Fastify), Django, Laravel, FastAPI, and WordPress/WooCommerce. It automatically detects your framework during the Inventory phase to apply the correct security rules.

    No, the skill focuses on static code analysis and configuration review, though it can perform optional passive runtime probes via GET/HEAD requests. It is designed to be safe for development environments and does not perform destructive actions, brute force, or active exploitation.

    The primary output is a detailed `AUDIT-REPORT.md` file saved to your directory, featuring a localized findings ledger with severity levels, exact file:line references, and remediation suggestions. This allows you to track and fix vulnerabilities directly within your workflow.

    Yes, you can configure the audit to target specific routes, roles, or directories. This is particularly useful for 'Pre-release hardening' where you might only want to audit a newly developed feature or a specific business-critical flow like a checkout system.

    New in Security