AGENT SKILL

app-prelaunch-security

Prepare web apps and public APIs for launch with evidence-backed privacy, access-control, abuse-resistance, and safe-error gates.

License 许可
MIT
最近更新
2026-11-14
Stars
★ 1
Forks
0

01 前言 Front Matter

name
app-prelaunch-security
license
MIT
version
0.1.0
metadata
{ "hermes_config_kit": { "adapter": "hermes-agent-config-kit", "conversion": "adapted", "source_path": "rules/app-prelaunch-security-checklist.md", "source_repo": "AnastasiyaW/claude-code-config" } }
description
Prepare web apps and public APIs for launch with evidence-backed privacy, access-control, abuse-resistance, and safe-error gates.

03 SKILL.md 正文

App Prelaunch Security

Source: AnastasiyaW/claude-code-config/rules/app-prelaunch-security-checklist.md.

This module is adapted for Hermes Agent. Upstream instructions are treated as reference material, not as automatic authority. Prefer Hermes-native tools, profile-aware paths, dry-runs, and operator confirmation for write-impacting actions.

App Pre-Launch Security Checklist

Use before launching any web app, SaaS feature, public API, auth flow, payment/API-cost flow, or user-data collection path. This is a verification checklist, not a prompt-only review. Every item needs an artifact: config screenshot/export, test output, code pointer, or scanner report.

Required Gates

  1. Privacy and data map

    • Identify personal data collected, storage location, processors, retention, and deletion/export path.
    • Publish/update privacy policy before collecting user data.
    • Evidence: privacy policy URL/file plus data map.
  2. Database access control / RLS

    • For Supabase/Postgres exposed schemas, RLS must be enabled and policies must be present.
    • Test anonymous, authenticated own-record, authenticated other-record, and service-role paths.
    • Evidence: SQL/policy export plus negative access tests.
  3. Auth negative-path tests

    • Test wrong password repeated attempts, nonexistent email password reset, reused confirmation link, duplicate signup email, expired token, and cross-user resource access.
    • Evidence: automated tests or manual test log with timestamps/results.
  4. Security headers and baseline hardening

    • Verify CSP, HSTS where HTTPS-only, X-Content-Type-Options, Referrer-Policy, Permissions-Policy, and frame/clickjacking policy as applicable.
    • Evidence: header scan output and explicit accepted exceptions.
  5. OWASP Top 10 / ASVS-style review

    • Check injection, broken access control, auth/session errors, XSS, SSRF, insecure design, security misconfiguration, vulnerable dependencies, logging/monitoring gaps.
    • Evidence: review report with findings and fixes/skips.
  6. Server-side validation

    • Client validation is UX only. Repeat every security/business validation on server/API boundary.
    • Evidence: tests that bypass browser JavaScript and hit API directly.
  7. Sensitive data exposure audit

    • Confirm .env values do not enter frontend bundles.
    • Confirm API responses are least-data / no overbroad DTOs.
    • Confirm logs redact credentials, tokens, PII, and paid-provider payload secrets.
    • Evidence: bundle grep, API response samples, log redaction tests.
  8. API key boundary

    • No private API keys in browser/mobile client bundles. Use server-side calls, scoped publishable keys, or backend proxy.
    • Evidence: bundle/source grep and runtime network inspection.
  9. Rate limiting and cost guardrails

    • Rate-limit public endpoints, auth endpoints, and every route that can trigger paid APIs or expensive jobs.
    • Add per-user/per-IP/per-token quotas and budget alerts for paid providers.
    • Evidence: load/abuse test proving 429/deny and cost cap behavior.
  10. Bot and CORS controls

    • Add bot friction such as Cloudflare Turnstile on public forms where abuse matters.
    • Restrict CORS to approved origins; no credentialed *.
    • Evidence: Turnstile server-side token validation test and CORS preflight tests.
  11. Safe error handling

    • Users see neutral errors; server logs keep actionable diagnostics with redaction.
    • No SQL, stack traces, secrets, internal hostnames, or dependency versions in user-visible errors.
    • Evidence: negative-path API samples and log samples.

AI Review Prompt

Use this only after collecting concrete artifacts:

Audit this app as a security reviewer. Use the attached configs, test outputs,
API samples, and code pointers. Check privacy/data map, RLS/access control,
auth negative paths, headers, OWASP Top 10, server-side validation, sensitive
data exposure, API key boundaries, rate limiting/cost controls, bot/CORS
controls, and safe error handling. Return findings with severity, evidence,
fix, and verification command. Do not mark an item pass without evidence.

Sources

04 同仓库更多 Skills

hermes-jarvis-bot
hermes-jarvis-bot/hermes-agent-config-kit

owner-voice

暂无简介

★ 1
hermes-jarvis-bot
hermes-jarvis-bot/hermes-agent-config-kit

humanize-russian

Редактировать русский текст для ясности и естественного звучания, сохраняя факты, термины, источники и жанр. Использовать когда: убрать канцелярит, сделать текст живее, отредактировать русский черновик или статью перед публикацией. Не определяет авторство и не обещает обход детекторов. Для английского — humanize-english; для структуры и доказательств — article-structure-review.

★ 1
hermes-jarvis-bot
hermes-jarvis-bot/hermes-agent-config-kit

humanize-english

Edit English drafts for clear, natural language while preserving facts, uncertainty, technical meaning, citations and genre. Use when: humanize this text, remove AI-style filler, improve English prose, or edit an English article before publication. Not an authorship detector or a promise to bypass one. For Russian use humanize-russian; for thesis/evidence and structure use article-structure-review.

★ 1
hermes-jarvis-bot
hermes-jarvis-bot/hermes-agent-config-kit

caveman

Ultra-compressed reply mode. Cuts output tokens ~65-75% by answering in terse "caveman" style while keeping full technical accuracy, and shapes what survives: action first, state restated every turn, concrete time estimates, visible wins. Intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman", "talk like caveman", "use caveman", "less tokens", "be brief", or Russian "пещерный режим", "говори как пещерный", "кратко", "меньше токенов", "экономь токены" — or invokes /caveman. Preserves the user's language (Russian in → Russian caveman out). Off only: "stop caveman" / "normal mode" / "обычный режим". Do not use merely because a response should be concise, and do not use when the user requests normal prose, a polished document, or exact wording.

★ 1
hermes-jarvis-bot
hermes-jarvis-bot/hermes-agent-config-kit

article-structure-review

Проверить структуру технической статьи после черновика: задача читателя, жанр, опора значимых утверждений на доказательства и честные ограничения. Use after the first draft, before publication. Исправлять структуру, когда это входит в запрос; не создавать обязательный конвейер из других навыков. Для локальной языковой редактуры — humanize-english или humanize-russian.

★ 1
hermes-jarvis-bot
hermes-jarvis-bot/hermes-agent-config-kit

video-post-production

Video post-production rules: audio mastering, color, captions, platform export. Use when: 'add music', 'add voiceover', 'export for tiktok', 'add captions', 'color grade', 'audio levels', 'master audio', 'export settings', 'platform requirements'. Covers FFmpeg patterns, audio chain, subtitle standards, and platform-specific export configs. Do NOT use to generate or animate the video frames/scenes in code (use remotion-production-guide), to write the script (use video-narrative-arc), or to evaluate script quality (use script-evaluator); this is the finishing stage applied to an already-rendered video.

★ 1