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 signalridge/slipway --skill clarifygit clone --depth 1 https://github.com/signalridge/slipwayWrote 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/signalridge/slipway/clarify)<a href="https://agentmods.dev/skills/signalridge/slipway/clarify"><img src="https://agentmods.dev/badge/skills/signalridge/slipway/clarify/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/signalridge/slipway/clarify"><img src="https://agentmods.dev/badge/skills/signalridge/slipway/clarify.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.00020 | $0.00281 |
| Opus 5.5 | $0.00008 | $0.00112 |
| Sonnet 5.5 | $0.00004 | $0.00056 |
| Haiku 4.5 | $0.00002 | $0.00028 |
Grade A, and why
slipway-clarify 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 1mo 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.
What it actually says
Slipway Clarify
Use this capability only when the user explicitly invokes it, or when an explicitly started Run returns a Clarify Action. Ordinary conversation must not start it ambiently.
{{ template "interview" . }}
Inside an already-started Run, if the interview adds or changes the execution understanding, summarize the current shared understanding and ask for its explicit confirmation as the single question of the current Clarify Action; the confirmation enters decision context only through the CLI's structured answer-decision variant. This is only a consent boundary for the changed understanding—not readiness, quality, Issue status, or delivery certification. If no interview was needed, the original explicit Run request is sufficient and must not trigger duplicate confirmation.
Standalone Clarify never grants implementation authority: end with a summary and wait for a separate explicit Run or Implement invocation. Do not implement, write files, create or edit Issues, persist the transcript, or preserve proposals superseded by later answers as if they remained current. Clarification is stateless; documentation is a separate explicitly invoked tool such as grill-with-docs, not a Slipway capability.
Use the decision interview reference for this discipline's provenance and licence.
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.
- 1mo ago First seen · 18 lines · 20 tokens per session scan A 6391b3ff1edb
slipway-clarify is a skill published in the GitHub repository signalridge/slipway (23 stars, last pushed yesterday), licensed BSD-3-Clause. It adds 20 tokens to every session and 281 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-30.
Other skills, from other repositories
repo-hygiene
Use when the scheduled repo-hygiene workflow runs from GitHub Actions (or an operator dry-run) to scan the repository for small, certain docs/test/code hygiene issues and fix them as one batched branch.
test-failure-explorer
Import and query an existing Vitest 3.2 JSON report to explore test failures, file-level errors and original diagnostic evidence.
requirements-writer
Use when converting PM intake into a slice SPEC.md with observable acceptance outcomes, explicit scope, and advisory sibling build dependencies.
refocusing
Use when a long-running agent may have lost the product outcome, when context was compacted, when work has crossed a major boundary, or when a fresh path-based trace is needed before the next consequential action. Not for fresh-session orientation, waking an idle seat, or checkpoints.
orchestration-team
Use when coordinating assignments, selected review boundaries, or blocked work across a rig.
oversight-team
Use when you are a seat on the oversight pod (a standing monitor-mode rig that keeps OTHER rigs healthy), configuring or running the drift detectors, or choosing whether to intervene vs escalate. Covers the pull-not-poll posture, the v0 detectors (premature-park, process-drift, off-task, token-burn), the intervention…