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-archive-taskgit 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-archive-task)<a href="https://agentmods.dev/skills/bonnguyenitc/specship/ss-archive-task"><img src="https://agentmods.dev/badge/skills/bonnguyenitc/specship/ss-archive-task/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-archive-task"><img src="https://agentmods.dev/badge/skills/bonnguyenitc/specship/ss-archive-task.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.00092 | $0.01074 |
| Opus 5 | $0.00046 | $0.00537 |
| Sonnet 5 | $0.00018 | $0.00215 |
| Haiku 4.5 | $0.00009 | $0.00107 |
Grade A, and why
ss-archive-task 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 — 35 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Archive Task
Goal: move a task out of the active working set by relocating its folder tasks/TASK-<ID>/ → tasks/archive/TASK-<ID>/, preserving every file and the full history. This keeps tasks/ focused on live work and stops finished/abandoned tasks from cluttering "current task" scans — without deleting anything.
ss-archive-task is a lifecycle skill, not a stage: it changes only the task's location (and logs why), never its stage or artifacts:. It's reversible — resume-task <ID> finds an archived task and restores it.
When to use
- A task is
doneand you want it off the active list. - A task is being abandoned/superseded and shouldn't show up as live work.
- The user asks to archive / shelve / put away a task.
- Not for tasks you'll resume soon (use
ss-pause-task— it stays in place) and never to delete history (archiving moves, never removes).
Shared task state
Part of the task pipeline — see ../WORKFLOW.md → "Task lifecycle". This skill writes tasks/ (it moves a folder); archived ids are retired and never reused for new tasks.
Method
Input: an optional task id argument in any form (archive-task TASK-20260723-fix-login, archive-task fix-login, archive-task 007), normalized to the on-disk folder name TASK-<ID>: a full TASK-… id as written; a bare all-digit argument maps to a legacy numeric folder matched as written (don't re-pad or strip leading zeros — 7 and 007 both resolve to TASK-007 if that's the folder); anything else (a slug fragment, or a ticket key like PROJ-123) resolves against tasks/TASK-* and tasks/archive/TASK-* folder names — an exact match (TASK-<argument>) wins, else a unique substring match; several matches → list candidates and ask; none → say so and stop — never fall back to auto-picking another task. A match already under tasks/archive/ needs nothing: report that it's archived and stop. No argument → resolve the current task (below).
- Locate the task: the normalized id argument, one named in conversation, else the most-recently-
updated:task undertasks/TASK-*(skiptasks/archive/*, and don't auto-pick astatus: pausedtask — to archive a paused one, name it explicitly). If ambiguous, list candidates and ask — don't guess. If the folder doesn't exist, say so; don't create anything. - Confirm intent — this moves a folder. State which task and its current
stage/status, then:- If
status: done→ proceed (still confirm once). But first check the draft shipped: ifreview.mdholds a commit/PR draft, look for a matching commit (git log) — if none exists, the work may be finished but unshipped; surface the draft to the user before archiving so it doesn't get buried inarchive/. - If not done (active / blocked / paused — unfinished work) → ask the user to confirm archiving unfinished work, and capture a reason (e.g. "superseded by TASK-20260722-parser-rewrite"). Never archive live work silently.
- If
- Log before moving — get the real time (
date "+%Y-%m-%d %H:%M %Z"), then intasks/TASK-<ID>/task.md: bumpupdated:and append a dated Pipeline Log line- <YYYY-MM-DD HH:MM +TZ> archived: <reason>— carrying your agent label (format:../WORKFLOW.md→ Agent handoff). Leavestageandartifacts:untouched. - Move the folder to
tasks/archive/TASK-<ID>/(createtasks/archive/if missing). Move the whole folder intact — every artifact comes along. Don'tgit rm/git mvor commit unless the user asks. - Confirm to the user: the task is archived at
tasks/archive/TASK-<ID>/, and/ss-resume-task <ID>restores it if needed.
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 · 35 lines · 92 tokens per session scan A cf9f1bcc0a57
ss-archive-task is a skill published in the GitHub repository bonnguyenitc/specship (2 stars, last pushed 1mo ago), licensed MIT. It adds 92 tokens to every session and 1,074 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
cyrus-setup-repository
Add one or more Git repositories to Cyrus configuration so it can process issues from those repos.
summarize
Format a final summary message for Linear. Your output is automatically streamed to the Linear agent session — just format it well, do not post it yourself.
cyrus-setup-linear
Create a Linear OAuth application and configure Cyrus to use it — supports agent-browser automation or guided manual setup.
issue-comment
Handle a non-build maintainer comment on an issue or PR — close, reopen, label, dedupe, answer a brief question, or triage. Action-only; redirect anything that needs code changes to /build.
chat
Conversational assistant for messaging-platform threads (Slack, Discord). Answer questions about repos, PRs, and issues, explain code, and guide users to the natural-language workflow triggers listed in the system prompt.
queue
A visible, editable Markdown work queue that agents drain autonomously — one task at a time or fanned out across parallel git worktrees — running each as a quick chore or the full feature-chain (design→prd→tdd→refine) with no user input. Use to queue, prioritize, stop/restart, seed from in-memory items, or…