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 uthumany/uthy-legacy-os --skill feature-ship-cyclegit clone --depth 1 https://github.com/uthumany/uthy-legacy-osWrote 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/uthumany/uthy-legacy-os/feature-ship-cycle)<a href="https://agentmods.dev/skills/uthumany/uthy-legacy-os/feature-ship-cycle"><img src="https://agentmods.dev/badge/skills/uthumany/uthy-legacy-os/feature-ship-cycle/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/uthumany/uthy-legacy-os/feature-ship-cycle"><img src="https://agentmods.dev/badge/skills/uthumany/uthy-legacy-os/feature-ship-cycle.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.00035 | $0.00785 |
| Opus 5 | $0.00017 | $0.00392 |
| Sonnet 5 | $0.00007 | $0.00157 |
| Haiku 4.5 | $0.00003 | $0.00078 |
Grade A, and why
feature-ship-cycle 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 11d 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 — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Feature Ship Cycle (2-4 Weeks)
Overview
The feature ship cycle takes a validated concept from specification through development, launch, and post-launch evaluation. Use this when you've completed discovery and are ready to commit to building.
Instructions
This workflow runs across 2-4 weeks. Each phase must be completed before moving to the next. Handoff criteria at each gate prevent rework.
Phase 1: Spec (Week 1)
- Write the PRD — Load prd-writer skill. Include: problem statement, scope, requirements, success metrics, launch criteria
- Break down stories — Load epic-breakdown skill. Split the feature into sprint-sized stories
- Write acceptance criteria — Load acceptance-criteria skill. Given/When/Then for each story
- Update technical spec — Work with engineering on API contracts, data models, and architecture
- Design review — Hand off to design with clear scope
Output: PRD, user stories, acceptance criteria, design brief
Phase 2: Build (Week 2-3)
- Support engineering — Clarify requirements, answer questions, make scope decisions
- Review progress — Check demos, review designs, provide feedback
- Manage scope — If something is taking too long, negotiate scope reduction (not deadline extension)
- Update stakeholders — Weekly status updates using RAG framework
Output: Working feature in staging
Phase 3: Launch (Week 3-4)
- QA sign-off — All P0/P1 bugs fixed, acceptance criteria met
- Write release notes — Load release-notes skill. Write for end users and enterprise
- Prepare launch materials — Load go-to-market skill. Landing page, email, in-app messaging
- Plan rollout — Load rollout-strategy skill. Phased rollout with rollback criteria
- Go/no-go meeting — Review launch criteria, make the call
Output: Feature shipped, announcements live
Phase 4: Measure (Week 4+)
- Monitor metrics — Load metrics-framework skill. Track primary and counter-metrics
- Analyze results — Load experiment-analysis skill. Did we hit our targets?
- Gather feedback — Support tickets, user interviews, NPS
- Plan iteration — What to improve next? Load iteration-prioritization skill
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.
- 11d ago First seen · 74 lines · 35 tokens per session scan A 6375653dfb35
feature-ship-cycle is a skill published in the GitHub repository uthumany/uthy-legacy-os (5 stars, last pushed 3mo ago), licensed MIT. It adds 35 tokens to every session and 785 once invoked, about $0.0002 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
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.