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 bonnguyenitc/specship --skill ss-plangit clone --depth 1 https://github.com/bonnguyenitc/specshipWrote 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/bonnguyenitc/specship/ss-plan)<a href="https://agentmods.dev/skills/bonnguyenitc/specship/ss-plan"><img src="https://agentmods.dev/badge/skills/bonnguyenitc/specship/ss-plan/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/bonnguyenitc/specship/ss-plan"><img src="https://agentmods.dev/badge/skills/bonnguyenitc/specship/ss-plan.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.00086 | $0.02274 |
| Opus 5 | $0.00043 | $0.01137 |
| Sonnet 5 | $0.00017 | $0.00455 |
| Haiku 4.5 | $0.00009 | $0.00227 |
Grade A, and why
ss-plan scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- For each step define: **what changes**, **which files** (`path`), and a **verify** check. The `verify:` must be **executable, not a description** — a concrete command or test the coding loop can run and read a pass/fai How it starts
The opening of the file, as written. The whole thing — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plan
Goal: turn an understood spec into a concrete, ordered implementation plan — small steps, each independently verifiable — before any code is written.
When to use
- The spec is understood (ideally via the
ss-specskill) and you're ready to design. - You're asked to break a feature into steps or weigh implementation approaches.
- Second stage of the workflow: spec → plan → coding → review (+
debug).
Shared task state
Part of the task pipeline — see ../WORKFLOW.md for the full contract.
- Hydrate: resolve the active
TASK-<ID>, readtasks/TASK-<ID>/task.md+spec.md, plusdocs/onboarding/{source-structure,how-to-code}.mdif present. Ifspec.mdis missing orstatus: draftwith open blockers, runss-specfirst. - Checkpoint: write
plan.md, then updatetask.md— setstage: plan,planartifactdraft→approved, bumpupdated:, append a Pipeline Log line carrying your agent label (format:../WORKFLOW.md→ Agent handoff). - Blocked? If planning can't be finalized because of an unresolved blocker
Q#or an external dependency (an API/data/decision the plan hinges on), setstatus: blocked, note it inBlocked by:, and log it; flip back toactivewhen it clears.blockedis involuntary — to set the task aside by choice, usess-pause-task. See../WORKFLOW.md→ Status values. - Lessons: read
tasks/LESSONS.mdat hydrate and apply its rules; if you detect a process mistake, fix it and append anL#entry there (see../WORKFLOW.md→ Lessons).
Method
1. Read the inputs
- Read
tasks/TASK-<ID>/spec.md(produced byss-spec) — every step must trace to a requirement or acceptance criterion in it, and its Assumptions can decide the design, so read them too. If it's missing, runss-specfirst. - Know where the code will live and the patterns to follow: reuse
docs/onboarding/source-structure.mdandhow-to-code.mdif present, or runss-explore-sourceif the project is unfamiliar. - Open the actual files the plan will touch — confirm the functions, signatures, and patterns the steps rely on really exist as you believe. A plan referencing imagined code doesn't fail now; it fails at
coding, where it's more expensive. - Delegate wide reads to a subagent. If confirming the plan's assumptions requires broad exploration (an unfamiliar area, many candidate files), spawn the
ss-exploreragent if your platform can spawn it (ships with specship for Claude Code), else the built-in Explore agent, for the fan-out and keep only its conclusions in this thread - but still open the specific files the steps touch yourself, and verify any path or symbol an agent reports before the plan relies on it. If your platform can't spawn subagents, do the exploration inline in this thread instead (../WORKFLOW.md→ In-stage subagents: delegation is an optimization, never a precondition).
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.
- 9d ago First seen · 94 lines · 86 tokens per session scan A 1553bc969f17
ss-plan is a skill published in the GitHub repository bonnguyenitc/specship (2 stars, last pushed 1mo ago), licensed MIT. It adds 86 tokens to every session and 2,274 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
design-taste-frontend
Anti-slop frontend skill for landing pages, portfolios, and redesigns. The agent reads the brief, infers the right design direction, and ships interfaces that do not look templated. Real design systems when applicable, audit-first on redesigns, strict pre-flight check.
html-artifacts
Author the HTML for a plan artifact, dashboard iframe, or Slack attachment — structure, design plan, available runtime, theming, and craft. Read this before writing HTML for saveplan, outputiframe, or slackattachhtml.
design-taste-frontend-v1
The original v1 taste-skill, preserved for projects depending on its exact behavior. The current default is design-taste-frontend (v2 experimental), which is a substantial rewrite. Use this v1 install name only if you need exact backward compatibility.
brandkit
Premium brand-kit image generation skill for creating high-end brand-guidelines boards, logo systems, identity decks, and visual-world presentations. Trained for minimalist, cinematic, editorial, dark-tech, luxury, cultural, security, gaming, developer-tool, and consumer-app brand systems. Optimized for intentional…
redesign-existing-projects
Upgrades existing websites and apps to premium quality. Audits current design, identifies generic AI patterns, and applies high-end design standards without breaking functionality. Works with any CSS framework or vanilla CSS.
gpt-taste
Elite UX/UI & Advanced GSAP Motion Engineer. Enforces Python-driven true randomization for layout variance, strict AIDA page structure, wide editorial typography (bans 6-line wraps), gapless bento grids, strict GSAP ScrollTriggers (pinning, stacking, scrubbing), inline micro-images, and massive section spacing.