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 derricktang/pm-workflow-plugin --skill proto-personagit clone --depth 1 https://github.com/derricktang/pm-workflow-pluginWrote 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/derricktang/pm-workflow-plugin/proto-persona)<a href="https://agentmods.dev/skills/derricktang/pm-workflow-plugin/proto-persona"><img src="https://agentmods.dev/badge/skills/derricktang/pm-workflow-plugin/proto-persona.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.00032 | $0.02738 |
| Opus 5 | $0.00016 | $0.01369 |
| Sonnet 5 | $0.00006 | $0.00548 |
| Haiku 4.5 | $0.00003 | $0.00274 |
Grade A, and why
proto-persona 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 8d 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.
This is a copy
95% identical to proto-persona — 3 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 330 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
Create an initial, assumption-based persona profile that synthesizes available user research, market data, and stakeholder knowledge into a working hypothesis about your target user. Use this to align teams early in product development, guide initial design decisions, and identify gaps in understanding that require validation through research.
This is not a validated persona—it's a "proto" (prototype) persona that evolves as you learn more. Think of it as a structured placeholder that prevents design-by-committee while acknowledging you don't have all the answers yet.
Key Concepts
What is a Proto-Persona?
A proto-persona is a lightweight, hypothesis-driven persona created from:
- Existing research: User interviews, surveys, analytics (if available)
- Market data: Industry reports, competitor analysis, demographic trends
- Stakeholder knowledge: Sales, support, and team insights
- Informed assumptions: Best guesses that need validation
Proto vs. Validated Persona
| Proto-Persona | Validated Persona |
|---|---|
| Created in hours/days | Created over weeks/months |
| Based on assumptions + limited research | Based on extensive user research |
| Used to align teams early | Used to guide detailed design |
| Evolves rapidly | Stable over time |
| Good enough to start | High confidence |
Why Use Proto-Personas?
- Speed: Align teams quickly without waiting for months of research
- Focus: Provides a shared reference point for "who we're building for"
- Hypothesis framing: Makes assumptions explicit, which can then be validated
- Prevents generic design: "Design for everyone" = design for no one
Anti-Patterns (What This Is NOT)
- Not validated research: Don't treat it as fact—it's a hypothesis
- Not a replacement for user research: Use it to guide research, not avoid it
- Not demographic data alone: Age and location don't explain behavior
- Not permanent: Proto-personas should evolve as you learn
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 8d ago First seen · 330 lines · 32 tokens per session scan A 0937ef48256e
proto-persona is a skill published in the GitHub repository derricktang/pm-workflow-plugin (2 stars, last pushed 2mo ago), licensed MIT. It adds 32 tokens to every session and 2,738 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 95% identical to proto-persona, differing in 3 lines, and is treated as a copy.
Other skills, from other repositories
mcp-builder
Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).
last30Days
Resolve "last30Days" to a concrete ISO date range relative to your run time — a rolling 30-day window ending today. Returns inclusive civil dates plus exact UTC instants so you have temporal context without computing dates by hand. Read-only: no writes, no network. Use before a "last 30 days" / trailing-month task…
thisWeek
Resolve "thisWeek" to a concrete ISO date range relative to your run time — this week so far (Monday → today). Returns inclusive civil dates plus exact UTC instants so you have temporal context without computing dates by hand. Read-only: no writes, no network. Use before a week-to-date task (this week's activity…
subagent-driven-development
Use when executing implementation plans with independent tasks in the current session.
comet-hotfix
A quick workflow for fixing an existing bug in Comet, a tool that manages structured code changes. It moves through opening the change, building, checking, and archiving it.
comet-verify
Comet Phase 4: Verify and Close. Invoke with /comet-verify. Verify implementation matches design, handle development branch.