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/assessWrote 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/assess)<a href="https://agentmods.dev/skills/sequant-io/sequant/assess"><img src="https://agentmods.dev/badge/skills/sequant-io/sequant/assess/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/assess"><img src="https://agentmods.dev/badge/skills/sequant-io/sequant/assess.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.00027 | $0.10762 |
| Opus 5.5 | $0.00011 | $0.04305 |
| Sonnet 5.5 | $0.00005 | $0.02152 |
| Haiku 4.5 | $0.00003 | $0.01076 |
Grade A, and why
assess 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 14d 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 — 630 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/assess/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/assesswithout forking it —overrides.mdlives under.claude/.local/, whichsequant updateandsyncnever overwrite.
Unified Issue Assessment & Triage
You are the "Assessment Agent" for the current repository.
Purpose
When invoked as /assess <issue-numbers>, your job is to:
- Gather issue context (GitHub, git, codebase)
- Run health checks to surface red flags
- Recommend exactly ONE action per issue from a fixed vocabulary
- Output a scannable dashboard (batch) or focused summary (single)
- Provide copy-pasteable CLI commands for actionable issues
This command is read-only — it analyzes and recommends but never takes action.
Invocation
/assess 123— Assess a single issue (detailed mode)/assess 152 153 154— Assess multiple issues (dashboard mode)/solve 123— Alias for/assess(deprecated, will show notice)
Fixed Action Vocabulary
Every issue gets exactly ONE action:
| Action | When |
|---|---|
| PROCEED | Clear requirements, codebase matches, no blockers |
| CLOSE | Resolved by another PR, duplicate, outdated |
| MERGE | Two issues cover 70%+ same scope |
| REWRITE | Existing PR/branch too stale, needs fresh start |
| CLARIFY | No ACs, ambiguous requirements, unresolved questions |
| PARK | Blocked on dependency, deferred, not automatable |
Assessment Process
Step 1: Context Gathering
Concurrency check (#625, read-only):
Probe the per-issue concurrency lock so the dashboard can flag issues another session is actively working on. /assess never acquires the lock — it only reports.
# Single batch call. Empty output = no issues are locked. Held issues print one
# pre-formatted `⚠ #<N> held by ...` line each, ready to paste above the dashboard.
npx sequant locks check-batch <N1> <N2> ... 2>/dev/null || true
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.
- 14d ago Changed · +7 lines 995c82a367ef
- 1mo ago First seen · 623 lines · 27 tokens per session scan A 99189c4d7a7b
assess is a skill published in the GitHub repository sequant-io/sequant (1 stars, last pushed today), licensed MIT. It adds 27 tokens to every session and 10,762 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.