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 skills/sequant-io/sequant/testnpx skills add sequant-io/sequant --skill testgit 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.00010 | $0.06031 |
| Opus 5 | $0.00005 | $0.03016 |
| Sonnet 5 | $0.00002 | $0.01206 |
| Haiku 4.5 | $0.00001 | $0.00603 |
Grade A, and why
test 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.
How it starts
The opening of the file, as written. The whole thing — 822 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/test/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/testwithout forking it —overrides.mdlives under.claude/.local/, whichsequant updateandsyncnever overwrite.
Browser Testing Command
You are the "Testing Agent" for the current repository.
Purpose
When invoked as /test <issue-number>, execute structured browser-based testing for admin features that require manual QA validation.
When This Phase Runs
The /test phase is invoked by /fullsolve based on issue labels:
| Label | Effect |
|---|---|
ui, frontend, admin |
/test phase runs automatically |
no-browser-test |
/test phase is skipped (explicit opt-out, overrides UI labels) |
| Neither | /test is skipped; /spec may suggest adding ui label if .tsx files detected |
Workflow:
- Setup Phase: Fetch Issue, prepare test data, start dev server
- Execution Phase: Run tests systematically with browser automation
- Reporting Phase: Generate test results and GitHub comment
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 | test |
SEQUANT_ISSUE |
Issue number being processed | 123 |
SEQUANT_WORKTREE |
Path to the feature worktree | /path/to/worktrees/feature/... |
Behavior when orchestrated (SEQUANT_ORCHESTRATOR is set):
- Skip issue fetch - Use
SEQUANT_ISSUEdirectly, orchestrator has context - Use provided worktree - Work in
SEQUANT_WORKTREEpath - Reduce GitHub comment frequency - Defer progress updates to orchestrator
- Trust dev server status - Orchestrator may have started it already
What ships with it
1 file 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.
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 · 822 lines · 10 tokens per session scan A 7ff0847cdeef
test is a skill published in the GitHub repository sequant-io/sequant (1 stars, last pushed yesterday), licensed MIT. It adds 10 tokens to every session and 6,031 once invoked, about $0.0001 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 skills, from other repositories
agent-estate
Perpetual autonomous work loop for Claude Code — no end condition, no memory regression, no context overfill. Maintains a persistent ledger across all sessions.
citation-audit
Zero-context verification that every bibliographic entry in the paper is real, correctly attributed, and used in a context the cited paper actually supports — catching hallucinated authors, wrong years, fabricated venues, version mismatches, and wrong-context citations. Use when user says "审查引用", "check citations"…
paper-illustration
Generate publication-quality AI illustrations for academic papers using Gemini image generation. Creates architecture diagrams, method illustrations with Claude-supervised iterative refinement loop. Use when user says "生成图表", "画架构图", "AI绘图", "paper illustration", "generate diagram", or needs visual figures for papers.
paper-illustration-image2
Generate publication-quality academic illustrations through a local Codex app-server bridge that uses Codex native image generation. This is a separate experimental alternative to paper-illustration, intended for Claude Code users who want a GPT-image-style renderer without modifying the original skill.
experiment-plan
Turn a refined research proposal or method idea into a detailed, claim-driven experiment roadmap. Use after research-refine, or when the user asks for a detailed experiment plan, ablation matrix, evaluation protocol, run order, compute budget, or paper-ready validation that supports the core problem, novelty…
paper-writing
Workflow 3: Full paper writing pipeline that goes from a narrative report to a polished, submission-ready PDF. Use when user says "写论文全流程", "write paper pipeline", "从报告到PDF", "paper writing", or wants the complete paper generation workflow.