Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/sequant-io/sequantnpx agentmods add skills/sequant-io/sequant/loopWrote 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/loop)<a href="https://agentmods.dev/skills/sequant-io/sequant/loop"><img src="https://agentmods.dev/badge/skills/sequant-io/sequant/loop/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/loop"><img src="https://agentmods.dev/badge/skills/sequant-io/sequant/loop.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.00016 | $0.07564 |
| Opus 5.5 | $0.00006 | $0.03026 |
| Sonnet 5.5 | $0.00003 | $0.01513 |
| Haiku 4.5 | $0.00002 | $0.00756 |
Grade A, and why
loop 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 15d 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.
How it starts
The opening of the file, as written. The whole thing — 721 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/loop/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/loopwithout forking it —overrides.mdlives under.claude/.local/, whichsequant updateandsyncnever overwrite.
Quality Loop Command
You are the "Quality Loop Agent" for the current repository.
Purpose
When invoked as /loop <issue-number>, your job is to:
- Read the previous phase output from
/tmp/claude-issue-<N>.log - Parse findings from the last
/testor/qaphase - Fix the identified issues
- Re-run validation until quality gates pass
- Exit when
READY_FOR_MERGEor max iterations reached
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 | loop |
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):
- Use provided worktree - Work in
SEQUANT_WORKTREEpath directly - Use
SEQUANT_ISSUE- Skip issue number parsing from invocation - Reduce GitHub comment frequency - Defer updates to orchestrator
- Trust embedded context - when the orchestrator injected a
<!-- SEQUANT_PROMPT_CONTEXT -->block into this invocation, it is the authoritative QA-findings source; do not re-fetch from GitHub (see Step 1A below)
Behavior when standalone (SEQUANT_ORCHESTRATOR is NOT set):
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.
- 15d ago Changed · +1 lines 6db97d13f731
- 21d ago Changed · -1 lines 05e36ccd2873
- 26d ago Changed · +39 lines 6b55116fc5f9
- 1mo ago Changed · +38 lines f143344324da
- 1mo ago First seen · 644 lines · 16 tokens per session scan A 3f351e2f9e72
loop is a skill published in the GitHub repository sequant-io/sequant (1 stars, last pushed today), licensed MIT. It adds 16 tokens to every session and 7,564 once invoked, about $0.0001 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 skills, from other repositories
brooks-test
Test quality review drawing on twelve classic engineering books — with primary focus on xUnit Test Patterns, The Art of Unit Testing, How Google Tests Software, and Working Effectively with Legacy Code — that diagnoses structural problems in an existing test suite: brittleness, mock abuse, coverage illusions, slow…
improve-code-quality
Guided journey from a working-but-untested vibe-coded prototype to a production-ready product with tests, clean structure, a business-rules boundary, and resilience at scale. Orchestrates nine skills phase by phase - working-with-legacy-code, clean-code, refactoring-patterns, software-design-philosophy…
crap-analyzer
Use to produce a risk-based refactor + test plan for recently-changed code on a diff/branch/PR by computing CRAP (complexity × untested) on changed methods. Multi-language — TypeScript, JavaScript, Python, Java, Kotlin, Go, Ruby, C#, Rust, PHP — auto-discovers how the repo generates coverage. Triggers …
pre-pr-audit
Pre-PR confidence audit with 5-dimension scoring. Use when: final check before commit/push/PR, evaluating PR readiness, assessing test quality + risk + coverage holistically. Triggers: pre-pr, readiness check, confidence audit, final verification, ready to PR, how confident. Not for: code review (use…
vibe-gap-analysis
Assesses production readiness or audits a codebase against its specs. Supports quick static mode, deep 17-dimension audit, or single-dimension focus. Use before a production launch, after a major refactor, when inheriting a codebase, or when someone asks how done the project is.
hermit-scribe
File a GitHub issue or post a comment on an existing issue via a GitHub App bot identity. Use when the operator says "file as a GH issue", "open an issue for PROP-NNN", "report this to the tracker", "add a comment to issue.