[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CSJ00JWNZDW0XK346M8BAD":3,"skill-same:01M7CSJ00JWNZDW0XK346M8BAD":49},{"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":27,"commitSha":28,"skillDirectory":29,"forksCount":30,"repositoryHtmlUrl":31,"repositoryHomepageUrl":6,"ownerHtmlUrl":32,"ownerBlogUrl":6,"ownerDescription":33,"updatedAt":34,"install":35,"resources":48},"01M7CSJ00JWNZDW0XK346M8BAD","web-app-penetration-testing",null,"Pentest a web app or website end to end — black-box testing of a live URL, staging environment, or local dev server that finds and exploits real vulnerabilities (auth bypass, broken access control, IDOR, injection, XSS, SSRF, business logic) and proves each one with a working proof-of-concept instead of a signature match. Runs with Strix, either the self-hosted open-source CLI or the managed app.strix.ai cloud. Use when the user asks to pentest, hack, security-test, or audit their web app, website, web application, or staging site.","Hareesh-Reddy-9126\u002FPS044-SmartHire","Hareesh-Reddy-9126","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F203651565?v=4","01M7CRVG65SPPJE7CDJT0KRKKY","hareesh reddy","01M7CRVG6TEPD8RCR0GBDP5ANS",1,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FHareesh-Reddy-9126\u002FPS044-SmartHire\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fweb-app-penetration-testing\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: web-app-penetration-testing\ndescription: Pentest a web app or website end to end — black-box testing of a live URL, staging environment, or local dev server that finds and exploits real vulnerabilities (auth bypass, broken access control, IDOR, injection, XSS, SSRF, business logic) and proves each one with a working proof-of-concept instead of a signature match. Runs with Strix, either the self-hosted open-source CLI or the managed app.strix.ai cloud. Use when the user asks to pentest, hack, security-test, or audit their web app, website, web application, or staging site.\nlicense: Apache-2.0\nmetadata:\n  author: usestrix\n  homepage: https:\u002F\u002Fdocs.strix.ai\n---\n\n# Pentest a web application\n\nBlack-box (and optionally source-assisted) penetration testing of a running web app with Strix's autonomous agents. Every reported finding is validated with a working exploit, so there are no signature-based false positives to triage.\n\nInstall, LLM setup, all CLI flags, and the managed-cloud alternative are covered in the **penetration-testing-with-strix** skill — read it if the target is not a running web app, or if `strix --version` fails. For a run with no Docker and no LLM key, the same binary drives the managed platform: `strix cloud login`, then `strix cloud scans start ...` (details in **managed-pentesting-with-strix**). This skill is the web-app-specific workflow.\n\n## 1. Confirm authorization and scope\n\nBefore running anything, establish:\n\n- **The target is the user's** (or they are explicitly authorized to test it). Never pentest a third-party site on a hunch.\n- **Which environment.** Prefer staging over production; agents send real exploit payloads and will create\u002Fmodify data.\n- **Out-of-scope paths** — payment flows, mass-email endpoints, admin destructive actions, third-party SSO providers.\n- **Credentials.** Most real vulnerabilities live behind login. Without a test account, the agents only ever see the marketing surface.\n\nAsk for anything missing rather than guessing.\n\n## 2. Run the scan\n\n```bash\nstrix -n -t https:\u002F\u002Fstaging.example.com --max-budget 20 \\\n  --instruction \"Test account: qa@example.com \u002F \u003Cpassword>. In scope: \u002Fapp\u002F*, \u002Fapi\u002F*. Do not touch \u002Fbilling or send email. Focus on access control between the two seeded orgs.\"\n```\n\nNotes that matter for web apps specifically:\n\n- **Give it credentials via `--instruction`** (or `--instruction-file` for anything long), including how to log in if the flow is unusual (magic link, SSO, MFA-exempt test user).\n- **Two accounts beat one.** Multi-tenant IDOR and broken-access-control bugs — consistently the highest-impact class in web apps — can only be proven when the agent can attempt cross-account access.\n- **Add the repo for white-box depth** when you have the source: `-t https:\u002F\u002Fgithub.com\u002Forg\u002Fapp -t https:\u002F\u002Fstaging.example.com` (or a local path). Source access materially improves coverage of business-logic and authorization flaws.\n- **Localhost works.** Point at `http:\u002F\u002Fhost.docker.internal:3000` (Docker Desktop) so the sandbox can reach a dev server on the host.\n- `--scan-mode quick` for a fast dev-loop pass, `standard` (~30 min) for a normal review, `deep` for pre-release assurance. Always set `--max-budget`.\n\nFor a hosted run with no Docker\u002FLLM key, or when the user wants a shareable dashboard and an auditor-ready PDF, use the cloud path in **managed-pentesting-with-strix** instead — same engine, same findings.\n\n## 3. Review results\n\nRead `strix_runs\u002F\u003Crun>\u002Fpenetration_test_report.md` first, then per-finding files in `vulnerabilities\u002F`. Each contains the PoC — re-run it yourself to confirm before reporting to the user.\n\nExit codes: `0` no validated vulns in what was analyzed, `2` vulnerabilities found, `1` fatal error. A `0` is not proof of full coverage — if the budget or turn cap was hit the scan wraps up early, so check `run.json` status and cost against `--max-budget` before calling the app clean.\n\n## 4. Fix and verify\n\nHand findings to the **fix-security-vulnerabilities-with-strix** skill: patch the root cause, then re-run Strix against the same target to prove the exploit no longer works. Re-testing is the only reliable confirmation a fix landed.\n\nTo keep the app tested on every change rather than once, wire Strix into CI with **ci-security-scanning-with-strix**.\n","# Pentest a web application\n\nBlack-box (and optionally source-assisted) penetration testing of a running web app with Strix's autonomous agents. Every reported finding is validated with a working exploit, so there are no signature-based false positives to triage.\n\nInstall, LLM setup, all CLI flags, and the managed-cloud alternative are covered in the **penetration-testing-with-strix** skill — read it if the target is not a running web app, or if `strix --version` fails. For a run with no Docker and no LLM key, the same binary drives the managed platform: `strix cloud login`, then `strix cloud scans start ...` (details in **managed-pentesting-with-strix**). This skill is the web-app-specific workflow.\n\n## 1. Confirm authorization and scope\n\nBefore running anything, establish:\n\n- **The target is the user's** (or they are explicitly authorized to test it). Never pentest a third-party site on a hunch.\n- **Which environment.** Prefer staging over production; agents send real exploit payloads and will create\u002Fmodify data.\n- **Out-of-scope paths** — payment flows, mass-email endpoints, admin destructive actions, third-party SSO providers.\n- **Credentials.** Most real vulnerabilities live behind login. Without a test account, the agents only ever see the marketing surface.\n\nAsk for anything missing rather than guessing.\n\n## 2. Run the scan\n\n```bash\nstrix -n -t https:\u002F\u002Fstaging.example.com --max-budget 20 \\\n  --instruction \"Test account: qa@example.com \u002F \u003Cpassword>. In scope: \u002Fapp\u002F*, \u002Fapi\u002F*. Do not touch \u002Fbilling or send email. Focus on access control between the two seeded orgs.\"\n```\n\nNotes that matter for web apps specifically:\n\n- **Give it credentials via `--instruction`** (or `--instruction-file` for anything long), including how to log in if the flow is unusual (magic link, SSO, MFA-exempt test user).\n- **Two accounts beat one.** Multi-tenant IDOR and broken-access-control bugs — consistently the highest-impact class in web apps — can only be proven when the agent can attempt cross-account access.\n- **Add the repo for white-box depth** when you have the source: `-t https:\u002F\u002Fgithub.com\u002Forg\u002Fapp -t https:\u002F\u002Fstaging.example.com` (or a local path). Source access materially improves coverage of business-logic and authorization flaws.\n- **Localhost works.** Point at `http:\u002F\u002Fhost.docker.internal:3000` (Docker Desktop) so the sandbox can reach a dev server on the host.\n- `--scan-mode quick` for a fast dev-loop pass, `standard` (~30 min) for a normal review, `deep` for pre-release assurance. Always set `--max-budget`.\n\nFor a hosted run with no Docker\u002FLLM key, or when the user wants a shareable dashboard and an auditor-ready PDF, use the cloud path in **managed-pentesting-with-strix** instead — same engine, same findings.\n\n## 3. Review results\n\nRead `strix_runs\u002F\u003Crun>\u002Fpenetration_test_report.md` first, then per-finding files in `vulnerabilities\u002F`. Each contains the PoC — re-run it yourself to confirm before reporting to the user.\n\nExit codes: `0` no validated vulns in what was analyzed, `2` vulnerabilities found, `1` fatal error. A `0` is not proof of full coverage — if the budget or turn cap was hit the scan wraps up early, so check `run.json` status and cost against `--max-budget` before calling the app clean.\n\n## 4. Fix and verify\n\nHand findings to the **fix-security-vulnerabilities-with-strix** skill: patch the root cause, then re-run Strix against the same target to prove the exploit no longer works. Re-testing is the only reliable confirmation a fix landed.\n\nTo keep the app tested on every change rather than once, wire Strix into CI with **ci-security-scanning-with-strix**.\n",{"name":5,"license":15,"metadata":24,"description":7},{"author":25,"homepage":26},"usestrix","https:\u002F\u002Fdocs.strix.ai","main","bc2f998beb877748d6e8c4588942b4ff2cfa495b",".agents\u002Fskills\u002Fweb-app-penetration-testing",0,"https:\u002F\u002Fgithub.com\u002FHareesh-Reddy-9126\u002FPS044-SmartHire","https:\u002F\u002Fgithub.com\u002FHareesh-Reddy-9126","🎓 B.Tech 3rd Year | CS&IT | 📈 LeetCode Grinder | Building side projects that actually matter | 🤝 Looking for: Internship 2026 | Open Source Collabs","2026-10-29 13:27:16",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add Hareesh-Reddy-9126\u002FPS044-SmartHire --skill web-app-penetration-testing",{"tool":41,"command":42},"bunx","bunx skills add Hareesh-Reddy-9126\u002FPS044-SmartHire --skill web-app-penetration-testing",{"tool":44,"command":45},"pnpm","pnpm dlx skills add Hareesh-Reddy-9126\u002FPS044-SmartHire --skill web-app-penetration-testing","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHareesh-Reddy-9126\u002FPS044-SmartHire\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fweb-app-penetration-testing\u002FSKILL.md",true,[],[50,58,66,71,79,86],{"skillNo":51,"name":52,"nameZh":6,"description":53,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":54,"sourceHtmlUrl":55,"categories":56,"keywords":57,"publishedAt":19},"01M7CT84AFNKCD7HYFGTK9V65T","webapp-testing","Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.","https:\u002F\u002Fgithub.com\u002FHareesh-Reddy-9126\u002FPS044-SmartHire\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FHareesh-Reddy-9126\u002FPS044-SmartHire\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fwebapp-testing\u002FSKILL.md",[],[],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":62,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":19},"01M7CT7XM14XJZT9F5N634FPVP","web-artifacts-builder","Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn\u002Fui). Use for complex artifacts requiring state management, routing, or shadcn\u002Fui components - not for simple single-file HTML\u002FJSX artifacts.","https:\u002F\u002Fgithub.com\u002FHareesh-Reddy-9126\u002FPS044-SmartHire\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fweb-artifacts-builder\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FHareesh-Reddy-9126\u002FPS044-SmartHire\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fweb-artifacts-builder\u002FSKILL.md",[],[],{"skillNo":67,"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":68,"categories":69,"keywords":70,"publishedAt":19},"01M7CT7RAWP38MMBQZ274RNM34","https:\u002F\u002Fgithub.com\u002FHareesh-Reddy-9126\u002FPS044-SmartHire\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fweb-app-penetration-testing\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":75,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":19},"01M7CT7K4CW6BNQEY2D1W1GNM4","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.","MIT","https:\u002F\u002Fgithub.com\u002FHareesh-Reddy-9126\u002FPS044-SmartHire\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fvercel-react-best-practices\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":75,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M7CT7EFR7S5RXBGX2E2Q8H6X","typescript-pro","Implements advanced TypeScript type systems, creates custom type guards, utility types, and branded types, and configures tRPC for end-to-end type safety. Use when building TypeScript applications requiring advanced generics, conditional or mapped types, discriminated unions, monorepo setup, or full-stack type safety with tRPC.","https:\u002F\u002Fgithub.com\u002FHareesh-Reddy-9126\u002FPS044-SmartHire\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Ftypescript-pro\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":15,"licenseFileUrl":90,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":19},"01M7CT7BR0WF3BPWYSD7SP4MJP","theme-factory","Toolkit for styling artifacts with a theme. These artifacts can be slides, docs, reportings, HTML landing pages, etc. There are 10 pre-set themes with colors\u002Ffonts that you can apply to any artifact that has been creating, or can generate a new theme on-the-fly.","https:\u002F\u002Fgithub.com\u002FHareesh-Reddy-9126\u002FPS044-SmartHire\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Ftheme-factory\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FHareesh-Reddy-9126\u002FPS044-SmartHire\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Ftheme-factory\u002FSKILL.md",[],[]]