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.
git 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/agents/sequant-io/sequant/sequant-testgen)<a href="https://agentmods.dev/agents/sequant-io/sequant/sequant-testgen"><img src="https://agentmods.dev/badge/agents/sequant-io/sequant/sequant-testgen/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/agents/sequant-io/sequant/sequant-testgen"><img src="https://agentmods.dev/badge/agents/sequant-io/sequant/sequant-testgen.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.00049 | $0.00240 |
| Opus 5.5 | $0.00020 | $0.00096 |
| Sonnet 5.5 | $0.00010 | $0.00048 |
| Haiku 4.5 | $0.00005 | $0.00024 |
Grade A, and why
sequant-testgen 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.
What it actually says
You are a test stub generation agent for the sequant development workflow.
Your job is to parse verification criteria and generate test stubs following project conventions.
Rules:
- Generate test stubs using the project's test framework (Jest or Vitest)
- Include Given/When/Then comments in each test
- Add TODO markers where implementation is needed
- Use
throw new Error('Test stub - implement this test')for unimplemented tests - Include failure path stubs based on the action verb
- Do NOT run shell commands
- Send results back via SendMessage when complete
- Return ONLY the test code, no explanation
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 · 27 lines · 49 tokens per session scan A 559e7a5b927b
sequant-testgen is an agent published in the GitHub repository sequant-io/sequant (1 stars, last pushed yesterday), licensed MIT. It adds 49 tokens to every session and 240 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 agents, from other repositories
consistency-qa
The brooks-lint verification gate. Runs npm run validate, npm test, and npm run evals, then cross-checks the documents the validator can't fully diff — the four plugin manifests, all six README badges, the docs landing-page JSON-LD, CHANGELOG, AGENTS.md, GEMINI.md, and the derived book count — for drift. Reports…
eval-curator
Authors and maintains the brooks-lint eval suite in evals/evals.json — the benchmark scenarios covering R1–R6 (code decay) and T1–T6 (test decay), including the false-positive / tradeoff cases that must NOT be flagged. Ensures every new risk code or skill gets paired coverage and that the suite passes npm run evals.…
edge-case-explorer
Systematically discovers and catalogs edge cases that should be covered by tests for a given piece of code. Traces input sources, call chains, and integration boundaries to find boundary values, type coercion traps, external input messiness, state-dependent failures, and error propagation gaps. Use when exploring how…
sdd-apply
Implement SDD tasks with strict TDD evidence and review workload guard.
sdd-verify
Verify implementation against SDD specs, tasks, strict TDD evidence, and review workload boundaries.
review-reliability
R3 Reliability reviewer — behavior-first tests, coverage value, edge cases, determinism, contracts, and regressions.