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/fullsolveWrote 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/fullsolve)<a href="https://agentmods.dev/skills/sequant-io/sequant/fullsolve"><img src="https://agentmods.dev/badge/skills/sequant-io/sequant/fullsolve/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/fullsolve"><img src="https://agentmods.dev/badge/skills/sequant-io/sequant/fullsolve.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.00023 | $0.11089 |
| Opus 5.5 | $0.00009 | $0.04436 |
| Sonnet 5.5 | $0.00005 | $0.02218 |
| Haiku 4.5 | $0.00002 | $0.01109 |
Grade A, and why
fullsolve 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 11d 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 — 1,161 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/fullsolve/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/fullsolvewithout forking it —overrides.mdlives under.claude/.local/, whichsequant updateandsyncnever overwrite.
Full Solve Command
You are the "Full Solve Agent" for the current repository.
Purpose
When invoked as /fullsolve <issue-number>, execute the complete issue resolution workflow with integrated quality loops. This command orchestrates all phases and automatically iterates until quality gates pass.
CRITICAL: Auto-Progression Between Phases
DO NOT wait for user confirmation between phases. This is an autonomous workflow — through PR creation.
After each phase completes successfully, immediately proceed to the next phase:
/speccompletes → immediately invoke/exec/execcompletes → immediately invoke/test(if UI) or/qa/testcompletes → immediately invoke/qa/qacompletes → immediately create the PR and post the final summary
The workflow's terminal state is PR created + final summary posted — not merged. Merging (§5.3), post-merge verification (§5.4), and the auto-merge-path lock release (§5.5) run only when --auto-merge is passed, run.autoMerge is true in .sequant/settings.json, or the user has explicitly instructed a merge in this conversation (invoking /fullsolve alone does not count). Without one of those, /fullsolve stops after the final summary — the PR is left open for human review. See "Merge Gate" below for how this is resolved, and §5.3 for the gate itself.
The user invoked /fullsolve expecting end-to-end automation up to a mergeable PR. Only stop for:
- Unrecoverable errors (after retry attempts exhausted)
- Final summary after PR creation — this is the workflow's terminal state, not a pause
- Explicit user interruption
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.
- 11d ago Changed · -3 lines cee5b89bdef9
- 16d ago Changed · +51 lines c2ebf8f42336
- 18d ago Changed · -1 lines 1a5ea5fd45d8
- 1mo ago First seen · 1,114 lines · 23 tokens per session scan A 5dba6cd9f192
fullsolve is a skill published in the GitHub repository sequant-io/sequant (1 stars, last pushed today), licensed MIT. It adds 23 tokens to every session and 11,089 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…
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.
spike-consumer-adversarial
OI-3 spike harness — heavy consumer, ADVERSARIAL arm. Worst-case early-exit test: the mid-workflow Skill call has no continuation guardrail and the guidance skill ends with a final-sounding anchor. Use only when explicitly invoked by the spike harness with a TRIALID and data path.
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.