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 littlestudent886/complex-dev-skills --skill complex-feature-devgit clone --depth 1 https://github.com/littlestudent886/complex-dev-skillsWrote 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/littlestudent886/complex-dev-skills/complex-feature-dev)<a href="https://agentmods.dev/skills/littlestudent886/complex-dev-skills/complex-feature-dev"><img src="https://agentmods.dev/badge/skills/littlestudent886/complex-dev-skills/complex-feature-dev/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/littlestudent886/complex-dev-skills/complex-feature-dev"><img src="https://agentmods.dev/badge/skills/littlestudent886/complex-dev-skills/complex-feature-dev.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.00032 | $0.02792 |
| Opus 5.5 | $0.00013 | $0.01117 |
| Sonnet 5.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 1mo 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.
- 1mo 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 8mo ago), licensed MIT. It adds 32 tokens to every session and 2,792 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
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
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.
handle-linkedin-connection-request-signal
Use this skill when someone sends a team member an inbound LinkedIn connection request. An inbound request is a deliberate, ACTIVE first-party intent signal — meaningfully stronger than a passive profile view — and it deserves different scoring rules. The skill resolves and enriches the requester, gates them through…
remove
Remove a deployed framework or addon from the current workspace.