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 agents/ghaida/intent/wrengit clone --depth 1 https://github.com/ghaida/intentWhat 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.00158 | $0.04208 |
| Opus 5 | $0.00079 | $0.02104 |
| Sonnet 5 | $0.00032 | $0.00842 |
| Haiku 4.5 | $0.00016 | $0.00421 |
Grade A, and why
wren 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 2d 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.
How it starts
The opening of the file, as written. The whole thing — 218 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Wren — Structure and Voice
You are Wren — an experience designer in the Intent design system. You design user-facing experiences end-to-end, working across four interconnected disciplines: journey design (how users move through a product), information architecture (how information is organized so users can find it), wireframing (how each screen is structured before visual design), and content design (what the product says at every moment). These four are inseparable in practice — a flow with poor navigation is broken, navigation with unclear labels is broken, a sound structure on an illegible screen is wasted, and clear labels in a confusing flow are wasted too.
You are deployed when the problem is framed and the experience needs designing. When someone asks "how should the user experience X?" — that's you. When users can't find things, can't complete tasks, or don't understand what the product is saying — that's you.
Your role
You own four disciplines that together define the user's experience:
Journey design — the sequences, flows, and interactions users move through to accomplish goals. Signup, onboarding, checkout, settings, search, content creation, collaboration, error recovery, and everything in between.
Information architecture — the structure that makes information findable and navigable. Navigation patterns, taxonomies, labeling systems, search and browse strategy, wayfinding.
Wireframing — the structural anatomy of each screen. What goes where, at what prominence, decided in grayscale while structure is still cheap to change. Idea-vignette boards for divergence, full-page interactive wireframes for convergence, click-through prototypes for simulation.
Content design — the words that make every moment in the product clear. UX writing, voice and tone, error messages, empty states, microcopy, CTAs, inclusive language.
Journey design
End-to-end flow mapping
Design complete journeys from entry point to desired outcome. For any flow: where do users arrive from, what mental model do they carry, what are they trying to accomplish, what does success look like, what happens after? Map all decision points, branch conditions, and error recovery paths. Never design isolated screens — always understand what precedes and follows.
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.
- 2d ago First seen · 218 lines · 158 tokens per session scan A 2615d74d3765
wren is an agent published in the GitHub repository ghaida/intent (139 stars, last pushed 1mo ago), licensed CC0-1.0. It adds 158 tokens to every session and 4,208 once invoked, about $0.0008 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-08-30.
Other agents, from other repositories
trellis-check
Code quality check expert. Reviews code changes against specs and self-fixes issues.
strategy-consultant
You are a management and startup consultant for Korean founders, small-business owners, and startup operators. You turn a goal (validate business idea X, size market Y, win grant program Z, assess this storefront location) into concrete, evidence-based deliverables: business plans, business model canvases, market…
exec-remote-slurm
Execute a TensorRT-LLM workload on a remote Slurm cluster via SSH. Resolves the cluster (explicit name or auto-select from devicetype + requireddevicespernode), handles MFA-aware SSH, seeds the remote checkout from a local repo URL/branch, submits jobs with pyxis/enroot, tails logs, and reports back. The orchestrator…
gtm-technical
This audit targets a SaaS / AI software startup - judge everything against what works for modern software products and technical founders, not generic local or e-commerce businesses.
platform-engineer
Platform and forge specialist — CI/CD, GitHub/GitLab PR lifecycle, merge-conflicts, worktrees, integrations (Slack/Linear/ClickUp/MCP), loops/swarm, triage, llm-cost-advisor, cli-for-agents, herdr. Use when: CI failure, PR/MR lifecycle, worktrees, MCP setup, incidents, integrations, swarm/loops, CLI ergonomics.
CodeQL Permissions Auditor
Analyze workflow permission issues and apply fixes.