dev-swarm-stage-personas

dev-swarm-stage-personas is a skill for Claude Code, Codex from X-School-Academy/skill-pilot. It costs 51 tokens per session (1,140 once invoked), scanned A, original, MIT.

A workflow skill for creating user personas, user stories, and user journey maps from market research and business requirements. A persona is a description of a typical target user and their needs.

In plain words
What is it for?
It is for defining target users, documenting their stories, and mapping their interactions with a product.
Why use it?
It helps turn research and business goals into a clearer account of who the product serves and what those people need. It also checks earlier project stages before proceeding.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit It is for defining target users, documenting their stories, and mapping their interactions with a product.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/x-school-academy/skill-pilot/dev-swarm-stage-personas
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.

Any agent
npx skills add X-School-Academy/skill-pilot --skill dev-swarm-stage-personas
Clone the repo
git clone --depth 1 https://github.com/X-School-Academy/skill-pilot

Made for: Claude Code, Codex.

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 dev-swarm-stage-personas

README.md
[![agentmods](https://agentmods.dev/badge/skills/x-school-academy/skill-pilot/dev-swarm-stage-personas/github.svg)](https://agentmods.dev/skills/x-school-academy/skill-pilot/dev-swarm-stage-personas)
Your own site
<a href="https://agentmods.dev/skills/x-school-academy/skill-pilot/dev-swarm-stage-personas"><img src="https://agentmods.dev/badge/skills/x-school-academy/skill-pilot/dev-swarm-stage-personas/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.

agentmods 80×15 button for dev-swarm-stage-personas

Your own site · 80×15
<a href="https://agentmods.dev/skills/x-school-academy/skill-pilot/dev-swarm-stage-personas"><img src="https://agentmods.dev/badge/skills/x-school-academy/skill-pilot/dev-swarm-stage-personas.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 51 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,140 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00051 $0.01140
Opus 5.5 $0.00020 $0.00456
Sonnet 5.5 $0.00010 $0.00228
Haiku 4.5 $0.00005 $0.00114

Measured 16d ago against content hash 35fb30be6d0b, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

dev-swarm-stage-personas 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 16d 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.

dev-swarm/skills/dev-swarm-stage-personas/SKILL.md · 142 lines

How it starts

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

Stage 02 - Personas

Create/Update detailed user personas and user stories to deeply understand target users' needs, behaviors, pain points, and goals.

When to Use This Skill

  • User asks to start stage 02 (personas)
  • User wants to create/update user personas or user stories
  • User wants to map user journeys or empathy maps

Your Roles in This Skill

See dev-swarm/docs/general-dev-stage-rule.md for role selection guidance.

Role Communication

See dev-swarm/docs/general-dev-stage-rule.md for the required role announcement format.

Pre-Stage Check

Before starting, verify previous stages:

  1. Check if 00-init-ideas/ folder has content (not just .gitkeep)
  2. Check if 01-market-research/ folder has content
  3. If any previous stage is empty and has no SKIP.md:
    • Ask user: "Stage {XX} is not complete. Would you like to skip it or start from that stage first?"

Instructions

Step 1: Context Review

Read all files to understand the project:

  • ideas.md
  • 00-init-ideas/*.md - All markdown files
  • 01-market-research/*.md - All markdown files

Step 2: Create Stage Proposal

General Rules: See dev-swarm/docs/general-dev-stage-rule.md → "Create Stage Proposal Rules" section.

If this stage is skipped (has SKIP.md), execute the next non-skipped stage's agent skill. Otherwise, create the file 02-personas/README.md with the following content:

2.1 Stage Goal

Brief the goal in 2-3 paragraphs:

  • What this stage aims to achieve
  • Why user personas are critical for product success
  • How this builds upon previous stages
  • What deliverables will be produced
2.2 File Selection

Select files from these options based on project needs:

User Research & Personas:

  • personas.md - Detailed user personas with demographics, behaviors, motivations
  • pain-points.md - Comprehensive list of user pain points
  • empathy-maps/ - Diagrams visualizing what users say, think, do, and feel

User Stories & Journeys:

  • user-stories.md - Stories in "As a [persona], I want to [action], so that [benefit]" format
  • user-journey-maps/ - Journey diagrams showing user interactions
  • use-cases.md - Detailed use cases for different personas

Read the full file on GitHub · 142 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. 16d ago First seen · 142 lines · 51 tokens per session scan A 35fb30be6d0b

Subscribe to this mod's changes

dev-swarm-stage-personas is a skill published in the GitHub repository X-School-Academy/skill-pilot (20 stars, last pushed 4mo ago), licensed MIT. It adds 51 tokens to every session and 1,140 once invoked, about $0.0002 per session on Opus 5.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-10-02.

Related

Other skills, from other repositories

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

chronicle

Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…

microsoft/vscode · 72 tokens

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

component-fixtures

Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.

microsoft/vscode · 53 tokens