Borrowing it
Nothing to install: this file belongs to vicmaster/coide. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/vicmaster/coide/main/.claude/skills/ship-feature/SKILL.mdgit clone --depth 1 https://github.com/vicmaster/coideWrote 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/vicmaster/coide/ship-feature)<a href="https://agentmods.dev/skills/vicmaster/coide/ship-feature"><img src="https://agentmods.dev/badge/skills/vicmaster/coide/ship-feature/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/vicmaster/coide/ship-feature"><img src="https://agentmods.dev/badge/skills/vicmaster/coide/ship-feature.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.00031 | $0.00668 |
| Opus 5.5 | $0.00012 | $0.00267 |
| Sonnet 5.5 | $0.00006 | $0.00134 |
| Haiku 4.5 | $0.00003 | $0.00067 |
Grade A, and why
ship-feature 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 2mo 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 — 38 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ship Feature
Wrap up a completed feature: ensure tests exist and pass, commit all changes, move it from VISION.md's roadmap into SHIPPED.md, add to release notes, and push.
Instructions
- Run
git statusandgit diffto see all staged and unstaged changes - Verify tests exist for the feature:
- Look at the changed/added files and identify any new store actions, utility functions, or event parsing logic
- Check if corresponding test files already exist under
src/__tests__/ - If tests are missing for new logic, write Vitest tests before proceeding:
- Store actions →
src/__tests__/store/ - Utility functions →
src/__tests__/utils/ - Follow the existing test patterns (see
sessions.test.ts,diff.test.ts,mcpParsing.test.tsfor examples)
- Store actions →
- Pure UI components without logic don't require tests, but any extracted logic they use does
- Run the full test suite with
npx vitest run- If any test fails, fix the issue and re-run until all tests pass
- Do NOT proceed to commit if tests are failing
- Read
VISION.mdand find the unchecked item (- [ ]) under## Roadmapthat best matches: "$ARGUMENTS"- If no match is found, list the unchecked items and ask which one (or skip — polish/bug fixes don't always map to a roadmap item)
- Move the matched item to
SHIPPED.md:- Remove the
- [ ]line from VISION.md's## Roadmapsection - Append the item (without the
[ ]checkbox, just- Feature name — description) to the appropriate section inSHIPPED.md(e.g.## Core Roadmap (shipped)or## Copycat — Features parity with Claude Code CLI (shipped)); if no section fits, add to a## Misc (shipped)section, creating it if absent - If step 4 was skipped (no roadmap match), do NOT touch VISION.md or SHIPPED.md in this step
- Remove the
- Update release notes in
src/renderer/src/data/releaseNotes.ts:- Always append a one-line description to the first entry's
notesarray (regardless of what version it shows — the release script renames it on release) - Keep note descriptions concise (under 80 chars), user-facing language (not implementation details)
- Always append a one-line description to the first entry's
- Stage all relevant changed files (including the VISION.md/SHIPPED.md updates, release notes update, and any new test files)
- Write a commit message that describes the feature work done (based on the actual code changes), NOT just "mark as done"
- Commit and push to origin
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.
- 2mo ago First seen · 38 lines · 31 tokens per session scan A 67d47be6dffc
ship-feature is a skill published in the GitHub repository vicmaster/coide (12 stars, last pushed 11d ago), licensed MIT. It adds 31 tokens to every session and 668 once invoked, about $0.0001 per session on Opus 5.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
batch
Research and plan a large-scale change, then execute it in parallel across 5–30 isolated worktree agents that each open a PR.
team-release
Orchestrate the release team — release-manager, qa-lead, devops-engineer, producer — to execute a release from candidate to deployment.
shiplog
Recap of everything shipped since the last run - cross-repo PRs, security fixes, star deltas, and X traction, synthesized into a digest article and a ready-to-post shiplog in your voice.
close-task-commit-push-pr
Close the active backlog task (detected from branch name), commit all changes, push to remote, and open a pull request. Use when the user says "close task and ship it", "close task commit push pr", or invokes /close-task-commit-push-pr.
github-project-management
GitHub project management with issue tracking, project-board automation, and sprint planning. Use when triaging or organizing issues, automating a project board, planning a sprint, or running release/roadmap coordination on GitHub.
gh-cli
GitHub CLI (gh) reference for repos, issues, PRs, Actions, releases, gists, projects, codespaces, and the API.