using-designpowers

using-designpowers is a skill for Claude Code, Codex from Owl-Listener/designpowers. It costs 50 tokens per session (10,017 once invoked), scanned A, original, MIT.

A required entry point for the Designpowers design workflow system, which guides work from research and strategy through design, accessibility, critique, and handoff.

In plain words
What is it for?
It welcomes users, checks for a saved taste profile, and directs each design-related request to the appropriate first skill.
Why use it?
It ensures the correct design workflow starts before any other Designpowers skill and adapts the welcome process for new or returning users.

Skill for Claude CodeCodex

Part of the designpowers plugin — 36 skills, 10 agents, 1 hook shipped together

Install

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.

agentmods
npx agentmods add skills/owl-listener/designpowers/using-designpowers
Any agent
npx skills add Owl-Listener/designpowers --skill using-designpowers
Clone the repo
git clone --depth 1 https://github.com/Owl-Listener/designpowers

Made for: Claude Code, Codex.

Or install designpowers, the plugin that ships this one along with the rest of its 36 skills, 10 agents, 1 hook.

Wrote 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.

agentmods badge for using-designpowers

README.md
[![agentmods](https://agentmods.dev/badge/skills/owl-listener/designpowers/using-designpowers.svg)](https://agentmods.dev/skills/owl-listener/designpowers/using-designpowers)
Your own site
<a href="https://agentmods.dev/skills/owl-listener/designpowers/using-designpowers"><img src="https://agentmods.dev/badge/skills/owl-listener/designpowers/using-designpowers.svg" alt="Measured on agentmods" height="20"></a>
Per session 50 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 10,017 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00050 $0.10017
Opus 5 $0.00025 $0.05008
Sonnet 5 $0.00010 $0.02003
Haiku 4.5 $0.00005 $0.01002

Measured 3d ago against content hash 77f98d1eaa44, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

using-designpowers 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 3d 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.

skills/using-designpowers/SKILL.md · 805 lines

How it starts

The opening of the file, as written. The whole thing — 805 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Using Designpowers

Designpowers is a design workflow system. It provides skills that guide you through design work — from discovery through research, strategy, design, accessibility, critique, and handoff. These skills are not suggestions. They are mandatory workflows.

Welcome Sequence

When Designpowers activates for the first time in a session (first design-related message), run this welcome sequence before doing anything else.

Step 1: Check for Returning User

Before showing anything, check for an existing taste profile at ~/.designpowers/taste-profile.md. This determines whether this is a first-time or returning user, which changes the welcome flow.

Step 2: Show Welcome

For first-time users (no taste profile found), show this welcome:

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

                <o)
                /) )
              ==#===

  ▓▓▓▓  DESIGNPOWERS  ▓▓▓▓
  ━━━━━━━━━━━━━━━━━━━━━━━━

  Hey — welcome. You've got a design team now.

  Here's how it works: you describe what you want
  to build, and a team of 10 design agents works
  through it — research, strategy, visual design,
  content, accessibility, code. They talk to each
  other, hand off work, and check each other's
  output.

  You're the creative director. You can steer,
  correct, or override anything at any time.

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

For returning users (a design record exists), show this instead:

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

                <o)
                /) )
              ==#===

  ▓▓▓▓  DESIGNPOWERS  ▓▓▓▓
  ━━━━━━━━━━━━━━━━━━━━━━━━

  Welcome back. I've been keeping a record of how
  you design across your [Z] projects — your habits,
  the moves you reach for, how you tend to decide.

  [1-2 sentence observation, e.g., "You lean toward
  warm neutrals and generous whitespace, and you
  tend to settle structure before colour."]

  It's just a mirror — I don't apply it to your work,
  it's there if you're curious. Want to see your full
  design record? Otherwise, let's get into it.

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Read the full file on GitHub · 805 lines

Changes

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.

  1. 3d ago First seen · 805 lines · 50 tokens per session scan A 77f98d1eaa44

Subscribe to this mod's changes

using-designpowers is a skill published in the GitHub repository Owl-Listener/designpowers (240 stars, last pushed 2mo ago), licensed MIT. It adds 50 tokens to every session and 10,017 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.

Related

Other skills, from other repositories

doubt-driven-review

In-flight adversarial check on a non-trivial decision BEFORE it stands — distinct from post-hoc review of a finished diff. Use on "stress-test this decision", "are we sure about this", "verify before commit", "poke holes in this", when working in unfamiliar code, or before an irreversible step (migration, prod deploy…

BlackBeltTechnology/pi-agent-dashboard · 90 tokens

release-cut

Cut a new pi-agent-dashboard release: promote ## [Unreleased] in CHANGELOG.md, bump every workspace package.json per SemVer, commit, tag v , and push — triggering the Release workflow that publishes every non-private workspace, builds the Electron artifacts, and creates a GitHub Release. Use on "cut a release"…

BlackBeltTechnology/pi-agent-dashboard · 93 tokens

ship-it

Worktree-side implementation orchestrator for an OpenSpec change. Idempotent: gates automated scenarios on filesystem reality, owns the red-test fix loop, runs the docker harness with always-teardown, then drives ship-change inline. Escape hatch writes SHIPITBLOCKED.md. Runnable headless. Triggers: "ship it", "build…

BlackBeltTechnology/pi-agent-dashboard · 92 tokens

faq-mine

Mine docs/faq.md from README.md, docs/.md, and the pi-hermes memory stores. Dispatches @fast subagents per source, dedupes against the existing FAQ, and merges entries in caveman style. Use when asked to "build / regenerate / extend the FAQ", "mine docs into FAQ", "mine hermes memory into FAQ", "surface runtime…

BlackBeltTechnology/pi-agent-dashboard · 94 tokens

session-to-guideline

Turn a pi session into a Markdown "how-we-did-it" collaboration guideline: reads the session's JSONL transcript and synthesizes a reusable playbook of which prompts worked, what had to be steered, and how to reproduce the result faster. Use when: "document this session", "write up how we did X with the AI", "make a…

BlackBeltTechnology/pi-agent-dashboard · 93 tokens

scenario-design

Draft real-life test SCENARIOS (not smoke tests) from a change/feature spec. Derives edge-case, performance, frontend-quirk and error-handling scenarios with ISTQB techniques, routes each to a test level, and writes test-plan.md, emitting clarification questions on a spec gap. Use on "design test scenarios", "what…

BlackBeltTechnology/pi-agent-dashboard · 88 tokens