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 skills add sequant-io/sequant --skill solvegit 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/skills/sequant-io/sequant/solve)<a href="https://agentmods.dev/skills/sequant-io/sequant/solve"><img src="https://agentmods.dev/badge/skills/sequant-io/sequant/solve/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/solve"><img src="https://agentmods.dev/badge/skills/sequant-io/sequant/solve.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.00022 | $0.00669 |
| Opus 5.5 | $0.00009 | $0.00268 |
| Sonnet 5.5 | $0.00004 | $0.00134 |
| Haiku 4.5 | $0.00002 | $0.00067 |
Grade A, and why
solve 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 20d 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 — 82 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/solve/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/solvewithout forking it —overrides.mdlives under.claude/.local/, whichsequant updateandsyncnever overwrite.
/solve — Deprecated Alias for /assess
This command has been merged into /assess. Use /assess instead.
Deprecation Notice
When invoked as /solve <issue-numbers>, display this notice:
⚠ /solve is deprecated — use /assess instead.
/assess now includes workflow recommendations alongside health checks.
Running /assess for you...
Then immediately execute the full /assess workflow for the provided issue numbers, following the assess SKILL.md instructions exactly.
Behavior
/solve is functionally identical to /assess. The only difference is the deprecation notice shown before the assessment output.
/solve 152→ Shows deprecation notice, then runs/assess 152/solve 152 153→ Shows deprecation notice, then runs/assess 152 153
Migration
# Before (deprecated):
/solve 152
# After (preferred):
/assess 152
Comment Format
When persisting to issue comments, use the new assess: marker format:
<!-- assess:phases=spec,exec,qa -->
<!-- assess:action=PROCEED -->
<!-- assess:quality-loop=true -->
The old solve: markers are still parsed for backward compatibility, but new comments should use assess: markers.
Output Verification
After showing the deprecation notice, the output should follow the /assess output format exactly, including:
- Deprecation Notice — Shown before assessment output
- Action Headline —
→ ACTION — reason - Health Checks — Signals that informed the action
- Workflow Plan — Full CLI command with flags (for PROCEED)
- HTML Markers — Using
assess:prefix (notsolve:)
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.
- 20d ago Changed · +7 lines 745737f2bfdb
- 1mo ago First seen · 75 lines · 22 tokens per session scan A ce568d2bbd3f
solve is a skill published in the GitHub repository sequant-io/sequant (1 stars, last pushed 2d ago), licensed MIT. It adds 22 tokens to every session and 669 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
ai-development-guide
Applies language-agnostic and backend technical decision criteria, anti-pattern detection, debugging, and quality gates. Use when reviewing general/backend implementation choices, code smells, failures, or implementation completeness.
recipe-front-review
Reviews completed frontend implementation for governing-source compliance, scope economy, repository quality, and security, then applies user-approved React corrections.
recipe-review
Reviews completed implementation for governing-source compliance, scope economy, repository quality, and security, then applies user-approved corrections.
coding-principles
Language-agnostic coding principles for maintainability, readability, and quality. Use when implementing features, refactoring code, or reviewing code quality.
vertical-onboarding
Onboarding-and-switching playbook for SMB Product-Builder products. Defines the first-run experience that turns a prospect leaving an incumbent (ServiceTitan/Toast/Mindbody/Shopify/QuickBooks) into an activated user — import-first onboarding, the activation milestone, sample-data fallback, and the time-to-first-value…
spike-consumer-baseline
OI-3 spike harness — heavy consumer skill, BASELINE arm. Builds an incident post-mortem and sources the readability standard mid-workflow by reading a file directly, with NO Skill-tool call. Use only when explicitly invoked by the spike harness with a TRIALID and data path.