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 agentmods add skills/littlestudent886/complex-dev-skills/complex-feature-devnpx skills add littlestudent886/complex-dev-skills --skill complex-feature-devgit clone --depth 1 https://github.com/littlestudent886/complex-dev-skillsWhat 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 | $0.00032 | $0.02792 |
| Opus 5 | $0.00016 | $0.01396 |
| Sonnet 5 | $0.00006 | $0.00558 |
| Haiku 4.5 | $0.00003 | $0.00279 |
Grade A, and why
complex-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 2d 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 — 302 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Feature Development (Complex Tasks)
A codebase-agnostic workflow for building new features safely:
- 7 phases (discovery → exploration → questions → architecture → implement → review → summary)
- Persistent planning files for long tasks (macro memory: goal, status, next actions, and durable decisions)
Inputs
Minimum input:
- A 1–2 sentence feature description (what to build + who/why).
Helpful extras (optional):
- Acceptance criteria / examples
- Related files or modules
- Docs / tickets / prototypes (if inaccessible, ask user to paste key parts)
Non-Negotiable Rules
- Never skip Phase 3 (Clarifying Questions). If anything is underspecified, ask and wait.
- Never start Phase 5 (Implementation) without explicit approval.
- Use the planning files as persistent macro memory. Keep them concise and durable.
- Read before decide. Before major decisions, re-read
task_plan.md. - Log errors briefly + don’t repeat failures. If an action fails, change the approach.
Quick Start (Planning Files)
This workflow requires these files in the repo root:
task_plan.mdfindings.mdprogress.mdCLAUDE.md(agent instructions; created by init if missing)
To initialize them, run:
/complex-feature-dev:init(recommended)
Or via terminal:
- macOS/Linux (or Windows Git Bash):
bash "$(ls -dt ~/.claude/plugins/cache/complex-dev-skills/complex-feature-dev/*/scripts/init-session.sh 2>/dev/null | head -1)" - Windows PowerShell:
pwsh -ExecutionPolicy Bypass -File "~/.claude/plugins/cache/complex-dev-skills/complex-feature-dev/<version>/scripts/init-session.ps1"
Project Guidelines
- Follow
AGENTS.md/CLAUDE.md/CONTRIBUTING.md/README.mdif present. - Prefer matching existing code patterns over introducing new abstractions.
- Write important conventions you discover into
findings.md.
Phase 1: Discovery
Goal: Make the request concrete and testable.
- If planning files are missing, run the initializer script via the Bash tool and do not proceed until the files exist.
- Restate the request as acceptance criteria; confirm scope and non-goals.
- Capture constraints (compatibility, performance, time, rollout).
- Write brief confirmed requirements + acceptance criteria to
findings.md.
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.
- 2d ago First seen · 302 lines · 32 tokens per session scan A 35c6db179e90
complex-feature-dev is a skill published in the GitHub repository littlestudent886/complex-dev-skills (5 stars, last pushed 6mo ago), licensed MIT. It adds 32 tokens to every session and 2,792 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
babysit
Same-session monitoring loop for PRs, CI runs, tickets, and deployments using the monitorstart / monitorupdate / autonudgestop MCP tools. The loop re-injects your check instructions into THIS session on an idle interval — same context, same tools — and works from dashboard chat, Slack threads, and Discord DMs. Use…
agile-product-owner
../../../product-team/agile-product-owner/skills/agile-product-owner/SKILL.md.
dot-ai-prd-create
Create documentation-first PRDs that guide development through user-facing content.
agent-upkeep
Perform one small, scoped maintenance improvement to the Elements monorepo and open a single reviewable pull request. Use this skill for scheduled or unattended upkeep runs that improve unit test coverage for one file, fix one behavioral bug in one module, or move one off ESLint rule toward enforcement to reduce…
organize-project
Organise documents into folders and move them between folders and modules with MOVE. Use when a module has grown unstructured, when restructuring a project, or when a document is in the wrong place.
smithers-supervise
Watch for stale running runs and auto-resume them. Run smithers supervise --help for usage details.