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 thapaliyabikendra/ai-artifacts --skill feature-development-workflowgit clone --depth 1 https://github.com/thapaliyabikendra/ai-artifactsWrote 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/thapaliyabikendra/ai-artifacts/feature-development-workflow)<a href="https://agentmods.dev/skills/thapaliyabikendra/ai-artifacts/feature-development-workflow"><img src="https://agentmods.dev/badge/skills/thapaliyabikendra/ai-artifacts/feature-development-workflow/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/thapaliyabikendra/ai-artifacts/feature-development-workflow"><img src="https://agentmods.dev/badge/skills/thapaliyabikendra/ai-artifacts/feature-development-workflow.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.00054 | $0.00668 |
| Opus 5 | $0.00027 | $0.00334 |
| Sonnet 5 | $0.00011 | $0.00134 |
| Haiku 4.5 | $0.00005 | $0.00067 |
Grade A, and why
feature-development-workflow 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 — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Feature Development Workflow
For complete feature implementation, use the /add-feature command.
Quick Reference
| Command | Time | Use Case |
|---|---|---|
/add-feature <name> "<reqs>" --minimal |
~2 min | Simple CRUD, no docs |
/add-feature <name> "<reqs>" --fast |
~2.5 min | Skip BA, requirements clear |
/add-feature <name> "<reqs>" |
~3 min | Standard (progressive handoff) |
/add-feature <name> "<reqs>" --full-review |
~4.5 min | With code + security review |
Dependency Chain (Signal-Based)
BA(entity+perms) ─┬──→ [Architect + QA-Data] ──→ [Developer + QA-Tests]
🟢 ENTITY_READY │ 🟢 CONTRACTS_READY (parallel implementation)
│
BA(reqs+rules) ───┘ (continues in background, non-blocking)
Signal Protocol: Agents emit signals (🟢 ENTITY_READY, 🟢 CONTRACTS_READY) to trigger dependent agents immediately.
Agent Roles
| Stage | Agent | Trigger | Output |
|---|---|---|---|
| Analyze | business-analyst |
Start | Entity definition, permissions, requirements |
| Design | backend-architect |
🟢 ENTITY_READY | Technical design, interface contracts |
| Test Data | qa-engineer |
🟢 ENTITY_READY | TestData.cs, Seeder.cs (parallel with Architect) |
| Implement | abp-developer |
🟢 CONTRACTS_READY | Domain, Application, EF Core layers |
| Tests | qa-engineer |
🟢 CONTRACTS_READY | Unit tests (parallel with Developer) |
| Review | abp-code-reviewer |
Phase 2 complete | Review report (optional) |
| Security | security-engineer |
Phase 2 complete | Security audit (optional) |
Parallelism Optimizations
- Phase 1b: Architect + QA-Data run in parallel (on ENTITY_READY)
- Phase 2: Developer + QA-Tests run in parallel (on CONTRACTS_READY)
- BA secondary outputs: Non-blocking (requirements.md, business-rules.md)
- Skipped by default: ANALYSIS.md, impact-analysis.md (use
--impactflag)
Full Documentation
See .claude/commands/feature/add-feature.md for complete workflow documentation.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 58 lines · 54 tokens per session scan A c6bb0c2606b6
feature-development-workflow is a skill published in the GitHub repository thapaliyabikendra/ai-artifacts (24 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 54 tokens to every session and 668 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-09-03.
Other skills, from other repositories
ai-loop
Runs a bounded spec-build-review development loop with explicit scope, stop conditions, and human approval gates for risky or ambiguous work.
create_profile_style_skill
A workflow for turning a person's video-editing habits into a reusable editing skill file. It examines choices such as pacing, storytelling, audio, subtitles, colour, transitions, and recurring editing rules.
Paper Writing Workflow
Workflow phases for paper-writing tasks: triage, material inventory, research question, literature review, paper outline, data analysis summary, figure storyline, reader testing, and finalize packet. Each phase is a short contract — read the relevant rows for the current task only.
project-brainstorming
Guides project ideation via Socratic questioning to produce a validated brief. Use before specification when requirements are unclear.
project-execution
Executes implementation plans with progress tracking, checkpoint validation, and quality gates. Use after planning is complete and tasks are ready to implement.
company-product-context
Compiles comprehensive company product context from PDF documents, web research, and industry knowledge.