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 tahirraufkeeyu/software-development-agent-stack--sdas --skill ship-featuregit clone --depth 1 https://github.com/tahirraufkeeyu/software-development-agent-stack--sdasWrote 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/tahirraufkeeyu/software-development-agent-stack--sdas/ship-feature)<a href="https://agentmods.dev/skills/tahirraufkeeyu/software-development-agent-stack--sdas/ship-feature"><img src="https://agentmods.dev/badge/skills/tahirraufkeeyu/software-development-agent-stack--sdas/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/tahirraufkeeyu/software-development-agent-stack--sdas/ship-feature"><img src="https://agentmods.dev/badge/skills/tahirraufkeeyu/software-development-agent-stack--sdas/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.00061 | $0.02397 |
| Opus 5 | $0.00030 | $0.01198 |
| Sonnet 5 | $0.00012 | $0.00479 |
| Haiku 4.5 | $0.00006 | $0.00240 |
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 8d 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 — 213 lines — stays where its author put it; the contents beside it link to each section on GitHub.
When to use
- Developer has finished writing a feature but has not yet committed.
- User says "ship this", "get this ready to commit", "wrap this up", or "prep this for PR".
- A feature branch has uncommitted work and the user wants the full pre-commit gate (tests + review + message) in a single flow.
- A teammate asks to hand off work and wants a one-shot summary of what changed and whether it is safe to land.
Do not use this for multi-feature branches (run once per feature), merge conflict resolution, or releasing/tagging (see deploy-checklist). Do not use this to actually run git commit — this orchestrator produces the message, it does not execute the commit.
Chained skills
- test-writer — reads the new/changed production code, infers repo test conventions, generates AAA tests for every observable behaviour, and emits the test file path(s).
- code-review — reviews the combined diff (production + generated tests) against the security/correctness/performance/testing/observability checklist and returns severity-labelled findings.
- commit-message — takes the staged diff (now including tests) and produces a Conventional Commits subject plus body.
Inputs
- A path or glob identifying the changed production code (e.g.
src/pricing/discount.ts, or "whatever is ingit diff"). - Optional: the feature's ticket id (
JIRA-1234,GH-456) for the commit footer. - Optional: the target base branch if not
main/master(defaults to the repo's default branch).
Outputs
- Generated test file(s) written in the location dictated by the repo's convention (via test-writer).
.sdas/artifacts/developers/ship-feature-report.mdcontaining:- The list of test files generated and the behaviours they pin down.
- The full code-review output (verdict, findings table, inline suggestions).
- The proposed commit message (subject + body + footers) ready to paste into
git commit -F. - A final
Status:line:ready-to-commitorhalted-high-severity.
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.
- 8d ago First seen · 213 lines · 61 tokens per session scan A 21c41756d5b2
ship-feature is a skill published in the GitHub repository tahirraufkeeyu/software-development-agent-stack--sdas (18 stars, last pushed 4mo ago), licensed MIT. It adds 61 tokens to every session and 2,397 once invoked, about $0.0003 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-30.
Other skills, from other repositories
review-implement-phase
Implements triaged review actions, commits focused fixes, and posts Done plus resolves threads. Use when the user wants only the implementation phase of the review-framework workflow.
github-pr-workflow
Prepare a GitHub pull request from a feature branch — branch hygiene, commit shape, title/body, verification notes, screenshots for UI work, and replies to review comments.
review-delta
Review only changes since last commit using impact analysis. Token-efficient delta review with automatic blast-radius detection.
work-unit-commits
Plan commits as reviewable work units. Trigger: implementation, commit splitting, chained PRs, or keeping tests and docs with code.
github-contributor
End-to-end playbook for shipping high-quality pull requests to open-source projects you don't maintain — discovery, CONTRIBUTING compliance, PR-size check, minimal-diff implementation, PR description with AI-assisted disclosure, conflict resolution, and post-submission maintainer interaction. Use whenever creating…
pr-pending-feedback
Evaluate pending (unsubmitted) review comments on the current branch's PR and, after user confirmation, address each in a separate sub-agent and separate commit.