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/story-and-test)<a href="https://agentmods.dev/commands/epam/ai-dial-ui-kit/story-and-test"><img src="https://agentmods.dev/badge/commands/epam/ai-dial-ui-kit/story-and-test/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/story-and-test"><img src="https://agentmods.dev/badge/commands/epam/ai-dial-ui-kit/story-and-test.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.00177 |
| Opus 5.5 | $0.00000 | $0.00071 |
| Sonnet 5.5 | $0.00000 | $0.00035 |
| Haiku 4.5 | $0.00000 | $0.00018 |
Grade A, and why
story-and-test 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
Add or align Storybook + tests
For the component(s) in scope:
- Storybook — Default + variants (sizes, states, error). Use the same structure as sibling components in
src/components/. - Vitest — User interactions (click, type, keyboard) via Testing Library; assert visible outcomes and callbacks.
- Coverage — Aim to cover branches you added; follow existing
*.spec.tsxstyle in this folder. - Exports — If the component is public, confirm
src/index.tsexports match the story import path consumers would use.
After edits, npm run typecheck, npm run lint, npm run test, and Storybook if UI changed — run or explicitly ask the user to run them; stories and specs must typecheck too.
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 · 11 lines · 0 tokens per session scan A c750f5b91e72
story-and-test 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 177 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
test-coverage
Analyze and improve test coverage.
verify
Run verification loop to validate implementation.
verify
Grade work that already exists and decide whether it can merge. Runs the project's current unit, integration, and E2E suites plus security scanning and type checking, scores every dimension 0-10, and returns a merge verdict with a VERIFIED-vs-CLAIMED evidence manifest. Writes no test files and edits no source. Use…
test
A command that runs JavaScript or TypeScript tests with npm or Vitest, a test-runner tool, and explains any failures.
fix-test
Auto-diagnose and fix failing tests — identifies root causes and applies fixes.
smart-test
Find test gaps and generate tests for uncovered code.