[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MG98HH0H2YA16T17Q3AKWH":3,"skill-same:01M6MG98HH0H2YA16T17Q3AKWH":67},{"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":37,"linkOnly":38,"markdownContent":39,"markdownBody":40,"frontMatter":41,"refName":43,"commitSha":44,"skillDirectory":45,"forksCount":46,"repositoryHtmlUrl":47,"repositoryHomepageUrl":48,"ownerHtmlUrl":49,"ownerBlogUrl":50,"ownerDescription":51,"updatedAt":52,"install":53,"resources":66},"01M6MG98HH0H2YA16T17Q3AKWH","secure",null,"Security review checklist with optional engagement scoping. Use when auth, DB, API, infra, or secrets code is touched.","hashgraph-online\u002Fawesome-codex-plugins","hashgraph-online","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160371962?v=4","01M6CNB6NRJVNNGN14TR01Q6D3","HOL (Hashgraph Online)","01M6JT1HSKKG9V68KQAQGBA7XP",1575,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fepicsagas\u002Fepic-harness\u002Fskills\u002Fsecure\u002FSKILL.md",[],[5,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36],"secrets","when","with","db","control","infra","checklist","engagement","use","scoping","review","api","Safety","review checklist","code","security review","auth","security","2026-11-10 10:12:30",false,"---\nname: secure\ndimension: control_and_safety\ndescription: \"Security review checklist with optional engagement scoping. Use when auth, DB, API, infra, or secrets code is touched.\"\n---\n\n# Secure — Security Review\n\n## Iron Law\n\nNO DEPLOYMENT WITHOUT SECURITY REVIEW OF ALL CHANGED FILES. Every code change is a potential attack vector.\n\n## Process\n\n### Step 0: Load Engagement Context (Optional)\n\nCheck for engagement scoping:\n```bash\ncat .harness\u002Fengagement.md 2>\u002Fdev\u002Fnull\n```\n\nIf `.harness\u002Fengagement.md` exists:\n1. Parse the **Scope**, **Constraints**, and **Exclusions** sections\n2. Restrict security checks to in-scope components\n3. Apply rules of engagement (method, rate limits, no-exfil rules)\n4. Skip findings matching exclusion patterns\n5. Include engagement reference in report header\n\nIf not found: apply full OWASP Top 10 checklist (default behavior). No scope restrictions.\n\nSee `references\u002Fengagement.md` for the engagement file format.\n\n### Step 1: Identify Security-Relevant Changes\n\nIdentify security-relevant changes from the diff (auth, DB, API, infra, secrets).\n\n### Step 2: Run Checklist\n\nRun the Checklist below, marking each item as pass, fail, or N\u002FA with reason.\n\n### Step 3: Report\n\nFor each failure, cite the file and line number with severity (CRITICAL\u002FHIGH\u002FMEDIUM).\nReport findings using the Evidence Required section.\n\n## When to Trigger\n- Authentication or authorization code changed\n- Database queries written or modified\n- API endpoints added or changed\n- Environment variables or secrets referenced\n- File upload, user input parsing, or serialization code\n- Infrastructure config (Docker, K8s, CI\u002FCD)\n\n## Checklist\n\n### Injection\n- [ ] All user input sanitized\u002Fescaped before use in queries — unsanitized input is the #1 attack vector for SQL injection, XSS, and command injection\n- [ ] Parameterized queries used (no string concatenation in SQL) — string concatenation enables SQL injection even with escaping; parameterized queries are the only safe default\n- [ ] No `eval()`, `exec()`, or template injection vectors — these functions execute arbitrary code and bypass all input validation\n\n### Authentication & Authorization\n- [ ] Auth checks on every protected endpoint — missing checks on a single endpoint exposes the entire system\n- [ ] Tokens validated and not just decoded — decoding without signature verification lets attackers forge any token\n- [ ] Session expiry and refresh logic correct — stale sessions allow account takeover; refresh token rotation prevents replay attacks\n- [ ] No hardcoded credentials or secrets in code — hardcoded secrets end up in version control and are impossible to rotate\n\n### Data Exposure\n- [ ] Sensitive data not logged (passwords, tokens, PII) — logs are often accessible to more people than the database and persist indefinitely\n- [ ] API responses don't leak internal details — stack traces, DB schemas, and server versions help attackers craft targeted exploits\n- [ ] Error messages don't reveal system internals — generic errors in production prevent information disclosure; detailed errors belong in server logs only\n- [ ] `.env` files in `.gitignore` — committed `.env` files expose secrets permanently even after deletion (git history retains them)\n\n### Access Control\n- [ ] RBAC\u002Fpermissions checked before data access — authorization must happen at the data layer, not just the UI layer, to prevent IDOR and privilege escalation\n- [ ] No IDOR (Insecure Direct Object Reference) vulnerabilities — replacing an ID in a URL should never grant access to another user's resource\n- [ ] Rate limiting on authentication endpoints — without rate limiting, brute-force and credential-stuffing attacks are trivial\n\nSee `references\u002Fsecurity.md` for the full OWASP Top 10 checklist.\n\n## Anti-Rationalization\n\n| Excuse | Rebuttal | What to do instead |\n|--------|----------|-------------------|\n| \"This is internal-only, no security risk\" | Internal tools get exposed. Assume every endpoint is public-facing. | Apply the same security standards as public APIs. |\n| \"We'll add security later\" | Security debt compounds exponentially. Fix it now or pay 10x later. | Build it secure from the start. Retrofitting misses edge cases. |\n| \"The framework handles security\" | Frameworks provide tools, not guarantees. OWASP Top 10 still applies. | Verify framework defaults and add application-layer checks. |\n| \"Security review is overkill for this\" | One missed injection is a breach. Every input surface matters. | Run the checklist. It takes 2 minutes, a breach takes months. |\n| \"We'll harden it before production\" | Security bolted on later is always incomplete. | Build it secure now. Retrofitting misses edge cases. |\n| \"It's an internal API, no one will abuse it\" | Lateral movement attacks start from internal APIs. | Internal does not mean trusted. Validate and authorize every request. |\n| \"I'll just disable CORS for development\" | Dev shortcuts leak into production. | Use a proper CORS allow-list from day one. |\n| \"Engagement scoping is bureaucratic overhead\" | Unscoped assessments waste time on irrelevant surface area. | Define scope once, get focused results. Opt-in only. |\n\n## Evidence Required\n\nBefore claiming security review is complete, show ALL applicable:\n\n- [ ] Checklist above completed: each item marked pass or N\u002FA with reason\n- [ ] No secrets in code: `grep -r \"sk-\\|password\\s*=\" --include=\"*.{ts,js,py}\" .` shows clean\n- [ ] Parameterized queries used: show the query code (no string concat)\n- [ ] Auth checks present on new endpoints: show the middleware\u002Fguard\n- [ ] `.env` in `.gitignore`: confirmed\n- [ ] Engagement context loaded (or confirmed absent): scope applied to findings\n\n**A blank checklist is not a review. Each item needs a pass or N\u002FA.**\n\n## Red Flags\n- Storing secrets in code or config files committed to git\n- Using `HTTP` instead of `HTTPS` for sensitive data\n- `eval()` or string-concatenated SQL anywhere\n- Skipping engagement scope when `.harness\u002Fengagement.md` is present\n- Reporting findings outside authorized scope as blockers (informational only)\n","# Secure — Security Review\n\n## Iron Law\n\nNO DEPLOYMENT WITHOUT SECURITY REVIEW OF ALL CHANGED FILES. Every code change is a potential attack vector.\n\n## Process\n\n### Step 0: Load Engagement Context (Optional)\n\nCheck for engagement scoping:\n```bash\ncat .harness\u002Fengagement.md 2>\u002Fdev\u002Fnull\n```\n\nIf `.harness\u002Fengagement.md` exists:\n1. Parse the **Scope**, **Constraints**, and **Exclusions** sections\n2. Restrict security checks to in-scope components\n3. Apply rules of engagement (method, rate limits, no-exfil rules)\n4. Skip findings matching exclusion patterns\n5. Include engagement reference in report header\n\nIf not found: apply full OWASP Top 10 checklist (default behavior). No scope restrictions.\n\nSee `references\u002Fengagement.md` for the engagement file format.\n\n### Step 1: Identify Security-Relevant Changes\n\nIdentify security-relevant changes from the diff (auth, DB, API, infra, secrets).\n\n### Step 2: Run Checklist\n\nRun the Checklist below, marking each item as pass, fail, or N\u002FA with reason.\n\n### Step 3: Report\n\nFor each failure, cite the file and line number with severity (CRITICAL\u002FHIGH\u002FMEDIUM).\nReport findings using the Evidence Required section.\n\n## When to Trigger\n- Authentication or authorization code changed\n- Database queries written or modified\n- API endpoints added or changed\n- Environment variables or secrets referenced\n- File upload, user input parsing, or serialization code\n- Infrastructure config (Docker, K8s, CI\u002FCD)\n\n## Checklist\n\n### Injection\n- [ ] All user input sanitized\u002Fescaped before use in queries — unsanitized input is the #1 attack vector for SQL injection, XSS, and command injection\n- [ ] Parameterized queries used (no string concatenation in SQL) — string concatenation enables SQL injection even with escaping; parameterized queries are the only safe default\n- [ ] No `eval()`, `exec()`, or template injection vectors — these functions execute arbitrary code and bypass all input validation\n\n### Authentication & Authorization\n- [ ] Auth checks on every protected endpoint — missing checks on a single endpoint exposes the entire system\n- [ ] Tokens validated and not just decoded — decoding without signature verification lets attackers forge any token\n- [ ] Session expiry and refresh logic correct — stale sessions allow account takeover; refresh token rotation prevents replay attacks\n- [ ] No hardcoded credentials or secrets in code — hardcoded secrets end up in version control and are impossible to rotate\n\n### Data Exposure\n- [ ] Sensitive data not logged (passwords, tokens, PII) — logs are often accessible to more people than the database and persist indefinitely\n- [ ] API responses don't leak internal details — stack traces, DB schemas, and server versions help attackers craft targeted exploits\n- [ ] Error messages don't reveal system internals — generic errors in production prevent information disclosure; detailed errors belong in server logs only\n- [ ] `.env` files in `.gitignore` — committed `.env` files expose secrets permanently even after deletion (git history retains them)\n\n### Access Control\n- [ ] RBAC\u002Fpermissions checked before data access — authorization must happen at the data layer, not just the UI layer, to prevent IDOR and privilege escalation\n- [ ] No IDOR (Insecure Direct Object Reference) vulnerabilities — replacing an ID in a URL should never grant access to another user's resource\n- [ ] Rate limiting on authentication endpoints — without rate limiting, brute-force and credential-stuffing attacks are trivial\n\nSee `references\u002Fsecurity.md` for the full OWASP Top 10 checklist.\n\n## Anti-Rationalization\n\n| Excuse | Rebuttal | What to do instead |\n|--------|----------|-------------------|\n| \"This is internal-only, no security risk\" | Internal tools get exposed. Assume every endpoint is public-facing. | Apply the same security standards as public APIs. |\n| \"We'll add security later\" | Security debt compounds exponentially. Fix it now or pay 10x later. | Build it secure from the start. Retrofitting misses edge cases. |\n| \"The framework handles security\" | Frameworks provide tools, not guarantees. OWASP Top 10 still applies. | Verify framework defaults and add application-layer checks. |\n| \"Security review is overkill for this\" | One missed injection is a breach. Every input surface matters. | Run the checklist. It takes 2 minutes, a breach takes months. |\n| \"We'll harden it before production\" | Security bolted on later is always incomplete. | Build it secure now. Retrofitting misses edge cases. |\n| \"It's an internal API, no one will abuse it\" | Lateral movement attacks start from internal APIs. | Internal does not mean trusted. Validate and authorize every request. |\n| \"I'll just disable CORS for development\" | Dev shortcuts leak into production. | Use a proper CORS allow-list from day one. |\n| \"Engagement scoping is bureaucratic overhead\" | Unscoped assessments waste time on irrelevant surface area. | Define scope once, get focused results. Opt-in only. |\n\n## Evidence Required\n\nBefore claiming security review is complete, show ALL applicable:\n\n- [ ] Checklist above completed: each item marked pass or N\u002FA with reason\n- [ ] No secrets in code: `grep -r \"sk-\\|password\\s*=\" --include=\"*.{ts,js,py}\" .` shows clean\n- [ ] Parameterized queries used: show the query code (no string concat)\n- [ ] Auth checks present on new endpoints: show the middleware\u002Fguard\n- [ ] `.env` in `.gitignore`: confirmed\n- [ ] Engagement context loaded (or confirmed absent): scope applied to findings\n\n**A blank checklist is not a review. Each item needs a pass or N\u002FA.**\n\n## Red Flags\n- Storing secrets in code or config files committed to git\n- Using `HTTP` instead of `HTTPS` for sensitive data\n- `eval()` or string-concatenated SQL anywhere\n- Skipping engagement scope when `.harness\u002Fengagement.md` is present\n- Reporting findings outside authorized scope as blockers (informational only)\n",{"name":5,"dimension":42,"description":7},"control_and_safety","main","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002Fepicsagas\u002Fepic-harness\u002Fskills\u002Fsecure",491,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins","https:\u002F\u002Fhol.org\u002Fplugins\u002Fbest-codex-plugins","https:\u002F\u002Fgithub.com\u002Fhashgraph-online","https:\u002F\u002Fhol.org","Open-source standards and developer tools for interoperable AI agents: discovery, identity, communication, payments, privacy and security.","2026-11-14 14:06:13",{"source":8,"skillName":5,"commands":54,"prompt":64,"zipAvailable":65},[55,58,61],{"tool":56,"command":57},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill secure",{"tool":59,"command":60},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill secure",{"tool":62,"command":63},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill secure","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fepicsagas\u002Fepic-harness\u002Fskills\u002Fsecure\u002FSKILL.md",true,[],[68,78,86,94,102,110],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":72,"licenseFileUrl":73,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":77},"01M7DV332YQMGD8WTRJ9DZQXTB","worktable-review-with-annotations","Create, inspect, reply to, update, or resolve situated Worktable annotations. Use when feedback belongs to a Doc section, block, text range, or HTML Doc, or when the user asks to address existing review feedback and coordinate a requested artifact edit.","MIT","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":72,"licenseFileUrl":82,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":77},"01M7DV2YGHCZVBEB1AHYB6CGHE","worktable-find-and-synthesize-context","Find, assess, and synthesize context from Worktable Docs and Records. Use when the user asks what a workspace contains, wants workspace-backed research, needs current facts reconciled across artifacts, or requests a cited synthesis without changing workspace state.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":72,"licenseFileUrl":90,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":77},"01M7DV2TQN1H11ME2SAF9MXN7V","worktable-create-or-update-docs","Create, edit, rename, or maintain narrative Worktable Docs. Use for plans, decisions, briefs, notes, research syntheses, and other durable prose when the user requests a new artifact or a safe update to an existing one.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FSKILL.md",[],[],{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":72,"licenseFileUrl":98,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":77},"01M7DV2NE452NEA8TXATKSNAJH","worktable-create-or-manage-records","Organize repeated structured information as durable Worktable Records. Use for research datasets, inventories, directories, pipelines, trackers, and other collections whose items need identity, fields, filtering, links, validation, or individual updates.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FSKILL.md",[],[],{"skillNo":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":72,"licenseFileUrl":106,"sourceHtmlUrl":107,"categories":108,"keywords":109,"publishedAt":77},"01M7DV2HENRBR2KSCVM064WH0Y","worktable-create-or-manage-interactive-html","Create or improve durable visual and interactive artifacts in Worktable. Use for dashboards, trackers, calculators, mini apps, slide presentations, and other requests that benefit from a polished HTML Doc.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FSKILL.md",[],[],{"skillNo":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":72,"licenseFileUrl":114,"sourceHtmlUrl":115,"categories":116,"keywords":117,"publishedAt":77},"01M7DV2CADR5R7RQFFYPNAGR9Y","worktable-collaborate-threads","Read, answer, and hand off messages through durable Worktable threads with users or other authenticated participants. Use when the user asks to check addressed messages, reply to a participant, continue a thread, request another agent's help, wait briefly for a response, or watch for comments and messages sent to the agent.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FSKILL.md",[],[]]