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/appboypov/pew-pew-plaza-packsWrote 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/appboypov/pew-pew-plaza-packs/ui-ux-behaviour-block)<a href="https://agentmods.dev/commands/appboypov/pew-pew-plaza-packs/ui-ux-behaviour-block"><img src="https://agentmods.dev/badge/commands/appboypov/pew-pew-plaza-packs/ui-ux-behaviour-block/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/appboypov/pew-pew-plaza-packs/ui-ux-behaviour-block"><img src="https://agentmods.dev/badge/commands/appboypov/pew-pew-plaza-packs/ui-ux-behaviour-block.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.00215 |
| Opus 5 | $0.00000 | $0.00108 |
| Sonnet 5 | $0.00000 | $0.00043 |
| Haiku 4.5 | $0.00000 | $0.00021 |
Grade A, and why
ui-ux-behaviour-block 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.
What it actually says
Block Command
When this command is used, use the following block. Acknowledge your understanding and then await the user's request.
## 🎨 UI/UX Behaviour
> 💡 *Specific behavior requirements for UI/UX elements including positioning, responsive behavior, feedback, and animations.*
[List UI/UX behavioral requirements using wikilinks where applicable]
```
<example>
[ List UI/UX behavioral requirements using wikilinks where applicable:
- [[button-component]] should show loading indicator while processing
- Error messages appear below respective [[input-field]] with fade-in animation
- [[modal-dialog]] should center on screen and include backdrop blur
- On mobile, [[navigation-menu]] collapses to hamburger icon
- [[form-elements]] provide real-time validation feedback
- Page transitions use 300ms ease-in-out animation
- [[tooltip]] appears on hover with 500ms delay
- Overflow content in [[card-component]] shows ellipsis with full text on hover
]
</example>
```
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 · 28 lines · 0 tokens per session scan A 04aa3f068719
ui-ux-behaviour-block is a command published in the GitHub repository appboypov/pew-pew-plaza-packs (85 stars, last pushed 8mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 215 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-03.
Other commands, from other repositories
design-implement
Thin entry point for /design-implement [--route ] [--viewport WxH] [--from-screenshots] [--dry-run] — parses and validates the argument shape only, then hands control to the design-implement skill. No run logic lives here.
prototype-iterate
Apply targeted changes to an existing prototype without regenerating from scratch.
wireframes
Generate screen spec JSON files (NOT HTML) — one .json file per screen, rendered natively by Archon.
theme-tokens
Define a design system as Tailwind v4 @theme tokens (color, type scale, spacing, radius, shadow) with intentional light + dark themes. Use when setting up a...
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.