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.
npx agentmods add commands/instructure/instructure-ui/prgit clone --depth 1 https://github.com/instructure/instructure-uiWhat 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 | $0.00008 | $0.01557 |
| Opus 5 | $0.00004 | $0.00779 |
| Sonnet 5 | $0.00002 | $0.00311 |
| Haiku 4.5 | $0.00001 | $0.00156 |
Grade A, and why
pr 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 today.
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
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- today First seen · 89 lines · 8 tokens per session scan A 79c6dadd5b47
pr is a command published in the GitHub repository instructure/instructure-ui (479 stars, last pushed today), with no licence file. It adds 8 tokens to every session and 1,557 once invoked, about $0.0000 per session on Opus 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-01.
Other commands, from other repositories
update-hive
You are helping update the @hazelcast/ui design system from v3 to v4.
init
Initialize a project for on-brand Marmo UI generation — detect or interview for brand basics (layout, primary color, fonts, radius, spacing) and write a DESIGN.md if one doesn't exist.
speckit.tasks
Generate an actionable, dependency-ordered tasks.md for the feature based on available design artifacts.
anti-slop-designer
Use when a UI looks machine-made rather than decided. Violet gradients, glassmorphism everywhere, identical cards in a grid, untouched shadcn or Material defaults, emoji bullets, or copy stuffed with seamless and unlock.
database-setup
Use when a project needs to store data and has no database yet. Setting up Supabase, creating tables, writing queries, and connecting them to the frontend. Written for designers.
deploy-to-vercel
Use when a project runs locally but is not on the internet yet, or a Vercel deploy is failing. First deploy, build errors, environment variables, custom domain.