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 studiomeyer-io/studiomeyer-marketplace --skill persona-usagegit clone --depth 1 https://github.com/studiomeyer-io/studiomeyer-marketplaceWrote 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/studiomeyer-io/studiomeyer-marketplace/persona-usage)<a href="https://agentmods.dev/skills/studiomeyer-io/studiomeyer-marketplace/persona-usage"><img src="https://agentmods.dev/badge/skills/studiomeyer-io/studiomeyer-marketplace/persona-usage/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/studiomeyer-io/studiomeyer-marketplace/persona-usage"><img src="https://agentmods.dev/badge/skills/studiomeyer-io/studiomeyer-marketplace/persona-usage.svg" alt="Reviewed on agentmods" width="80" 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.00048 | $0.01175 |
| Opus 5.5 | $0.00019 | $0.00470 |
| Sonnet 5.5 | $0.00010 | $0.00235 |
| Haiku 4.5 | $0.00005 | $0.00118 |
Grade A, and why
persona-usage 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 1mo 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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Persona Usage Guide
Crew turns Claude into a specialist with a focused prompt, decision framework, and output format. This skill is the decision tree for picking the right one.
When to use a persona at all
A persona is worth activating when one specialist perspective will produce a better answer than general Claude. Good signals:
- The user asks a question framed from a specific role's viewpoint ("how would a CFO evaluate this?")
- The task has a canonical framework in that domain (RICE/ICE for PM, DORA for CTO, AARRR for CMO)
- The output format matters (financial tables for CFO, user stories for PM, creative briefs for Creative Director)
- The conversation will span multiple messages in that role, 5+ minutes of specialist work
Bad signals for activation:
- Simple factual question: stay in default Claude
- Mixed-domain question: do not switch mid-answer, stay general
- User just wants information, not a decision: default works
When to pick which persona
| User asks about... | Activate |
|---|---|
| Strategy, vision, delegation, board-level priorities | CEO |
| Pricing, ROI, budgets, financial modeling, revenue decisions | CFO |
| Marketing, growth, SEO, content strategy, positioning | CMO |
| Architecture, code review, tech debt, system design | CTO |
| Feature prioritization, PRDs, user stories, JTBD, roadmaps | PM |
| Market research, competitive analysis, data interpretation | Research Analyst |
| Brand voice, visual direction, copy, storytelling | Creative Director |
| Customer communication, docs, FAQ, onboarding flow | Support Lead |
Workflows: when one persona is not enough
Three built-in workflows chain personas for complex tasks:
strategy-review (CEO → CFO → CTO)
Use when the user has a strategic option and needs a go/no-go. CEO articulates the strategic case, CFO evaluates financial viability, CTO checks technical feasibility. Output is a unified verdict.
content-pipeline (CMO → Analyst → Creative)
Use when the user wants to produce content but has only a topic. CMO sets the strategic angle, Analyst fact-checks, Creative polishes for voice and hook. Output is a ready-to-publish piece.
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.
- 1mo ago Changed a899b65780d7
- 1mo ago First seen · 91 lines · 48 tokens per session scan A 120ea95ac1fc
persona-usage is a skill published in the GitHub repository studiomeyer-io/studiomeyer-marketplace (2 stars, last pushed 5d ago), licensed MIT. It adds 48 tokens to every session and 1,175 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-08-31.
Other skills, from other repositories
gemini
Cross-model second opinion from Google Gemini — a different AI reviewing the same changes, with deep Google ecosystem knowledge. Three modes: review (pass/fail gate for Google Ads campaigns, SEO metadata, or code), challenge (adversarial stress-test that tries to break your changes), and consult (open Q&A with Gemini…
backlink-audit
Backlink / off-page SEO audit. Works WITHOUT a paid tool by default — it uses the Google Search Console Links report (your top linking sites, most-linked pages, and anchor text) plus any backlink export the user provides (Ahrefs / Semrush / Majestic / DataForSEO CSV). Analyzes referring-domain profile, anchor-text…
competitor-pages
Competitor page gap analysis — take a query you want to win and the pages currently outranking you, and produce a concrete brief on what to add or change to compete. Compares content depth and coverage (subtopics they cover that you don't), structure (headings, format, tables, media), search-intent match, E-E-A-T…
hreflang-international
International / multilingual SEO audit focused on hreflang correctness: missing or broken return tags, wrong language/region codes, missing x-default, self-referencing errors, hreflang vs canonical conflicts, and inconsistent signals across HTML head, HTTP headers and XML sitemap. Also reviews URL structure (ccTLD vs…
seo-drift
SEO drift monitoring — snapshot a site's SEO state and detect regressions over time. Captures a baseline (rankings/positions, indexed page count, titles & meta descriptions, canonical/robots directives, schema presence, key on-page elements) and on later runs diffs against it to surface what changed: ranking drops…
sitemap-audit
XML sitemap audit — find and fix the sitemap problems that quietly waste crawl budget and slow indexing. Discovers the sitemap (robots.txt, /sitemap.xml, sitemap index), validates structure and size limits, and cross-checks the URLs it lists against reality: non-200 / redirected / noindex / canonicalized-away URLs…