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 instructions/owl-listener/designpowers/gemini-mdgit 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/instructions/owl-listener/designpowers/gemini-md)<a href="https://agentmods.dev/instructions/owl-listener/designpowers/gemini-md"><img src="https://agentmods.dev/badge/instructions/owl-listener/designpowers/gemini-md.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 | $0.00569 | $0.00569 |
| Opus 5 | $0.00284 | $0.00284 |
| Sonnet 5 | $0.00114 | $0.00114 |
| Haiku 4.5 | $0.00057 | $0.00057 |
Grade A, and why
designpowers GEMINI.md 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 5d 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 — 36 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Designpowers
This is the Designpowers design workflow system.
Mandatory: Welcome Sequence First
Before doing anything else in a new session, you MUST run the welcome sequence defined in skills/using-designpowers/SKILL.md. This is non-negotiable.
- Read
skills/using-designpowers/SKILL.mdin full before responding to any user message - Follow the welcome sequence exactly: show the bird welcome screen and handle onboarding
- Do NOT skip the welcome, do NOT jump straight into design work, do NOT answer questions before the welcome runs
The welcome sequence checks for a returning user (taste profile at ~/.designpowers/taste-profile.md) and shows the appropriate welcome screen with the bird. First-time users get offered a guided walkthrough. This must happen before any design work begins.
Specifically: do NOT invoke design-discovery, design-strategy, design-memory, design-state, design-taste, or any other Designpowers skill until the welcome sequence has completed. The bird must appear. The user must see the greeting and the walkthrough offer. Only then can the pipeline begin. If any skill is invoked before the welcome, stop and run the welcome first.
Skills
All design skills live in skills/. The entry point is skills/using-designpowers/SKILL.md which orchestrates the entire workflow. Never bypass it.
Skills are markdown files. Read the SKILL.md for each skill before using it, and follow its instructions exactly. When the workflow calls for a skill, read the corresponding file in skills/<skill-name>/SKILL.md and do what it says.
Agents
Design agents live in agents/. They are invoked by the workflow — do not call them directly without going through the skill orchestration.
Agents are markdown files too. Each file in agents/ describes a specialist (design-strategist, design-lead, motion-designer, etc.). When the workflow hands off to an agent, read that agent's file and adopt its role, voice, and responsibilities for that part of the work.
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.
- 5d ago First seen · 36 lines · 569 tokens per session scan A 89f4c34b05de
designpowers GEMINI.md is an instructions file published in the GitHub repository Owl-Listener/designpowers (240 stars, last pushed 2mo ago), licensed MIT. It adds 569 tokens to every session, about $0.0028 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 instructions, from other repositories
pi-agent-dashboard AGENTS.md
AGENTS.md instructions for BlackBeltTechnology/pi-agent-dashboard, covering pi dashboard, docs-first gate — kb before grep (per-turn doctrine), code instructions (per-turn doctrine), investigation protocol — index first and documentation update protocol.
semantix CLAUDE.md
Claude Code instructions for Gnosil/semantix, covering 项目规则（claude code）, 1. 改动须经用户过目；由 claude 提交到分支 + pr，用户 review 后合并 and 2. 本地实验区：论文数据与实验材料不进 github.
rn-dev-agent AGENTS.md
AGENTS.md instructions for Lykhoyda/rn-dev-agent, covering repository guide for agents, repository map, editing rules, architecture rules and supported node runtimes.
nui CLAUDE.md
Claude Code instructions for plmbr/nui, covering claude.md, commands, backend (go), frontend (run from ui/) and full production build.
WorldLines AGENTS.md
AGENTS.md instructions for LudicDynamics/WorldLines, covering worldlines — 角色卡 / 世界卡创作工作台, 项目结构, 可用 skill, 怎么用 and 架构背景.
pi-agent-dashboard CLAUDE.md
Claude Code instructions for BlackBeltTechnology/pi-agent-dashboard, a project described as: Real-time web dashboard for pi coding-agent sessions. Multi-session view, live chat mirroring, integrated terminal, diff viewer, pi-flows execution, and mobile-first remote control via mDNS or zrok tunnel. Coexists with pi's…