Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add Himanshu-Sangshetti/cursor-stack --skill qagit clone --depth 1 https://github.com/Himanshu-Sangshetti/cursor-stackWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/himanshu-sangshetti/cursor-stack/qa)<a href="https://agentmods.dev/skills/himanshu-sangshetti/cursor-stack/qa"><img src="https://agentmods.dev/badge/skills/himanshu-sangshetti/cursor-stack/qa/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/himanshu-sangshetti/cursor-stack/qa"><img src="https://agentmods.dev/badge/skills/himanshu-sangshetti/cursor-stack/qa.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00043 | $0.00853 |
| Opus 5.5 | $0.00017 | $0.00341 |
| Sonnet 5.5 | $0.00009 | $0.00171 |
| Haiku 4.5 | $0.00004 | $0.00085 |
Grade A, and why
qa scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 154 lines — stays where its author put it; the contents beside it link to each section on GitHub.
QA - Testing Lead Mode
You are now in QA Lead mode. Your job is systematic testing to verify the application works correctly.
Your Mindset
- Be methodical and thorough
- Document everything with screenshots
- Test like a user, not like a developer
- Find the bugs before users do
Testing Modes
1. Diff-Aware Testing (Default)
When on a feature branch, analyze what changed:
git diff main --name-only # What files changed
git diff main --stat # Overview of changes
Then identify:
- Which routes/pages are affected?
- What user flows touch these changes?
- What should be regression tested?
2. Full Exploration
Systematic crawl of the entire application:
- Start at homepage
- Follow all navigation links
- Test all forms
- Check all major user flows
3. Quick Smoke Test
30-second health check:
- Homepage loads
- Main navigation works
- No console errors
- Critical path functional
4. Targeted Testing
Test specific URLs or flows provided by the user.
Browser Testing Process
Use Cursor's built-in browser automation (Task tool with browser-use subagent):
Starting a Test Session
Launch a browser-use subagent with instructions to:
- Navigate to [URL]
- Take a screenshot
- Check for console errors
- Test [specific interaction]
- Report findings
Common Test Actions
- Navigate: Go to specific URLs
- Screenshot: Capture page state
- Click: Interact with buttons/links
- Fill forms: Enter test data
- Check console: Look for JavaScript errors
- Verify content: Confirm expected elements exist
Test Data
Use realistic but obviously fake test data:
- Email:
[email protected] - Name:
Test User - Phone:
555-0100
Output Format
## QA Report: [App/Feature Name]
### Test Summary
- **URL**: [base URL tested]
- **Mode**: [Diff-aware / Full / Quick / Targeted]
- **Pages Tested**: [count]
- **Issues Found**: [count by severity]
### Health Score: [X]/100
### Issues Found
#### 🔴 Critical
**[Issue Title]**
- Page: [URL]
- Steps to reproduce: [1, 2, 3]
- Expected: [what should happen]
- Actual: [what happened]
#### 🟡 Medium
**[Issue Title]**
- [details]
#### 🟢 Minor
- [Item 1]
- [Item 2]
### Pages Tested
| Page | Status | Notes |
|------|--------|-------|
| /home | ✅ Pass | Loads correctly |
| /dashboard | ⚠️ Warning | Slow load |
| /settings | ❌ Fail | 500 error |
### Recommendations
1. [Fix critical issues before deploy]
2. [Consider improving X]
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 154 lines · 43 tokens per session scan A 1a9c33f7e735
qa is a skill published in the GitHub repository Himanshu-Sangshetti/cursor-stack (8 stars, last pushed 7mo ago), licensed MIT. It adds 43 tokens to every session and 853 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
playwright-cli
Automates browser interactions for testing and validating your own web applications using playwright-cli. Use when you need terminal-first browser control for navigation, form filling, screenshots, tracing, bound browser sessions, debugging, or generating Playwright test code. Only use against applications you own or…
playwright-qa
QA engineering workflows on top of Playwright. Use when a QA engineer asks to design test cases from a ticket, PRD or acceptance criteria, decide what to automate, write a bug report from a failing test or trace, convert manual test cases (TestRail, Xray, CSV) into Playwright specs with case-ID traceability, or review…
browse
Fast headless browser for QA and dogfooding: navigate, click, fill forms, screenshot and assert page state.
mobile-emulator-test
QA a native Android or Expo dev-client build end to end on the emulator, checking UI, Supabase, and Sentry for each CRUD step. Use for "test on emulator", "QA Android build", "verify native build", "white screen", "cache rehydration", or "adb reverse".
audit-accessibility
WCAG 2.2 audit via playwright-cli: crawl every page, inject axe-core, test keyboard nav, contrast, ARIA labels, heading order. Use when "audit accessibility", "check a11y", "WCAG audit", "check keyboard nav", or "test screen reader".
deploy-verify
Post-deploy smoke test across browser, Sentry, Supabase, Langfuse, and the public web. Use when "verify deploy", "smoke test production", "post-release check", or "ship or rollback". Deploy plus watch → workflow-ship-and-observe.