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 WellApp-ai/Well --skill qa-commitgit clone --depth 1 https://github.com/WellApp-ai/WellWrote 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/wellapp-ai/well/qa-commit)<a href="https://agentmods.dev/skills/wellapp-ai/well/qa-commit"><img src="https://agentmods.dev/badge/skills/wellapp-ai/well/qa-commit/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/wellapp-ai/well/qa-commit"><img src="https://agentmods.dev/badge/skills/wellapp-ai/well/qa-commit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00024 | $0.01304 |
| Opus 5.5 | $0.00010 | $0.00522 |
| Sonnet 5.5 | $0.00005 | $0.00261 |
| Haiku 4.5 | $0.00002 | $0.00130 |
Grade A, and why
qa-commit 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 — 236 lines — stays where its author put it; the contents beside it link to each section on GitHub.
QA Commit Skill
Verify that the current commit satisfies its assigned QA Contract criteria (G#N Gherkin scenarios and AC#N acceptance criteria). Returns GREEN (pass) or RED (fail, triggers debug).
When to Use
- After pr-review passes, before git commit
- During Agent Mode commit-level workflow
- Manually with "use qa-commit skill"
Input: Commit Context
Before running, identify:
- Current commit from Commit Plan
- Assigned criteria: "Satisfies: G#X, AC#Y, ..."
- Related files being changed
Phase 1: Load QA Contract
Retrieve the assigned criteria for this commit:
## Commit: [Name]
**Satisfies:** G#1, G#2, AC#1, AC#3
### Criteria to Verify:
- G#1: [Scenario description]
- G#2: [Scenario description]
- AC#1: [Acceptance criteria]
- AC#3: [Acceptance criteria]
Phase 2: Technical Validation
Use Cursor tools for technical checks:
2.1 ReadLints
ReadLints:
paths: [changed files]
Expect: No errors related to committed functionality
2.2 Type Safety
npm run typecheck
Expect: Exit code 0
2.3 Related Tests (if exist)
npm run test -- --grep "[feature name]"
Expect: All tests pass
Phase 3: Gherkin Verification (Backend - G#N)
For each G#N assigned to this commit:
3.1 Endpoint Existence
Verify the API endpoint exists and is implemented:
SemanticSearch: "Where is [endpoint] implemented?"
3.2 Response Shape
Check response matches expected schema:
Grep: "interface.*Response" in related files
3.3 Error Handling
Verify error cases are handled:
Grep: "throw|catch|error" in handler files
Gherkin Checklist
| G#N | Scenario | Status | Notes |
|---|---|---|---|
| G#1 | [Name] | PASS/FAIL | [Details] |
| G#2 | [Name] | PASS/FAIL | [Details] |
Phase 4: Acceptance Verification (Frontend - AC#N)
For each AC#N assigned to this commit:
4.1 Component Existence
Verify component is implemented:
Glob: **/*[ComponentName]*.tsx
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 · 236 lines · 24 tokens per session scan A 1d205dc9a167
qa-commit is a skill published in the GitHub repository WellApp-ai/Well (345 stars, last pushed 6d ago), licensed MIT. It adds 24 tokens to every session and 1,304 once invoked, about $0.0001 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-30.
Other skills, from other repositories
api-contract-testing
Design and review API contract tests across providers and consumers. Use for schema changes, compatibility regressions and client integration failures.
server-side-calls
Call tRPC procedures directly from server code using t.createCallerFactory() and router.createCaller(context) for integration testing, internal server logic, and custom API endpoints. Catch TRPCError and extract HTTP status with getHTTPStatusCodeFromError(). Error handling via onError option.
mirrord-prev-env
Help users create and manage mirrord preview environments — running a modified service as an isolated pod in a shared Kubernetes cluster, scoped by an environment key and HTTP/queue traffic filtering, so teams can validate and review changes against real traffic without affecting live services. Use when a developer…
mirrord-chaos
Help users chaos test their app with mirrord: inject artificial latency or connection errors into a mirrord session's outgoing traffic via per-session chaos rules managed with the mirrord chaos CLI. Use when a user wants to add latency or delay to outgoing connections or a dependency (e.g. a slow database), simulate…
horse-integration-tests
Guide for writing automated integration tests for Horse endpoints using DUnit/DUnitX and THTTPClient.
qa
QA test your code changes by reading your git diff, choosing the right validation path for frontend/browser and backend changes, and reporting pass/fail with evidence.