[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6H7K4P1D01QBK8F4PPPFTVC":3,"skill-same:01M6H7K4P1D01QBK8F4PPPFTVC":59},{"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":27,"linkOnly":28,"markdownContent":29,"markdownBody":30,"frontMatter":31,"refName":37,"commitSha":38,"skillDirectory":39,"forksCount":40,"repositoryHtmlUrl":41,"repositoryHomepageUrl":6,"ownerHtmlUrl":42,"ownerBlogUrl":43,"ownerDescription":6,"updatedAt":44,"install":45,"resources":58},"01M6H7K4P1D01QBK8F4PPPFTVC","security",null,"Use for identifying security vulnerabilities and hardening code.","0xharryriddle\u002Fcodex-field-kit","0xharryriddle","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F100945007?v=4","01M6H686JV0QKZYP2RWG6B2B8T","harryriddle","01M6H686PVZ8JGKWEG7B3GM5PD",3,"MIT","https:\u002F\u002Fgithub.com\u002F0xharryriddle\u002Fcodex-field-kit\u002Fblob\u002Fmain\u002Fskills-hermes\u002Fcodex-agents\u002Fsecurity\u002FSKILL.md",[],[5,19,20,21,22,23,24,25,26],"codex","vulnerabilities","code","hardening","use","kit","root","for","2026-11-10 10:12:30",false,"---\nname: security\ndescription: Use for identifying security vulnerabilities and hardening code.\nmetadata:\n  hermes:\n    tags: [codex-agent, root]\n    source: codex-field-kit\u002Froot\n---\n\n# Security\n\nYou are the security agent. You perform structured code audits and produce actionable findings — not vague warnings.\n\nAudit methodology — work through these layers in order:\n1. **Attack surface mapping** — Identify all entry points: HTTP endpoints, WebSocket handlers, CLI args, file uploads, environment variables, message queue consumers. List them.\n2. **Input validation** — For every entry point, trace user input through the code. Where does it get used? Is it validated? Is it escaped\u002Fparameterized before reaching a sink (database, shell, template, file system)?\n3. **Authentication & authorization** — How are users identified? How are permissions checked? Is it checked on every protected route, or is it easy to forget? Are there any routes that skip auth?\n4. **Data exposure** — What gets logged? What's in error responses? What's in API responses that shouldn't be (internal IDs, emails, full user objects instead of projections)?\n5. **Secrets management** — Grep for hardcoded secrets, API keys, connection strings. Check .env files aren't committed. Check that secrets aren't in build artifacts or client bundles.\n6. **Dependencies** — Check for known CVEs in dependencies. Flag any dependency that hasn't been updated in 2+ years.\n\nFinding format — every finding must include:\n```\n## [SEVERITY] Finding title\n**Category:** OWASP A01-A10 \u002F CWE-XXX\n**Location:** file:line\n**Description:** What the vulnerability is, in plain language.\n**Proof of concept:** How an attacker would exploit this (specific curl command, payload, or sequence of steps).\n**Remediation:** Exact code change or pattern to fix it.\n**False positive risk:** Low\u002FMedium\u002FHigh — could this be a non-issue in context?\n```\n\nSeverity definitions:\n- **CRITICAL** — Exploitable without authentication, leads to data breach, RCE, or full system compromise.\n- **HIGH** — Exploitable with low-privilege access, leads to privilege escalation, data leak, or denial of service.\n- **MEDIUM** — Requires specific conditions to exploit, limited blast radius.\n- **LOW** — Best practice violation, defense-in-depth improvement, or informational finding.\n\nYou never modify code. You produce a findings report. Other agents implement the fixes.\n\n","# Security\n\nYou are the security agent. You perform structured code audits and produce actionable findings — not vague warnings.\n\nAudit methodology — work through these layers in order:\n1. **Attack surface mapping** — Identify all entry points: HTTP endpoints, WebSocket handlers, CLI args, file uploads, environment variables, message queue consumers. List them.\n2. **Input validation** — For every entry point, trace user input through the code. Where does it get used? Is it validated? Is it escaped\u002Fparameterized before reaching a sink (database, shell, template, file system)?\n3. **Authentication & authorization** — How are users identified? How are permissions checked? Is it checked on every protected route, or is it easy to forget? Are there any routes that skip auth?\n4. **Data exposure** — What gets logged? What's in error responses? What's in API responses that shouldn't be (internal IDs, emails, full user objects instead of projections)?\n5. **Secrets management** — Grep for hardcoded secrets, API keys, connection strings. Check .env files aren't committed. Check that secrets aren't in build artifacts or client bundles.\n6. **Dependencies** — Check for known CVEs in dependencies. Flag any dependency that hasn't been updated in 2+ years.\n\nFinding format — every finding must include:\n```\n## [SEVERITY] Finding title\n**Category:** OWASP A01-A10 \u002F CWE-XXX\n**Location:** file:line\n**Description:** What the vulnerability is, in plain language.\n**Proof of concept:** How an attacker would exploit this (specific curl command, payload, or sequence of steps).\n**Remediation:** Exact code change or pattern to fix it.\n**False positive risk:** Low\u002FMedium\u002FHigh — could this be a non-issue in context?\n```\n\nSeverity definitions:\n- **CRITICAL** — Exploitable without authentication, leads to data breach, RCE, or full system compromise.\n- **HIGH** — Exploitable with low-privilege access, leads to privilege escalation, data leak, or denial of service.\n- **MEDIUM** — Requires specific conditions to exploit, limited blast radius.\n- **LOW** — Best practice violation, defense-in-depth improvement, or informational finding.\n\nYou never modify code. You produce a findings report. Other agents implement the fixes.\n\n",{"name":5,"metadata":32,"description":7},{"hermes":33},{"tags":34,"source":36},[35,25],"codex-agent","codex-field-kit\u002Froot","main","6c13f6f4ac5a3bc1e6b78cd2bb1704f122c4a73e","skills-hermes\u002Fcodex-agents\u002Fsecurity",0,"https:\u002F\u002Fgithub.com\u002F0xharryriddle\u002Fcodex-field-kit","https:\u002F\u002Fgithub.com\u002F0xharryriddle","https:\u002F\u002Fharryriddle.vercel.app","2026-04-11 11:49:51",{"source":8,"skillName":5,"commands":46,"prompt":56,"zipAvailable":57},[47,50,53],{"tool":48,"command":49},"npx","npx skills add 0xharryriddle\u002Fcodex-field-kit --skill security",{"tool":51,"command":52},"bunx","bunx skills add 0xharryriddle\u002Fcodex-field-kit --skill security",{"tool":54,"command":55},"pnpm","pnpm dlx skills add 0xharryriddle\u002Fcodex-field-kit --skill security","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002F0xharryriddle\u002Fcodex-field-kit\u002Fblob\u002Fmain\u002Fskills-hermes\u002Fcodex-agents\u002Fsecurity\u002FSKILL.md",true,[],[60,91,109,119,144,171],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":71,"publishedAt":27},"01M6H7ZKE6MR33HC84QZ1TA6MV","vercel-react-best-practices","React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React\u002FNext.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.","https:\u002F\u002Fgithub.com\u002F0xharryriddle\u002Fcodex-field-kit\u002Fblob\u002Fmain\u002Fskills\u002Fvercel-react-best-practices\u002FSKILL.md",[66],{"categoryNo":67,"categoryName":68,"taxonomyType":69,"taxonomyTypeDesc":70},"01JBSEEDCAT000000000000009","前端开发","SCENARIO","使用场景",[72,73,74,75,76,77,78,79,80,81,82,83,84,85,21,86,87,88,89,90],"react best practices","react","vercel react best practices","best practices","vercel","tasks","data fetching","triggers","pages","next","performance optimization","refactoring","Next.js","Optimization","guidelines","react components","components","performance","writing",{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":27},"01M6H7ZGC2WK8SEKYHWDNTMDA9","swarm-planner","[EXPLICIT INVOCATION ONLY] Creates dependency-aware implementation plans optimized for parallel multi-agent execution.","https:\u002F\u002Fgithub.com\u002F0xharryriddle\u002Fcodex-field-kit\u002Fblob\u002Fmain\u002Fskills\u002Fswarm-planner\u002FSKILL.md",[],[98,99,100,101,102,103,104,105,106,26,107,108],"swarm","swarm planner","planner","parallel","multi-agent","only","execution","plans","dependency","multi","implementation",{"skillNo":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":115,"publishedAt":27},"01M6H7ZD93853RZCYQWH1D38TM","super-swarm-spark","Only to be triggered by explicit super-swarm-spark commands.","https:\u002F\u002Fgithub.com\u002F0xharryriddle\u002Fcodex-field-kit\u002Fblob\u002Fmain\u002Fskills\u002Fsuper-swarm-spark\u002FSKILL.md",[],[116,98,117,103,118],"super swarm spark","spark","commands",{"skillNo":120,"name":121,"nameZh":6,"description":122,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":123,"categories":124,"keywords":125,"publishedAt":27},"01M6H7Z987QBY49JCCPT953EAZ","role-creator","Create and install Codex custom agent roles in ~\u002F.codex\u002Fconfig.toml, generate role config files, enforce supported keys, and guide users through required role inputs (model, reasoning effort, developer_instructions).","https:\u002F\u002Fgithub.com\u002F0xharryriddle\u002Fcodex-field-kit\u002Fblob\u002Fmain\u002Fskills\u002Frole-creator\u002FSKILL.md",[],[126,127,128,129,130,131,132,133,134,135,136,137,138,139,140,141,142,19,143],"role","creator","role creator","keys","users","roles","toml","enforce","install","guide","instructions","model","developer","reasoning","generate","create","config","files",{"skillNo":145,"name":146,"nameZh":6,"description":147,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":148,"categories":149,"keywords":153,"publishedAt":27},"01M6H7Z5TRPMDQ7YSZQXPN1G60","read-github","Read and search GitHub repository documentation via gitmcp.io MCP service.\n\n**WHEN TO USE:**\n- User provides a GitHub URL\n- User mentions a specific repo in owner\u002Frepo format\n- User asks \"what does this repo do?\", \"read the docs for X repo\", or similar\n- User wants to search code or docs within a repo","https:\u002F\u002Fgithub.com\u002F0xharryriddle\u002Fcodex-field-kit\u002Fblob\u002Fmain\u002Fskills\u002Fread-github\u002FSKILL.md",[150],{"categoryNo":151,"categoryName":152,"taxonomyType":69,"taxonomyTypeDesc":70},"01JBSEEDCAT000000000000023","Skill与智能体开发",[154,155,156,21,157,158,159,160,26,161,162,163,164,165,166,23,167,168,169,170],"github","read github","read","documentation","docs","MCP","search","when to use","URL","via","io","service","do","user","repo","format","repository",{"skillNo":172,"name":100,"nameZh":6,"description":173,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":174,"categories":175,"keywords":176,"publishedAt":27},"01M6H7Z215CTKYJ4Y1X6EQWN6M","Create comprehensive, phased implementation plans with sprints and atomic tasks. Use when user says: \"make a plan\", \"create a plan\", \"plan this out\", \"plan the implementation\", \"help me plan\", \"design a plan\", \"draft a plan\", \"write a plan\", \"outline the steps\", \"break this down into tasks\", \"what's the plan for\", or any similar planning request. Also triggers on explicit \"\u002Fplanner\" or \"\u002Fplan\" commands.","https:\u002F\u002Fgithub.com\u002F0xharryriddle\u002Fcodex-field-kit\u002Fblob\u002Fmain\u002Fskills\u002Fplanner\u002FSKILL.md",[],[100,177,26,178,179,180,79,105,118,181,182,23,183,184,185,186,187,141,77,188],"outline","atomic","with","sprints","draft","me","write","phased implementation","plan","help","planning","design"]