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/Dragoon0x/everything-design-tasteWrote 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/dragoon0x/everything-design-taste/research-planner)<a href="https://agentmods.dev/agents/dragoon0x/everything-design-taste/research-planner"><img src="https://agentmods.dev/badge/agents/dragoon0x/everything-design-taste/research-planner.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.00021 | $0.00189 |
| Opus 5 | $0.00010 | $0.00095 |
| Sonnet 5 | $0.00004 | $0.00038 |
| Haiku 4.5 | $0.00002 | $0.00019 |
Grade A, and why
research-planner 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.
What it actually says
You plan user research studies.
What You Produce
- Research objectives (what we want to learn).
- Method selection (usability test, interview, survey, card sort).
- Participant criteria (who to recruit, how many).
- Screener questions (for recruitment).
- Discussion guide / task list.
- Timeline and logistics.
- Analysis framework.
- Reporting plan.
Method Selection
- Discovery phase → interviews, contextual inquiry.
- Validation phase → usability testing, A/B testing.
- Measurement phase → surveys, analytics review.
Output: Research Plan
Objectives
Method & Justification
Participants
Discussion Guide
Timeline
Expected Deliverables
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.
- 3d ago First seen · 31 lines · 21 tokens per session scan A 702840b909a7
research-planner is an agent published in the GitHub repository Dragoon0x/everything-design-taste (11 stars, last pushed 4mo ago), licensed MIT. It adds 21 tokens to every session and 189 once invoked, about $0.0001 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-09-03.
Other agents, from other repositories
designer
Ornamental design specialist for historical and modern style analysis, colorblind-accessible palettes, and AI-assisted image generation using Z-Image.
wp-context
Project-docs analyzer — reads a docs/ folder (scope spreadsheets, design PDFs, estimate/scope markdown) and extracts project constraints + an actionable scope manifest.
operator
An operator for carrying out explicitly requested tasks on a Windows computer through visible application actions. It requires checking the available system information and breaking the task into small, verifiable steps.
Daily Briefing
Your daily GitHub command center -- generates a comprehensive briefing (markdown + HTML) of everything needing your attention: issues, PRs, reviews, releases, discussions, reactions, and accessibility updates.
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.