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-testgengit 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.00049 | $0.00240 |
| Opus 5 | $0.00024 | $0.00120 |
| Sonnet 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 yesterday.
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.
- yesterday 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 2d ago), licensed MIT. It adds 49 tokens to every session and 240 once invoked, about $0.0002 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.
observability-scout
Used by /flow-next:prime to scan for observability setup including logging, tracing, metrics, and health endpoints. Do not invoke directly.
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-speccer-validator
Pre-planning path-validation gate. Scans a spec file for path tokens inside code fences or backticks, checks each against the target repo, and returns REPLANNEEDED with (spec-line, missing-path) pairs when any are missing. Invoked automatically by /forge plan before forge-planner.