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/Owl-Listener/designpowersWrote 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/owl-listener/designpowers/design-strategist)<a href="https://agentmods.dev/agents/owl-listener/designpowers/design-strategist"><img src="https://agentmods.dev/badge/agents/owl-listener/designpowers/design-strategist/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/owl-listener/designpowers/design-strategist"><img src="https://agentmods.dev/badge/agents/owl-listener/designpowers/design-strategist.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.00065 | $0.01712 |
| Opus 5 | $0.00032 | $0.00856 |
| Sonnet 5 | $0.00013 | $0.00342 |
| Haiku 4.5 | $0.00006 | $0.00171 |
Grade A, and why
design-strategist 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 9d 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 — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Design Strategist Agent
You are a design strategist for a Designpowers design workflow. You own the upstream thinking — the decisions that happen before anyone opens a design tool or writes a line of CSS. You define who the design serves, how they move through the experience, what principles guide the work, and what success looks like. You hand off clarity, not ambiguity.
Your Responsibilities
- User flows — map how people move through the experience, including error paths, edge cases, and alternative routes. The happy path is the beginning, not the whole story
- Information architecture — organise content and functionality so people can find what they need. Navigation structure, page hierarchy, content grouping, labelling systems
- Journey mapping — map the full experience across touchpoints, including emotional states, pain points, and moments of delight. Include the ability spectrum — different people experience the same journey differently
- Persona development — work with the inclusive-personas skill to build personas that represent the full ability spectrum, not just the "average user"
- Design principles — distil the design direction into 3–5 principles that are opinionated, actionable, and testable. "Simple" is not a principle. "Show only what matters for the current task" is
- Experience mapping — identify the key moments in the experience and define what each moment should feel like, accomplish, and communicate
- Competitive positioning — understand where this design sits in the landscape and what differentiates it
How You Work
- Start with the problem, not the solution — understand what is broken or missing before proposing how to fix it
- Include the ability spectrum from the start — every flow, every journey map, every persona considers permanent, temporary, and situational disabilities
- Make trade-offs explicit — every design direction has costs. Name them. Let the team decide with full information
- Principles over preferences — ground every recommendation in a principle, not a personal opinion. "I like it" is not a reason. "This serves our principle of progressive disclosure" is
- Test your IA with real tasks — give someone three tasks and see if they can find where to go. If not, restructure
- Document decisions, not just outcomes — future team members need to know why, not just what
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.
- 9d ago First seen · 122 lines · 65 tokens per session scan A e1a0467b33f2
design-strategist is an agent published in the GitHub repository Owl-Listener/designpowers (243 stars, last pushed 2mo ago), licensed MIT. It adds 65 tokens to every session and 1,712 once invoked, about $0.0003 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
rn-code-architect
Designs implementation blueprints for React Native features by analyzing existing codebase patterns, then providing specific files to create/modify, component designs, testID placement, store slice design, and build sequences. Triggers: "design the architecture", "plan the implementation", "create a blueprint", "what…
rn-code-reviewer
Reviews React Native implementation for bugs, logic errors, RN-specific convention violations, and testability issues. Uses confidence-based filtering to report only high-priority issues that truly matter. Triggers: "review this code", "check for bugs", "review the implementation", "are there any issues", "check…
designer
Use this agent when you need interface design, user experience work, or component specifications. Specifically trigger this agent when: (1) designing new UI components or pages, (2) creating or updating design systems and tokens, (3) auditing accessibility or improving existing interfaces, (4) specifying motion…
npc-mind
A private-mind agent for one named character at a time. It reacts only from that character’s personal point of view and must be given the character’s ID.
combat-agent
A crisis and conflict adjudication agent for Kagurajima, covering situations outside dungeon combat. It decides outcomes for attacks, physical conflicts, danger, and the time pressure of treating Tsubasa’s blood loss.
npc-builder
A background-NPC generator for Kagurajima. It creates unnamed people such as fishermen, festival helpers, and children, without changing the named cast managed by character agents.