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 workflowgit 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/workflow)<a href="https://agentmods.dev/skills/signalridge/slipway/workflow"><img src="https://agentmods.dev/badge/skills/signalridge/slipway/workflow/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/workflow"><img src="https://agentmods.dev/badge/skills/signalridge/slipway/workflow.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 48 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
- medium Excessive Agency · line 91 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00041 | $0.02929 |
| Opus 5 | $0.00020 | $0.01465 |
| Sonnet 5 | $0.00008 | $0.00586 |
| Haiku 4.5 | $0.00004 | $0.00293 |
Grade A, and why
slipway-workflow 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 9d 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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Slipway Workflow
Use this capability only when the user explicitly asks to run the Slipway workflow, take an idea to a work-item draft, or orient existing Slipway work to its next function. One invocation authorizes only the guidance work for the current stage: inspect current facts, resolve genuine human decisions, and synthesize a draft when one is needed. It does not authorize an external write, Objective decomposition, implementation, or a Run. Ordinary conversation must never start it.
This capability is stateless only in the Slipway sense: it opens no Run, writes no journal, and creates no durable pipeline cursor. Conversation, documents, tracker artifacts, prototypes, and repository edits are still state and side effects. The workflow itself is read-only. It may read an existing external or unmanaged artifact as non-authoritative planning input, but a valid managed Objective, Change, or Run record retains the routing and source authority defined by the contract. It never creates or modifies an artifact as a detour.
Orchestrate Slipway functions, not installed skills
Coordinate the product functions defined by Slipway's Issue workflow: clarification, publication, Objective decomposition, Run start or resume, and the Run-owned Implement and Review loop. Do not discover, rank, or dispatch the host's general skill catalog. Do not invoke a sibling slipway-* capability; every sibling remains a user-invoked boundary and must be named for the user to invoke explicitly.
The workflow is self-contained and must work when no Matt Pocock skill is installed. Never invoke a user-only external front door such as /grill-me or /wayfinder. Do not invoke an external implementation or review skill even when it is model-reachable: after the Change handoff, Slipway Run owns execution and advisory Review. The only optional external primitive this workflow may invoke is an already-installed, model-invocable /grilling interview. Missing primitives never block the workflow and never trigger installation or enablement.
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.
- 9d ago First seen · 102 lines · 41 tokens per session scan A 09c1dafa5d26
slipway-workflow is a skill published in the GitHub repository signalridge/slipway (23 stars, last pushed yesterday), licensed BSD-3-Clause. It adds 41 tokens to every session and 2,929 once invoked, about $0.0002 per session on Opus 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.
find-simplifications
Use for a periodic repo-wide sweep of qwen-code for accumulated excess surface — dead components and files, orphaned locale keys, exports nothing consumes, added-then-removed scaffolding — filing candidates on a tracking issue and landing only what a maintainer has said yes to. Repo-wide and evidence-first; every…
autoprompt
Explicit-only useful-first orchestration. Invoke only when the user names autoprompt - typed as /autoprompt or in plain language such as "act in autoprompt mode" - to turn a mission into one executable roadmap, build dependency-safe lanes, and verify the result with independent reviewers. Do not infer invocation from…
autoprompt
Explicit-only useful-first orchestration. Invoke /autoprompt to turn a mission into one executable roadmap, build dependency-safe lanes, and verify the result with independent reviewers. Never infer invocation from ordinary requests. Never resume from leftover artifacts without an explicit resume instruction.
autoprompt
Explicit-only useful-first orchestration. Invoke /autoprompt to turn a mission into one executable roadmap, build dependency-safe lanes, and verify the result with independent reviewers. Never infer invocation from ordinary requests. Never resume from leftover artifacts without an explicit resume instruction.
autoprompt
Explicit-only useful-first orchestration. Invoke /autoprompt to turn a mission into one executable roadmap, build dependency-safe lanes, and verify the result with independent reviewers. Never infer invocation from ordinary requests. Never resume from leftover artifacts without an explicit resume instruction.