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/epam/ai-dial-ui-kitWrote 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/epam/ai-dial-ui-kit/feature-pipeline)<a href="https://agentmods.dev/commands/epam/ai-dial-ui-kit/feature-pipeline"><img src="https://agentmods.dev/badge/commands/epam/ai-dial-ui-kit/feature-pipeline/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/epam/ai-dial-ui-kit/feature-pipeline"><img src="https://agentmods.dev/badge/commands/epam/ai-dial-ui-kit/feature-pipeline.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.00000 | $0.00317 |
| Opus 5.5 | $0.00000 | $0.00127 |
| Sonnet 5.5 | $0.00000 | $0.00063 |
| Haiku 4.5 | $0.00000 | $0.00032 |
Grade A, and why
feature-pipeline 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 25d 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.
What it actually says
Feature pipeline (plan → implement → review → fix)
Run this workflow in order in one conversation, unless the user stops between steps.
Phase 1 — Plan
- Output only a structured plan (same sections as
/plan-component: name, props, states, dependencies, deliverables, risks). - Do not write implementation code in Phase 1.
Wait for explicit user confirmation (e.g. “approved”, “go”) before Phase 2, unless the user already said to run the full pipeline without pauses.
Phase 2 — Implement
- Implement strictly according to the approved plan (
/implement-from-planrules). - Run
npm run typecheck,npm run lint,npm run test; fix failures.
Phase 3 — Review
- Act as reviewer only (
/review-changes): correctness, API, a11y, tests, styles, churn. - Output a prioritized must-fix / nice-to-have list with file references.
- Do not apply fixes in Phase 3.
Phase 4 — Apply fixes
- Apply only must-fix items from Phase 3 (
/apply-reviewrules). Include nice-to-have only if the user asked. - Re-run
npm run typecheck,npm run lint,npm run test.
End with a short summary: what shipped, what was deferred, and any follow-ups for the user.
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.
- 25d ago First seen · 29 lines · 0 tokens per session scan A 2da76b3d4f74
feature-pipeline is a command published in the GitHub repository epam/ai-dial-ui-kit (10 stars, last pushed yesterday), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 317 tokens. 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-19.
Other commands, from other repositories
quality-gate
Run the ECC quality pipeline on demand for a file or project scope.
review
Review code changes against project conventions.
review
Review a skill for quality before merge.
critique
Design lens critique covering visual hierarchy, clarity, and anti-slop patterns — produces a findings table, no code edits unless asked. Use when the user wants a design review, says "what's wrong with this UI", or needs a second opinion before a handoff or presentation.
review
Review the current diff against project memory.
code-review
Code review a pull request.