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 agentmods add skills/bonnguyenitc/specship/ss-codingnpx skills add bonnguyenitc/specship --skill ss-codinggit 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-coding)<a href="https://agentmods.dev/skills/bonnguyenitc/specship/ss-coding"><img src="https://agentmods.dev/badge/skills/bonnguyenitc/specship/ss-coding.svg" alt="Measured on agentmods" 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 | $0.00077 | $0.02363 |
| Opus 5 | $0.00039 | $0.01182 |
| Sonnet 5 | $0.00015 | $0.00473 |
| Haiku 4.5 | $0.00008 | $0.00236 |
Grade A, and why
ss-coding 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 4d 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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Coding
Goal: execute the approved plan into working, clean code — one verifiable step at a time, matching the project's existing conventions.
When to use
- A plan exists (ideally from the
ss-planskill) and is approved. - You're asked to implement, build, or code up a feature.
- Third 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,plan.md,spec.md, anddocs/onboarding/how-to-code.md. Ifplan.mdis missing, runss-planfirst. - Checkpoint: as steps pass, tick
S#inplan.md; updatetask.md— setstage: coding,codingartifactin-progress→done, bumpupdated:, append a Pipeline Log line carrying your agent label (format:../WORKFLOW.md→ Agent handoff). - Blocked? If a step can't proceed because of an external dependency (an unmerged API, missing data/access, another team), set
status: blocked, note it inBlocked by:, and log it; flip back toactivewhen it clears. A blocker bug instead goes throughss-debug(which setsblockeditself).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).
Before you write
- Read
tasks/TASK-<ID>/plan.mdandspec.mdso every change traces to a planned step and a requirement. If they're missing, runss-plan/ss-specfirst. - Know the conventions: if
docs/onboarding/how-to-code.md/source-structure.mdexist, follow them (placement, naming, layer separation, error handling, imports); otherwise read neighbouring code and match its style. - Ask the user which approach they want — e.g. "Bạn muốn code theo TDD hay cách thông thường?":
- TDD — write a failing test first, then code to make it pass, then refactor (red → green → refactor).
- Thông thường (conventional) — implement first, then add tests to verify.
- If the user has no preference, default to whatever the codebase already does (if tests are pervasive, lean TDD); otherwise conventional. (Under
ss-ship, don't ask — apply this default directly.)
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.
- 4d ago First seen · 84 lines · 77 tokens per session scan A 27a6b467b05d
ss-coding is a skill published in the GitHub repository bonnguyenitc/specship (2 stars, last pushed 26d ago), licensed MIT. It adds 77 tokens to every session and 2,363 once invoked, about $0.0004 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-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.
image-to-code
Elite website image-to-code skill for Codex. For visually important web tasks, it must first generate the design image(s) itself, deeply analyze them, then implement the website to match them as closely as possible. In Codex, it must prefer large, readable, section-specific images instead of tiny compressed boards…
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.
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.