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 Lifecycle-Innovations-Limited/claude-ops --skill ops-feature-devgit clone --depth 1 https://github.com/Lifecycle-Innovations-Limited/claude-opsWrote 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/lifecycle-innovations-limited/claude-ops/ops-feature-dev)<a href="https://agentmods.dev/skills/lifecycle-innovations-limited/claude-ops/ops-feature-dev"><img src="https://agentmods.dev/badge/skills/lifecycle-innovations-limited/claude-ops/ops-feature-dev.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.00028 | $0.00655 |
| Opus 5 | $0.00014 | $0.00328 |
| Sonnet 5 | $0.00006 | $0.00131 |
| Haiku 4.5 | $0.00003 | $0.00065 |
Grade A, and why
ops-feature-dev 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 7d 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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Teams support
If CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1 is set, use Agent Teams when
feature-dev phases fan out in parallel (e.g. explore + architect, or implement +
review). This enables:
- Phase agents share findings mid-flight (explore surfaces a constraint → architect adjusts before implementation starts)
- You can steer priorities in real time ("finish API contract first, then UI")
- Agents report progress as each phase completes
Team setup (only when the flag is enabled, and only for genuinely parallel phases):
TeamCreate("feature-dev-lifecycle")
Agent(team_name="feature-dev-lifecycle", name="phase-explore", ...)
Agent(team_name="feature-dev-lifecycle", name="phase-architect", ...)
Steer with SendMessage / broadcast; share work via TaskCreate/TaskUpdate.
If the flag is NOT set, fall back to standard fire-and-forget subagents (the
default), or invoke /feature-dev inline via the Skill tool.
OPS ► FEATURE DEV
Load ops-rules before acting. Public repo (no personal data). Outbound: one draft → one approval → one send. If AskUserQuestion / Workflow are missing, follow Rule 10 in ops-rules (Hermes: numbered options / two-turn Telegram card; delegate_task).
Thin router into the feature-dev companion plugin. Do not re-implement its phases here.
When to use
- Ad-hoc repos (no
.planning/): optional structured alternative to jumping straight into/flow build. - Project repos (
.planning/present): run beforegsd-execute-phasewhen you want exploration + architecture + clarifying questions; execution still canonical via GSD. - Review: gstack
/reviewandgsd-code-reviewstay canonical; feature-dev Phase 6 is available via explicit/feature-devor auto-swap tofeature-dev:code-reviewer.
Routing
If $ARGUMENTS is empty, invoke /feature-dev with no args (discovery phase).
Otherwise invoke /feature-dev $ARGUMENTS via the Skill tool.
Integration notes
- Requires the feature-dev plugin installed (
/ops:setupStep 2c or/plugin install feature-dev). - Specialist auto-swap (
feature-dev:code-*) is handled bybin/ops-suggest-specialized-agentwhen the plugin is present. - Does not replace
/flow build,/review, orgsd-execute-phase— it overlays them.
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.
- 7d ago First seen · 64 lines · 28 tokens per session scan A c9d268a144e6
ops-feature-dev is a skill published in the GitHub repository Lifecycle-Innovations-Limited/claude-ops (186 stars, last pushed yesterday), licensed MIT. It adds 28 tokens to every session and 655 once invoked, about $0.0001 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
abm-campaign-builder
Builds targeted Account-Based Marketing campaigns by identifying ideal customer profiles, mapping buying committees, creating personalized outreach sequences, and designing multi-channel engagement strategies. Use when targeting enterprise accounts, building sales playbooks, or designing vertical market penetration…
business-roi-analyzer
Calculates ROI, payback period, and financial projections for business investments including technology purchases, automation projects, hiring decisions, and equipment acquisitions. Use when evaluating whether a business investment is worth making, comparing multiple investment options, or building a business case for…
change-management-planner
Plans organizational change initiatives including technology rollouts, process redesigns, and team restructuring. Maps stakeholders, identifies resistance, designs communication plans, and builds adoption strategies with measurable milestones.
client-discovery-interview
Conducts structured discovery interviews for consultants, agencies, and service providers. Guides conversation through problem identification, stakeholder mapping, success criteria definition, budget/timeline scoping, and produces a formatted discovery brief with next steps.
cognify-workflow-analysis
Analyzes business workflows to identify automation opportunities, calculate ROI, and generate structured redesign recommendations. Use when a user describes operational pain points, wants to reduce manual work, improve team communication, automate repetitive tasks, or evaluate where AI can save time and money.
competitive-intelligence
Conducts structured competitive analysis including market positioning, feature comparison, pricing intelligence, SWOT analysis, and strategic recommendations. Use when evaluating competitors, preparing for a sales battle card, planning market entry, differentiating a product, or building a competitive strategy.