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 agentmods add skills/jkudjo/oh-my-cursor/qanpx skills add Jkudjo/oh-my-cursor --skill qagit clone --depth 1 https://github.com/Jkudjo/oh-my-cursorWrote 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/jkudjo/oh-my-cursor/qa)<a href="https://agentmods.dev/skills/jkudjo/oh-my-cursor/qa"><img src="https://agentmods.dev/badge/skills/jkudjo/oh-my-cursor/qa.svg" alt="Measured on agentmods" 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.00018 | $0.00229 |
| Opus 5 | $0.00009 | $0.00114 |
| Sonnet 5 | $0.00004 | $0.00046 |
| Haiku 4.5 | $0.00002 | $0.00023 |
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 6d 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.
What it actually says
qa
Invoke this skill to run a structured QA testing pass.
When to use
- After implementing a feature
- Before shipping or creating a PR
- When you want to verify edge cases were handled
What it does
- Identifies what was built (reads recent changes, plan if available)
- Generates a test plan:
- Happy path scenarios
- Edge cases (empty, null, max, concurrent)
- Error/failure paths
- Integration points
- Executes each test case — runs code, reads output, verifies behavior
- For each failure: documents repro steps, expected vs actual
- Reports:
- Health score (0–100)
- Passed / Failed / Skipped counts
- Bug list with repro steps
- Recommendation: SHIP / SHIP WITH NOTES / HOLD
Example
@qa "the new authentication flow"
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.
- 6d ago First seen · 38 lines · 18 tokens per session scan A db730ab75daf
qa is a skill published in the GitHub repository Jkudjo/oh-my-cursor (1 stars, last pushed 5mo ago), licensed MIT. It adds 18 tokens to every session and 229 once invoked, about $0.0001 per session on Opus 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
testing-pyramid
Test Distribution Analysis Command 🧪.
android-preflight
Final verification checklist to run before declaring Android work finished — build, both themes, string resources, lifecycle and leak risks, registered permissions and components, resource parity between values and values-night, and honest reporting of what was and was not verified. Use at the end of any feature, fix…
ai-evals-builder
Build AI evals using the Husain-Shankar framework (error analysis, open/axial coding, LLM-as-judge). Use when a user needs to create, improve, or debug evals for an AI product — including defining failure modes, building LLM judges, or setting up production monitoring for an LLM application.
test-driven-development
Use when implementing any feature, bugfix, or code change - write tests first, watch them fail, then implement.
character-animation-qa
Review local character animation with schema checks, Playwright browser previews, frame sampling, and FFmpeg/ffprobe final output checks.
patrol-e2e-testing
Use when writing E2E/integration tests, testing native interactions like permissions or system dialogs, capturing UI regressions, or validating cross-platform behavior (Patrol 4.x).