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.
git 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/commands/thapaliyabikendra/ai-artifacts/add-feature)<a href="https://agentmods.dev/commands/thapaliyabikendra/ai-artifacts/add-feature"><img src="https://agentmods.dev/badge/commands/thapaliyabikendra/ai-artifacts/add-feature/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/commands/thapaliyabikendra/ai-artifacts/add-feature"><img src="https://agentmods.dev/badge/commands/thapaliyabikendra/ai-artifacts/add-feature.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.00019 | $0.01156 |
| Opus 5 | $0.00010 | $0.00578 |
| Sonnet 5 | $0.00004 | $0.00231 |
| Haiku 4.5 | $0.00002 | $0.00116 |
Grade A, and why
add-feature 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 9d 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 — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Add Feature Command
Orchestrate end-to-end feature development using specialized agents with optimized progressive handoff.
Arguments: $ARGUMENTS
Pre-flight
Project: !basename $(pwd)
Date: !date +%Y-%m-%d
Required files:
- !
test -d docs/domain && echo "✓ docs/domain/" || echo "✗ MISSING: docs/domain/" - !
test -d docs/architecture && echo "✓ docs/architecture/" || echo "✗ MISSING: docs/architecture/"
Mode Selection
| Flag | Mode | Flow | Time |
|---|---|---|---|
--minimal |
Direct implementation | Stage 3 only | ~2 min |
--fast |
Skip BA, Arch parses requirements | Arch → [Dev + QA] | ~3 min |
| (default) | Progressive handoff | BA(entity) → Arch ∥ BA(reqs) → [Dev + QA] | ~4 min |
--full-review |
Complete with reviews | All stages with parallelism | ~6 min |
Workflow Overview
--minimal: [abp-developer only]
--fast: backend-architect ──→ [abp-developer + qa-engineer]
(parses requirements directly)
default: BA(entity+perms) ─┬──→ [backend-architect + qa-data] ──→ [abp-developer + qa-tests]
🟢 ENTITY_READY │ 🟢 CONTRACTS_READY (parallel impl)
│
BA(reqs+rules) ───┘ (continues in background, non-blocking)
--full-review: [default] ──→ [abp-code-reviewer + security-engineer]
Signal Protocol
Agents communicate completion through explicit signals:
| Signal | Emitted By | Triggers |
|---|---|---|
🟢 ENTITY_READY |
BA | Architect + QA-Data can start |
🟢 CONTRACTS_READY |
Architect | Developer + QA-Tests can start |
Execution
See: references/add-feature-modes.md for detailed mode scripts.
Parse mode from arguments, then follow the appropriate execution flow.
Output Summary
## Feature: {feature-name}
### Mode: {minimal|fast|default|full-review}
### Execution Time: {time}
### Files Created
**Documentation:**
- docs/domain/entities/{entity}.md
- docs/features/{feature-name}/requirements.md (default/full only)
- docs/features/{feature-name}/technical-design.md
- docs/features/{feature-name}/test-cases.md
**Contracts:**
- Application.Contracts/{Feature}/I{Entity}AppService.cs
- Application.Contracts/{Feature}/{Entity}Dto.cs
- Application.Contracts/{Feature}/Create{Entity}Dto.cs
- Application.Contracts/{Feature}/Update{Entity}Dto.cs
- Application.Contracts/{Feature}/Get{Entity}sInput.cs
**Implementation:**
- Domain/{Feature}/{Entity}.cs
- Domain.Shared/{Feature}/{Entity}Consts.cs
- Application/{Feature}/{Entity}AppService.cs
- Application/{Feature}/{Entity}ApplicationMappers.cs
- Application/{Feature}/*Validator.cs
- EntityFrameworkCore/EntityTypeConfigurations/{Entity}Configuration.cs
**Tests:**
- test/TestBase/{Feature}/{Entity}TestData.cs
- test/TestBase/{Feature}/{Entity}TestDataSeedContributor.cs
- test/Application.Tests/{Feature}/{Entity}AppService_Tests.cs
### Build Status: {PASSED|FAILED}
### Next Steps
1. Generate migration: /generate:migration Add{Entity}
2. Apply migration: dotnet run --project api/src/*.DbMigrator
3. Run tests: dotnet test api/
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.
- 9d ago First seen · 138 lines · 19 tokens per session scan A 1b2c791ee43e
add-feature is a command published in the GitHub repository thapaliyabikendra/ai-artifacts (24 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 19 tokens to every session and 1,156 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 commands, from other repositories
init
Initialize configurations for Supabase local development.
http-service
Build, review or debug a Bun HTTP service. Loads the http-service skill, then works the task through its workflow.
start-10-1
A guided lesson on setting up clasp, a command-line tool for managing Google Apps Script projects, and connecting it to Google’s Apps Script API.
api-contract-review
Review an API contract (endpoints, request/response shapes, error codes, auth model) BEFORE implementation for naming consistency, versioning, pagination, idempotency, and alignment with existing endpoints. Distinct from review-hard (post-implementation risk) and repo-consistency-sweep (pattern matching on written…
build
Discover an AI Gateway's models and MCP tools, retrieve a credential, and integrate them into your app — call a model, connect MCP tools, or scaffold a runnable agent.
fastapi
FastAPI application design and implementation conventions. Use this skill when building, updating, or reviewing FastAPI services, routers, dependencies, request/response schemas, streaming endpoints, or API tests. Trigger on FastAPI-specific work such as path operation design, dependency injection, response models…