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-debugnpx skills add bonnguyenitc/specship --skill ss-debuggit 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-debug)<a href="https://agentmods.dev/skills/bonnguyenitc/specship/ss-debug"><img src="https://agentmods.dev/badge/skills/bonnguyenitc/specship/ss-debug.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.1 | $0.00097 | $0.02052 |
| Opus 5 | $0.00048 | $0.01026 |
| Sonnet 5 | $0.00019 | $0.00410 |
| Haiku 4.5 | $0.00010 | $0.00205 |
Grade A, and why
ss-debug 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 6d 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 — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Debug
Goal: find the root cause of a defect and fix it with the smallest correct change — never patch symptoms. Record the investigation so it's not lost.
When to use
- A test fails, the app misbehaves, or a regression appears.
- Asked to "debug", "fix this bug", or "why is this failing".
- Can be triggered at any point in the workflow (during
coding, duringreview, or on a bug found later).
Shared task state
Part of the task pipeline — see ../WORKFLOW.md for the full contract. ss-debug attaches to a task rather than being a fixed pipeline stage.
- Hydrate: resolve the owning
TASK-<ID>(see "Attach the bug to a task" below), read itstask.md, andspec.md/plan.mdas needed. If no task owns it, create a new one. - Checkpoint: append the
BUG#entry todebug.md; updatetask.md— setdebugartifactopen-bugs/clear, setstatus: blockedwhile a blocker bug is open (note it inBlocked by:), bumpupdated:, append a Pipeline Log line carrying your agent label (format:../WORKFLOW.md→ Agent handoff). Clear back toactivewhen fixed and return to the stage you came from. (blockedis involuntary; see../WORKFLOW.md→ Status values.) - Lessons: read
tasks/LESSONS.mdat hydrate and apply its rules; if the bug's root cause was a process mistake (e.g. a skipped verify, a stale plan), fix the process trace too and append anL#entry there (see../WORKFLOW.md→ Lessons).
Attach the bug to a task
- If the bug belongs to an existing task (it's in code that task touched, or found during its
coding/review): track it in that task's folder →tasks/TASK-<ID>/debug.md. - If it's a standalone bug with no task: create a new
tasks/TASK-<ID>/(from a ticket id, or generated per../WORKFLOW.md→ "ChoosingTASK-<ID>") and record it there. Aspec.mdis optional for a pure bugfix, but always keep the debug record. - If unsure which task owns it, ask the user before picking.
Method — scientific debugging
Work from evidence, one hypothesis at a time. Don't guess-and-change.
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.
- 6d ago First seen · 83 lines · 97 tokens per session scan A 48a348b7af08
ss-debug is a skill published in the GitHub repository bonnguyenitc/specship (2 stars, last pushed 28d ago), licensed MIT. It adds 97 tokens to every session and 2,052 once invoked, about $0.0005 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
debug
Full debugging workflow — reproduce the bug with a failing test, perform root cause analysis, then implement a minimal fix.
special-cute-coder-wife
可爱编码大神媳妇 - 技术超群之温柔编程伴侣，用甜蜜温柔之方式激发老公斗志，专业与可爱完美平衡.
shaman-linus
开源思维，技术实用主义，代码至上.
debug-systematically
Use this skill when diagnosing a bug, unexpected behavior, test failure, or any situation where code does not behave as expected. Follow a structured debugging process instead of randomly changing code.
fixing
Diagnose why a PR's CI failed — compare the CI definition against the sandbox, classify the failure, and make the minimal repair. Use when a PR is red and you must work out why before changing anything.
lastlight-debug
Debug a running Last Light instance over its admin API with the lastlight CLI — no SSH. Use when the user wants to "look at / debug a failed or stuck workflow", "why didn't the bot do X", "check a bad agent run / phase error on ", "tail a session", "search the logs", "read the server/docker logs", "list/trigger a…