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/mantacron/mantaWrote 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/agents/mantacron/manta/ux-planner)<a href="https://agentmods.dev/agents/mantacron/manta/ux-planner"><img src="https://agentmods.dev/badge/agents/mantacron/manta/ux-planner/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/agents/mantacron/manta/ux-planner"><img src="https://agentmods.dev/badge/agents/mantacron/manta/ux-planner.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.00041 | $0.00924 |
| Opus 5.5 | $0.00016 | $0.00370 |
| Sonnet 5.5 | $0.00008 | $0.00185 |
| Haiku 4.5 | $0.00004 | $0.00092 |
Grade A, and why
ux-planner 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.
The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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 · 148 lines · 41 tokens per session scan A 9279ec530844
ux-planner is an agent published in the GitHub repository mantacron/manta (10 stars, last pushed 15d ago), with no licence file. It adds 41 tokens to every session and 924 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-08-31.
Other agents, from other repositories
artifact-sonnet
Use proactively for any HTML artifact page, new or revised, once its content is decided: a report, a consultation page, a dashboard. The page is written as a page SPEC (a .spec.md) and built; the agent never writes raw HTML for a new or revised page. Handoff: ONE page per brief, never two — the fixed brief…
artifact-grader
Grades an artifact page from its screenshot tiles against the aidex visual-review rubric, with no access to its source. Handoff: the request the page answers, the absolute path of the shots manifest ( -shots.json from render-probe.sh --shots), the list of shot files regenerated this run, the rubric path, the profile's…
figure-sonnet
Use proactively when an artifact page needs a wireframe or screen mockup (inline SVG themed with the kit tokens). Not for structure trees or option A-vs-B comparisons: those are a diagram block (shape=tree / shape=compare) written straight into the page spec. Handoff: a spec file with a named "Files to read first"…
ui-ux-designer
UI/UX Designer & Frontend Validator.
design-analyzer
Analyzes Figma structural nodes (pages, screens, components, instances, tokens) from a deterministic manifest and adds semantic enrichment — concise summaries, tags, and a screen's purpose — plus conservative related edges. Does NOT invent structural nodes or edges.
mobile-engineer
Builds Solana mobile apps in React Native/Expo: Mobile Wallet Adapter, Seeker features, deep links, dApp Store releases. Web frontends go to solana-frontend-engineer.