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/saajunaid/caddis-pluginWrote 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/saajunaid/caddis-plugin/mockup)<a href="https://agentmods.dev/commands/saajunaid/caddis-plugin/mockup"><img src="https://agentmods.dev/badge/commands/saajunaid/caddis-plugin/mockup/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/saajunaid/caddis-plugin/mockup"><img src="https://agentmods.dev/badge/commands/saajunaid/caddis-plugin/mockup.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.00010 | $0.00261 |
| Opus 5.5 | $0.00004 | $0.00104 |
| Sonnet 5.5 | $0.00002 | $0.00052 |
| Haiku 4.5 | $0.00001 | $0.00026 |
Grade A, and why
mockup 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 1mo 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
Generate UI Mockup
Create a visual mockup or wireframe for a new feature before implementation begins.
Instructions
- Read
project-config.mdto understand the framework, brand colors, and UI conventions - Load the mockup skill:
.github/skills/frontend/mockup/SKILL.md - If an Intent Document exists in
.github/agent-docs/intents/, read it first to understand the goal - Ask: What feature or screen do you want to mock up?
Workflow
- Gather requirements (what the screen should show, who uses it, key interactions)
- Create the mockup as an SVG or HTML file
- Save to
.github/agent-docs/ux/mockups/<feature-name>-mockup.<ext> - Update
.github/agent-docs/ARTIFACTS.mdwith the new artifact - Present the mockup for review before implementation
Handoff
Once approved, hand off to UX Designer for review or Frontend Developer / Streamlit Developer for implementation.
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.
- 1mo ago First seen · 29 lines · 10 tokens per session scan A 5ddc4ab9fd90
mockup is a command published in the GitHub repository saajunaid/caddis-plugin (0 stars, last pushed today), licensed MIT. It adds 10 tokens to every session and 261 once invoked, about $0.0000 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-09.
Other commands, from other repositories
design
Command dispatcher for design.
test-feature
Test a React Native feature on the running simulator/emulator. Verifies UI, user flows, and internal state. Generates a persistent Maestro test file.
run-workflow
Validate and establish the proven rn-dev-agent operating sequence before a real React Native journey — declared package manager and dependencies, read-only inventory, typed session recovery, one exclusive device, managed integration and Metro, only the requested proof, reverse-order cleanup.
observe
Show the observability web UI URL (it autostarts with the session); stop or restart it.
accept
Command dispatcher for accept.
checklist
Generate a custom checklist for the current feature based on user requirements.