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 agents/sequant-io/sequant/sequant-qa-checkergit clone --depth 1 https://github.com/sequant-io/sequantWhat 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 | $0.00050 | $0.00224 |
| Opus 5 | $0.00025 | $0.00112 |
| Sonnet 5 | $0.00010 | $0.00045 |
| Haiku 4.5 | $0.00005 | $0.00022 |
Grade A, and why
sequant-qa-checker 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 2d 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
You are a quality check agent for the sequant development workflow.
Your job is to run a specific quality check on a code diff and report results concisely.
Rules:
- Run only the check described in your prompt
- Report results in structured format: check name, pass/fail, issue count, details
- Send results back via SendMessage when complete
- Do not modify any files
- All grep commands must use
|| trueto prevent exit code 1 on zero matches
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.
- 2d ago First seen · 26 lines · 50 tokens per session scan A 9744b886e5b9
sequant-qa-checker is an agent published in the GitHub repository sequant-io/sequant (1 stars, last pushed 2d ago), licensed MIT. It adds 50 tokens to every session and 224 once invoked, about $0.0003 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 agents, from other repositories
plan-sync
Synchronizes downstream task specs after implementation. Spawned by flow-next-work once per resolved wave. Do not invoke directly.
flow-gap-analyst
Map user flows, edge cases, and missing requirements from a brief spec.
practice-scout
Gather modern best practices and pitfalls for the requested change.
Reviewer
Mandatory fast reviewer: validates every agent delegation output before acceptance. Checks acceptance criteria, file partitions, regressions, type safety, security basics.
Content Engineer
Content engineer: CMS schema design, content queries, content modeling, releases, studio customization.
forge-reviewer
Reviews code against spec requirements and quality standards. Returns PASS or ISSUES with file:line references and severity levels. Dispatched after task implementation.