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/furkantokkan/agent-foundryWrote 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/furkantokkan/agent-foundry/ux-design)<a href="https://agentmods.dev/commands/furkantokkan/agent-foundry/ux-design"><img src="https://agentmods.dev/badge/commands/furkantokkan/agent-foundry/ux-design/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/furkantokkan/agent-foundry/ux-design"><img src="https://agentmods.dev/badge/commands/furkantokkan/agent-foundry/ux-design.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.00058 | $0.00125 |
| Opus 5.5 | $0.00023 | $0.00050 |
| Sonnet 5.5 | $0.00012 | $0.00025 |
| Haiku 4.5 | $0.00006 | $0.00013 |
Grade A, and why
ux-design 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 5d 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
/ux-design
Use the ux-design Codex skill for this request. If this workflow references
Claude-only agents, treat those names as role guidance and follow Codex's active
skills, global instructions, and local repository rules.
User arguments: $ARGUMENTS
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.
- 5d ago First seen · 12 lines · 58 tokens per session scan A 94f7ecfbb3c8
ux-design is a command published in the GitHub repository furkantokkan/agent-foundry (10 stars, last pushed today), licensed MIT. It adds 58 tokens to every session and 125 once invoked, about $0.0002 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-09-25.
Other commands, from other repositories
design-review
Review and interactively edit the current designdoc.json. Displays the design document in a readable format and allows modifications to components, patterns, decisions, and story mappings.
design-import
Import an external design document (Markdown, JSON, or HTML from Confluence/Notion) and convert it to designdoc.json format for Plan Cascade integration.
phase-2-step-4
Phase 2 Step 4: High-Fidelity Design.
phase-2-step-5
Kilo Code does not substitute $ARGUMENTS. Wherever this command refers to $ARGUMENTS, read it as the text I typed after the slash command in this message.
visual-standards
Load visual formatting standards for screenshots, emoji headings, and image specs: $ARGUMENTS.
git
The pre-finish status: branch, hygiene findings, message checks, workflow lint, template state.