[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7ARVBHVCB6E84HK22EEJNPC":3,"skill-same:01M7ARVBHVCB6E84HK22EEJNPC":54},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":29,"install":30,"resources":43},"01M7ARVBHVCB6E84HK22EEJNPC","backend-security-audit",null,"Defensive backend security review for source code, API servers, auth flows, database access, dependency configuration, secrets handling, file uploads, webhooks, background jobs, and deployment settings. Use when Codex is asked to audit, review, deep research, harden, or find vulnerabilities in a user's own backend or authorized codebase, and to report findings before making fixes.","ham-zax\u002Fwebharness","ham-zax","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F81289670?v=4","01M7AQGHAV4TPYCAZY23S7SVSC","Ahmed Hamza","01M7AQGHBCFJYE7KWZ34W9HEGH",0,"MIT","https:\u002F\u002Fgithub.com\u002Fham-zax\u002Fwebharness\u002Fblob\u002Fmain\u002Fskill-library\u002Fpacks\u002Fsentry\u002Fbackend-security-audit\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: backend-security-audit\ndescription: Defensive backend security review for source code, API servers, auth flows, database access, dependency configuration, secrets handling, file uploads, webhooks, background jobs, and deployment settings. Use when Codex is asked to audit, review, deep research, harden, or find vulnerabilities in a user's own backend or authorized codebase, and to report findings before making fixes.\n---\n\n# Backend Security Audit\n\n## Overview\n\nPerform a defensive, evidence-led backend security audit. Find as many real vulnerabilities and risky patterns as possible, report them clearly to the user, then ask whether to implement fixes.\n\nUse this only on systems the user owns or is authorized to assess. Do not provide exploit payloads, attack playbooks, or instructions for compromising third-party systems.\n\n## Audit Workflow\n\n1. Establish scope from the repository:\n   - Identify backend entry points, framework, package manager, runtime, API routes, middleware, auth\u002Fsession libraries, database layer, background jobs, file storage, webhook handlers, and deployment files.\n   - Read project docs, environment examples, schema files, route definitions, middleware, and dependency manifests before judging individual files.\n   - Prefer `rg` and `rg --files` for discovery.\n\n2. Load the checklist when needed:\n   - Read `references\u002Faudit-checklist.md` before the detailed pass, or when the backend uses unfamiliar patterns.\n   - Use it as coverage guidance, not as a substitute for code-specific reasoning.\n\n3. Trace trust boundaries:\n   - For each external input path, follow data from request, queue message, webhook, file upload, CLI job, or third-party callback into validation, authorization, persistence, side effects, and responses.\n   - Pay special attention to paths that cross user, tenant, organization, admin, payment, or internal-service boundaries.\n\n4. Verify findings against code:\n   - Report a finding only when there is concrete evidence in the code or configuration.\n   - Include file references and the relevant behavior. Avoid vague claims like \"may be vulnerable\" unless the uncertainty is explicitly explained.\n   - Separate confirmed vulnerabilities from hardening recommendations.\n\n5. Assess severity:\n   - `Critical`: likely account takeover, remote code execution, credential exposure, broad data breach, auth bypass, or payment\u002Fsecurity boundary compromise.\n   - `High`: unauthorized access\u002Fmodification of sensitive data, tenant isolation failure, privilege escalation, serious injection, exploitable SSRF, or dangerous file handling.\n   - `Medium`: meaningful security weakness requiring specific conditions, missing defense-in-depth around sensitive paths, weak session\u002Fcookie\u002FCORS\u002FCSRF posture, dependency risk with reachable impact.\n   - `Low`: limited-impact leak, minor misconfiguration, logging issue, weak validation with constrained impact, or maintainability issue that increases security risk.\n\n6. Report before fixing:\n   - Lead with findings ordered by severity.\n   - For each finding include: severity, title, affected file(s), evidence, impact, likely exploit scenario in defensive terms, and recommended fix.\n   - Include \"No finding\" notes only for important areas that were checked and looked safe.\n   - End by asking whether the user wants fixes implemented.\n\n## Review Priorities\n\nCover these areas during the audit:\n\n- Authentication: login, registration, password reset, email verification, OAuth callbacks, MFA, session creation, session rotation, logout, cookies, JWTs, API keys.\n- Authorization: object ownership, tenant\u002Forg membership, role checks, admin checks, horizontal\u002Fvertical privilege escalation, IDOR, route-level and service-level enforcement.\n- Input handling: schema validation, type coercion, parser limits, unsafe deserialization, query parameters, JSON bodies, multipart uploads, path parameters.\n- Injection: SQL\u002FNoSQL, command, template, LDAP, ORM raw queries, unsafe dynamic code, shell-outs, path traversal.\n- Data exposure: sensitive fields in API responses, logs, errors, caches, analytics, client bundles, OpenAPI specs, debug endpoints.\n- Secrets: committed credentials, weak env handling, secret logging, token storage, overbroad service keys.\n- Web security: CORS, CSRF, cookies, redirects, host header trust, rate limits, request size limits, security headers where backend-controlled.\n- File and media handling: upload validation, MIME\u002Fcontent sniffing, storage permissions, filename\u002Fpath use, malware scanning expectations, signed URL scope.\n- SSRF and outbound requests: user-controlled URLs, metadata services, internal host access, redirect following, DNS\u002FIP allowlists.\n- Webhooks and integrations: signature verification, replay protection, idempotency, event trust, payment state transitions.\n- Dependencies and supply chain: vulnerable packages, unsafe lifecycle scripts, lockfile drift, unmaintained auth\u002Fsecurity libraries.\n- Deployment: production debug flags, database\u002Fnetwork exposure, TLS assumptions, container permissions, cloud IAM, public buckets.\n\n## Output Format\n\nUse this structure:\n\n```markdown\n**Findings**\n1. [Severity] Title\n   - Evidence: `path\u002Fto\u002Ffile.ext:line` and concise code behavior.\n   - Impact: What can go wrong.\n   - Scenario: Defensive abuse case, without weaponized payloads.\n   - Fix: Specific implementation direction.\n\n**Checked**\n- Important surfaces reviewed with no confirmed issue.\n\n**Next**\nShould I implement the fixes for these findings?\n```\n\nIf no vulnerabilities are found, say that clearly, summarize the reviewed surfaces, note residual risk, and offer targeted hardening or tests.\n","# Backend Security Audit\n\n## Overview\n\nPerform a defensive, evidence-led backend security audit. Find as many real vulnerabilities and risky patterns as possible, report them clearly to the user, then ask whether to implement fixes.\n\nUse this only on systems the user owns or is authorized to assess. Do not provide exploit payloads, attack playbooks, or instructions for compromising third-party systems.\n\n## Audit Workflow\n\n1. Establish scope from the repository:\n   - Identify backend entry points, framework, package manager, runtime, API routes, middleware, auth\u002Fsession libraries, database layer, background jobs, file storage, webhook handlers, and deployment files.\n   - Read project docs, environment examples, schema files, route definitions, middleware, and dependency manifests before judging individual files.\n   - Prefer `rg` and `rg --files` for discovery.\n\n2. Load the checklist when needed:\n   - Read `references\u002Faudit-checklist.md` before the detailed pass, or when the backend uses unfamiliar patterns.\n   - Use it as coverage guidance, not as a substitute for code-specific reasoning.\n\n3. Trace trust boundaries:\n   - For each external input path, follow data from request, queue message, webhook, file upload, CLI job, or third-party callback into validation, authorization, persistence, side effects, and responses.\n   - Pay special attention to paths that cross user, tenant, organization, admin, payment, or internal-service boundaries.\n\n4. Verify findings against code:\n   - Report a finding only when there is concrete evidence in the code or configuration.\n   - Include file references and the relevant behavior. Avoid vague claims like \"may be vulnerable\" unless the uncertainty is explicitly explained.\n   - Separate confirmed vulnerabilities from hardening recommendations.\n\n5. Assess severity:\n   - `Critical`: likely account takeover, remote code execution, credential exposure, broad data breach, auth bypass, or payment\u002Fsecurity boundary compromise.\n   - `High`: unauthorized access\u002Fmodification of sensitive data, tenant isolation failure, privilege escalation, serious injection, exploitable SSRF, or dangerous file handling.\n   - `Medium`: meaningful security weakness requiring specific conditions, missing defense-in-depth around sensitive paths, weak session\u002Fcookie\u002FCORS\u002FCSRF posture, dependency risk with reachable impact.\n   - `Low`: limited-impact leak, minor misconfiguration, logging issue, weak validation with constrained impact, or maintainability issue that increases security risk.\n\n6. Report before fixing:\n   - Lead with findings ordered by severity.\n   - For each finding include: severity, title, affected file(s), evidence, impact, likely exploit scenario in defensive terms, and recommended fix.\n   - Include \"No finding\" notes only for important areas that were checked and looked safe.\n   - End by asking whether the user wants fixes implemented.\n\n## Review Priorities\n\nCover these areas during the audit:\n\n- Authentication: login, registration, password reset, email verification, OAuth callbacks, MFA, session creation, session rotation, logout, cookies, JWTs, API keys.\n- Authorization: object ownership, tenant\u002Forg membership, role checks, admin checks, horizontal\u002Fvertical privilege escalation, IDOR, route-level and service-level enforcement.\n- Input handling: schema validation, type coercion, parser limits, unsafe deserialization, query parameters, JSON bodies, multipart uploads, path parameters.\n- Injection: SQL\u002FNoSQL, command, template, LDAP, ORM raw queries, unsafe dynamic code, shell-outs, path traversal.\n- Data exposure: sensitive fields in API responses, logs, errors, caches, analytics, client bundles, OpenAPI specs, debug endpoints.\n- Secrets: committed credentials, weak env handling, secret logging, token storage, overbroad service keys.\n- Web security: CORS, CSRF, cookies, redirects, host header trust, rate limits, request size limits, security headers where backend-controlled.\n- File and media handling: upload validation, MIME\u002Fcontent sniffing, storage permissions, filename\u002Fpath use, malware scanning expectations, signed URL scope.\n- SSRF and outbound requests: user-controlled URLs, metadata services, internal host access, redirect following, DNS\u002FIP allowlists.\n- Webhooks and integrations: signature verification, replay protection, idempotency, event trust, payment state transitions.\n- Dependencies and supply chain: vulnerable packages, unsafe lifecycle scripts, lockfile drift, unmaintained auth\u002Fsecurity libraries.\n- Deployment: production debug flags, database\u002Fnetwork exposure, TLS assumptions, container permissions, cloud IAM, public buckets.\n\n## Output Format\n\nUse this structure:\n\n```markdown\n**Findings**\n1. [Severity] Title\n   - Evidence: `path\u002Fto\u002Ffile.ext:line` and concise code behavior.\n   - Impact: What can go wrong.\n   - Scenario: Defensive abuse case, without weaponized payloads.\n   - Fix: Specific implementation direction.\n\n**Checked**\n- Important surfaces reviewed with no confirmed issue.\n\n**Next**\nShould I implement the fixes for these findings?\n```\n\nIf no vulnerabilities are found, say that clearly, summarize the reviewed surfaces, note residual risk, and offer targeted hardening or tests.\n",{"name":5,"description":7},"main","59ee67804bc373a9bd079a3a27f47277a6efe564","skill-library\u002Fpacks\u002Fsentry\u002Fbackend-security-audit","https:\u002F\u002Fgithub.com\u002Fham-zax\u002Fwebharness","https:\u002F\u002Fgithub.com\u002Fham-zax","2026-11-15 01:18:51",{"source":8,"skillName":5,"commands":31,"prompt":41,"zipAvailable":42},[32,35,38],{"tool":33,"command":34},"npx","npx skills add ham-zax\u002Fwebharness --skill backend-security-audit",{"tool":36,"command":37},"bunx","bunx skills add ham-zax\u002Fwebharness --skill backend-security-audit",{"tool":39,"command":40},"pnpm","pnpm dlx skills add ham-zax\u002Fwebharness --skill backend-security-audit","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fham-zax\u002Fwebharness\u002Fblob\u002Fmain\u002Fskill-library\u002Fpacks\u002Fsentry\u002Fbackend-security-audit\u002FSKILL.md",true,[44,50],{"path":45,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":48,"sourceHtmlUrl":49},"agents\u002Fopenai.yaml","REFERENCE","参考文档",252,"https:\u002F\u002Fgithub.com\u002Fham-zax\u002Fwebharness\u002Fblob\u002Fmain\u002Fskill-library\u002Fpacks\u002Fsentry\u002Fbackend-security-audit\u002Fagents\u002Fopenai.yaml",{"path":51,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":52,"sourceHtmlUrl":53},"references\u002Faudit-checklist.md",3875,"https:\u002F\u002Fgithub.com\u002Fham-zax\u002Fwebharness\u002Fblob\u002Fmain\u002Fskill-library\u002Fpacks\u002Fsentry\u002Fbackend-security-audit\u002Freferences\u002Faudit-checklist.md",[55,62,69,76,85,92],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":19},"01M7AS6BAQQ2WQJYS3WBNJPB2G","x-content","Create, rewrite, critique, select formats for, discover opportunities for, and learn from X\u002FTwitter content and X Articles for a technical AI-native developer\u002Fbuilder account. Use when turning ideas, source posts, releases, benchmarks, results, conversations, authenticated For You or creator-watch opportunities, or project evidence into an Original, Quote, Thread, Reply, or Article; reviewing article titles\u002Foutlines\u002Fvisual briefs\u002Flaunch hooks; improving drafts; choosing additive contributions from live X context; or learning from own-account outcomes. Own content intelligence only; compose with agent-browser for live X state and Growth OS for discovery provenance, approvals, measurement, and publication.","https:\u002F\u002Fgithub.com\u002Fham-zax\u002Fwebharness\u002Fblob\u002Fmain\u002Fskills\u002Fx-content\u002FSKILL.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M7AS66FXQR8FEQYW8G8RJB2N","writing-plans","Create detailed implementation plans for multi-step software work before editing code. Use when requirements or a specification must become concrete file-level tasks, interfaces, acceptance criteria, risks, rollout, or explicitly required validation. Default to no test creation, test modification, test execution, TDD, regression-test, or coverage work unless the user, authoritative specification, or mandatory repository policy explicitly requires testing.","https:\u002F\u002Fgithub.com\u002Fham-zax\u002Fwebharness\u002Fblob\u002Fmain\u002Fskills\u002Fwriting-plans\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M7AS5ZCJX21NF2RESA2QDWPP","systematic-debugging","Root-cause debugging for concrete technical failures including bugs, failing builds or tests, integration issues, performance regressions, and unexpected behavior. Use before proposing or implementing a repair when diagnosis is required. Reproduce the symptom, trace the responsible owner, maintain one leading causal hypothesis, and falsify it with the smallest direct evidence. Compose with Causal Coding for source mutation; testing is opt-in and requires independent authorization.","https:\u002F\u002Fgithub.com\u002Fham-zax\u002Fwebharness\u002Fblob\u002Fmain\u002Fskills\u002Fsystematic-debugging\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":80,"licenseFileUrl":81,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":19},"01M7AS548FQ63SAB9G0X81VPGJ","skill-creator","Guide for creating and updating high-quality skills by translating workflows, conventions, and reusable processes into well-structured skills. Includes context, use case examples and spec for skills. Use this skill whenever a user asks to create, update, edit, improve, package, or troubleshoot a skill, and also for conversational questions about skills in ChatGPT (e.g., \"What are skills?\", \"What can I use skills for?\", \"What are the best skill use cases for me?\", \"Where can I find my skills?\").","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fham-zax\u002Fwebharness\u002Fblob\u002Fmain\u002Fskills\u002Fskill-creator\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fham-zax\u002Fwebharness\u002Fblob\u002Fmain\u002Fskills\u002Fskill-creator\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M7AS4XD121Q85Y06EXRGYS4F","reflexion","Self-refinement, multi-perspective critique, verification, and durable lesson curation adapted from NeoLabHQ Reflexion. Use when the user asks to reflect, self-review, critique, double-check, verify and improve prior work, run a rigorous review, memorize lessons, or says \"then reflect\" after a coding, analysis, or writing task. Supports repository-aware evidence gathering and works without subagents or Claude hooks.","https:\u002F\u002Fgithub.com\u002Fham-zax\u002Fwebharness\u002Fblob\u002Fmain\u002Fskills\u002Freflexion\u002FSKILL.md",[],[],{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":19},"01M7AS4RN5TYMA4P6SK6K7NVSR","ponytail","Enforce Ponytail's lazy-senior-developer approach for coding, fixing, refactoring, design, dependency choices, and explicit Ponytail modes such as review, audit, debt, gain, and help. Prefer YAGNI, existing code, standard library, native platform features, existing dependencies, low reader load, and the smallest correct diff. For source mutation, keep Causal Coding authoritative for scope, testing authorization, verification cadence, and stopping. On connected WSL\u002FLinux targets, compose with MCP Harness Router and use `wsl-web-harness` for authoritative repository work.","https:\u002F\u002Fgithub.com\u002Fham-zax\u002Fwebharness\u002Fblob\u002Fmain\u002Fskills\u002Fponytail\u002FSKILL.md",[],[]]