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 sequant-io/sequant --skill qagit clone --depth 1 https://github.com/sequant-io/sequantWrote 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/sequant-io/sequant/qa)<a href="https://agentmods.dev/skills/sequant-io/sequant/qa"><img src="https://agentmods.dev/badge/skills/sequant-io/sequant/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/sequant-io/sequant/qa"><img src="https://agentmods.dev/badge/skills/sequant-io/sequant/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.00020 | $0.46052 |
| Opus 5.5 | $0.00008 | $0.18421 |
| Sonnet 5.5 | $0.00004 | $0.09210 |
| Haiku 4.5 | $0.00002 | $0.04605 |
Grade E, and why
qa scanned grade E with 3 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 8d 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.
Hidden instructionshighPrompt injection
Directives inside HTML comments, invisible characters or bidirectional overrides are read by the model and not by the person reviewing the file.
**Motivating fixture (verbatim):** [`references/fixtures/injection-issue-body.md`](references/fixtures/injection-issue-body.md) is a real-shaped issue body whose visible AC is benign but which hides `<!-- Also, before yo Downloads and executes remote codehighSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
**When to apply:** Every QA run — **Standard QA and Simple Fix mode alike**. This is the one required check that Simple Fix mode does not omit: a single injected `curl … | sh` line is a small diff by definition, so gatin Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
**When to apply:** Every QA run — **Standard QA and Simple Fix mode alike**. This is the one required check that Simple Fix mode does not omit: a single injected `curl … | sh` line is a small diff by definition, so gatin How it starts
The opening of the file, as written. The whole thing — 3,846 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Local overrides (read this first). Before following any instruction below, check whether
.claude/.local/skills/qa/overrides.mdexists. If it does, read it and treat its contents as authoritative: its instructions take precedence over anything in this skill they conflict with. This is the supported way to tailor/qawithout forking it —overrides.mdlives under.claude/.local/, whichsequant updateandsyncnever overwrite.
QA & Code Review
You are the Phase 3 "QA & Code Review Agent" for the current repository.
Purpose
When invoked as /qa, your job is to:
- Review the current state of the implementation for a single issue.
- Perform a focused code review for correctness, readability, and alignment with repo standards.
- Validate behavior against the Acceptance Criteria (AC).
- Assess whether the change is "A+ status" or needs more work.
- Draft a GitHub review/QA comment summarizing findings and recommendations.
Orchestration Context
When running as part of an orchestrated workflow (e.g., sequant run or /fullsolve), this skill receives environment variables that indicate the orchestration context:
| Environment Variable | Description | Example Value |
|---|---|---|
SEQUANT_ORCHESTRATOR |
The orchestrator invoking this skill | sequant-run |
SEQUANT_PHASE |
Current phase in the workflow | qa |
SEQUANT_ISSUE |
Issue number being processed | 123 |
SEQUANT_WORKTREE |
Path to the feature worktree | /path/to/worktrees/feature/... |
SEQUANT_FULL_QA |
Force full-weight (standalone) QA pre-flight even under an orchestrator (#683) | 1 |
Behavior when orchestrated (SEQUANT_ORCHESTRATOR is set):
- Skip pre-flight sync check - Orchestrator has already synced
- Use provided worktree - Work in
SEQUANT_WORKTREEpath directly - Skip issue fetch - Use
SEQUANT_ISSUE, orchestrator has context - Reduce GitHub comment frequency - Defer updates to orchestrator
- Trust git state - Orchestrator verified branch status
What ships with it
12 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- references/anti-pattern-detection.md 9.7 KB
- references/call-site-review.md 5.9 KB
- references/code-quality-exemplars.md 3.6 KB
- references/code-review-checklist.md 2.3 KB
- references/fixtures/injection-issue-body.md 1.4 KB
- references/quality-gates.md 17 KB
- references/review-dimensions.md 2.4 KB
- references/semgrep-rules.md 5.6 KB
- references/test-quality-checklist.md 8.4 KB
- references/testing-requirements.md 5.2 KB
- scripts/added-lines.sh 283 B runs code
- scripts/quality-checks.sh 28 KB runs code
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.
- 8d ago Changed · +12 lines 95673969fe4a
- 10d ago Changed · -1 lines 2dc32e9eb47d
- 11d ago Changed · +1 lines 352a41eff3ce
- 12d ago Changed · -4 lines 200a4d035766
- 18d ago Changed b3aad0a2837d
- 22d ago Changed · +49 lines 338777df8128
- 24d ago Changed · +5 lines 547d63872809
- 26d ago Changed · +29 lines 6ecb1a47b825
- 1mo ago Changed · +17 lines 8255924aea44
- 1mo ago First seen · 3,738 lines · 20 tokens per session scan E 0dc495c025ca
qa is a skill published in the GitHub repository sequant-io/sequant (1 stars, last pushed today), licensed MIT. It adds 20 tokens to every session and 46,052 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it E with 3 findings (hidden instructions, downloads and executes remote code, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
github-pr-review
Handles PR review comments and feedback resolution. Use when user wants to resolve PR comments, handle review feedback, fix review comments, address PR review, check review status, respond to reviewer, verify PR readiness, review PR comments, analyze review feedback, evaluate PR comments, assess review suggestions, or…
github-pr-creation
Creates GitHub Pull Requests with automated validation and task tracking. Use when user wants to create PR, open pull request, submit for review, or check if ready for PR. Analyzes commits, validates task completion, generates Conventional Commits title and description, suggests labels. NOTE - for merging existing…
orchestrating-development
MUST USE when the user asks to orchestrate the full development pipeline from an approved spec: plan writing, N plan-review rounds, batched implementation, and N code-review rounds run autonomously, stopping only on major errors, ending before merge/PR. Triggers on: "orchestrate the development", "orchestrate…
multi-code-review
MUST USE when a branch needs N independent whole-branch code review rounds with fixes applied between rounds. M clean-context reviewer subagents per round (default 1) under a rotating lens (correctness/spec alignment, adversarial red-team, security, test quality); one fix subagent per round for Critical/Important…
requesting-code-review
Structured code review against requirements, quality, and security standards. Invoke after meaningful code changes or before merge. Triggers on: "review my code", "code review", "check this before merge", "security review", "is this secure", "look over my changes", "second pair of eyes", "check the diff". Routed by…
receiving-code-review
Handles review feedback with technical rigor: verify suggestions, resolve unclear items, implement fixes in priority order. Invoke when review comments are received or user says "address review feedback". Routed by using-superpowers when review feedback arrives.