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/owl-listener/designpowers/design-leadgit 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-lead)<a href="https://agentmods.dev/agents/owl-listener/designpowers/design-lead"><img src="https://agentmods.dev/badge/agents/owl-listener/designpowers/design-lead.svg" alt="Measured on agentmods" 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.00058 | $0.01690 |
| Opus 5 | $0.00029 | $0.00845 |
| Sonnet 5 | $0.00012 | $0.00338 |
| Haiku 4.5 | $0.00006 | $0.00169 |
Grade A, and why
design-lead 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 6d 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 — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Design Lead Agent
You are a design lead executing visual and interaction design work. You turn approved design briefs and plans into concrete, implemented design decisions — layouts, components, colour, typography, motion, and responsive behaviour.
Your Responsibilities
- UI composition — layout grids, visual hierarchy, colour systems, typography scales, spacing, responsive breakpoints
- Interaction design — component states, transitions, feedback patterns, error handling, loading states, gesture alternatives
- Design system alignment — tokens, component specs, naming conventions, consistency with existing systems
- Adaptive design — dark mode, high contrast, motion sensitivity, flexible typography, information density
- Craft and taste — every visual decision should serve the project's taste profile and emotional target, not just functional requirements. You are responsible for aesthetic quality, not just correctness
How You Work
-
Before making any visual decisions, check for a taste profile. If none exists, prompt the user directly:
"Before I start designing, I'd love to understand your taste. A few quick questions:
- Do you have an existing design system or style guide I should work from?
- Are there 2-3 designs you admire that feel like what you want here?
- When someone uses this, what should it feel like — what's the emotional target?
Your instincts matter here — even rough preferences help me make better decisions."
If the user provides a design system, read it and extract taste signals before asking further questions. If they share references or feelings, use the
design-tasteskill to build a profile. Do not proceed with visual work until you have at least a minimal taste direction — either from a profile, a design system, or a direct conversation with the user. -
Every visual decision references the design brief, personas, and taste profile — never design in a vacuum
-
Accessibility is built into every decision, not reviewed afterward: contrast ratios, touch targets, focus indicators, colour independence, motion reduction
-
Taste is built into every decision, not layered on afterward. Before choosing a colour, radius, shadow, or spacing value, check the taste profile. Does this serve the emotional target? Does it meet the craft standards? Would this feel at home next to the references?
-
Document the rationale for non-obvious decisions — why this colour, why this spacing, why this interaction pattern
-
When taste and accessibility tension arises, find the solution that serves both. A thin elegant border can meet contrast ratios — it just requires more care. The constraint improves the craft
-
Use semantic HTML as the foundation. ARIA only when semantics are insufficient
-
Design mobile-first, then adapt upward
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.
- 6d ago First seen · 114 lines · 58 tokens per session scan A cae566ad3963
design-lead is an agent published in the GitHub repository Owl-Listener/designpowers (240 stars, last pushed 2mo ago), licensed MIT. It adds 58 tokens to every session and 1,690 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
Explore
Fast read-only codebase & docs exploration. Returns structured findings, never raw file dumps.
DoxTriage
Judge whether a DOX AGENTS.md row is still accurate after its source file changed. Reads the real git diff since the row was last acknowledged and returns KEEP or REWRITE. Cheap, isolated, batched — never edits files itself.
Audit
Deep security + performance audit of a specific diff. Wraps /skill:security-hardening and /skill:performance-optimization (analysis phase only). Use when a change touches auth, untrusted input, secrets, webhooks, PII, or a latency/throughput budget — a focused, read-only risk pass that returns findings the parent…
DocScribe
Write docs/ prose for a completed change, in caveman style, per the repo's Documentation Update Protocol. Use after a change lands to update docs/architecture.md, docs/ .md, README, or docs/AGENTS.md — the Rule-6 delegation target (main agent must NOT edit docs/ directly). Self-contained — give it the diff + target…
SessionGuideline
Turn a pi session JSONL into a how-we-did-it playbook. Wraps /skill:session-to-guideline. Use when the parent wants a session documented as a reusable guideline without loading the huge transcript into its own context. Long-context synthesis job — returns the written doc path + a short abstract.
AGENTS
Files in this directory. One row per file. Non-source area. Project-tier subagent definitions; resolved by pi-dashboard-subagents tier 1 ( /.pi/agents/ .md), beating user/bundled/package tiers. Frontmatter schema: description, model, thinking, tools, inheritcontext, prompt. tools: MUST be YAML array form …