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 skills add Owl-Listener/designpowers --skill research-planninggit 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/skills/owl-listener/designpowers/research-planning)<a href="https://agentmods.dev/skills/owl-listener/designpowers/research-planning"><img src="https://agentmods.dev/badge/skills/owl-listener/designpowers/research-planning/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/skills/owl-listener/designpowers/research-planning"><img src="https://agentmods.dev/badge/skills/owl-listener/designpowers/research-planning.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00037 | $0.00783 |
| Opus 5 | $0.00018 | $0.00392 |
| Sonnet 5 | $0.00007 | $0.00157 |
| Haiku 4.5 | $0.00004 | $0.00078 |
Grade A, and why
research-planning 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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Research Planning
Research is how we replace assumptions with evidence. This skill structures what you need to learn before committing to a design direction.
When to Use
- The design brief identifies unknowns about users, context, or behaviour
- The team is making decisions based on assumptions rather than evidence
- A design is being created for a new audience or unfamiliar context
- Stakeholders disagree about user needs
Process
Step 1: Identify Knowledge Gaps
Review the design brief and list:
- What do we know about the people who will use this? (Evidence-backed)
- What do we assume? (Believed but unverified)
- What do we not know? (Acknowledged gaps)
Present this to the user. Assumptions and unknowns become research questions.
Step 2: Frame Research Questions
Convert gaps into answerable questions. Good research questions are:
- Specific — "How do users with screen readers navigate multi-step forms?" not "Is the form accessible?"
- Observable — focused on behaviour, not opinion
- Actionable — the answer will change a design decision
Aim for 3-5 research questions. More than that means you need to narrow scope.
Step 3: Select Methods
Match methods to questions:
| Question Type | Recommended Methods |
|---|---|
| "What do people currently do?" | Journey mapping, diary studies, contextual inquiry |
| "Why do people struggle with X?" | Usability testing, think-aloud protocols |
| "What do people need?" | Interviews, jobs-to-be-done analysis |
| "Which approach works better?" | A/B testing, preference testing, card sorting |
| "How does our offering compare?" | Competitive analysis, heuristic evaluation |
| "Who are we designing for?" | Persona development, ability spectrum mapping |
Step 4: Plan for Inclusion
Every research plan must address:
- Participant diversity — include people with disabilities, different ages, different technical literacy, different languages
- Method accessibility — ensure research methods themselves are accessible (e.g., interview formats that work for people with communication differences)
- Situational contexts — include scenarios of stress, distraction, low bandwidth, unfamiliar environments
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 · 97 lines · 37 tokens per session scan A 705fb38576cf
research-planning is a skill published in the GitHub repository Owl-Listener/designpowers (243 stars, last pushed 2mo ago), licensed MIT. It adds 37 tokens to every session and 783 once invoked, about $0.0002 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 skills, from other repositories
semantix
Install and use the semantix memory kernel as a middleware in your agent: extract user preferences / workflows / experience from past sessions, retrieve and inject them on demand. One binary + your agent's own tools.
semantix-guide
Troubleshoot and configure Semantix capabilities: Skills (project/custom/global/builtin priority, discovery dirs), Commands (override order, /dir:file naming), Hooks (11 events, automatic project loading, matchers, timeouts), MCP (semantix-agent.toml + .mcp.json + plugin packages, autostart), plugin packages…
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…
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"…
spec-coherence-check
Sweep all active OpenSpec proposals for staleness, conflicts, and obsolescence against the current codebase and archived changes. Use when proposals may be outdated, when checking cross-proposal conflicts, or before starting a batch of implementations. Produces a gap-analysis report, updates a priority queue file, and…
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…