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 P47Phoenix/Claude-Plugins --skill web-appgit clone --depth 1 https://github.com/P47Phoenix/Claude-PluginsWrote 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/p47phoenix/claude-plugins/web-app)<a href="https://agentmods.dev/skills/p47phoenix/claude-plugins/web-app"><img src="https://agentmods.dev/badge/skills/p47phoenix/claude-plugins/web-app/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/p47phoenix/claude-plugins/web-app"><img src="https://agentmods.dev/badge/skills/p47phoenix/claude-plugins/web-app.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.00075 | $0.00471 |
| Opus 5.5 | $0.00030 | $0.00188 |
| Sonnet 5.5 | $0.00015 | $0.00094 |
| Haiku 4.5 | $0.00007 | $0.00047 |
Grade A, and why
user-feedback-personas-web-app 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.
What it actually says
Web/App User Personas Sub-Skill
Router-dispatched paradigm sub-skill for web/app user persona feedback. Not directly invokable by the model; the user-feedback parent skill loads this sub-skill only when project type is GREENFIELD, FEATURE, or WEB_APP.
Personas Covered
| Persona | Profile Section |
|---|---|
| Power User Pat | references/persona-library.md § Category 2: Web/App Users → Power User Pat |
| Average User Avery | references/persona-library.md § Category 2: Web/App Users → Average User Avery |
| First-Timer Fran | references/persona-library.md § Category 2: Web/App Users → First-Timer Fran |
| Non-Technical Nancy | references/persona-library.md § Category 2: Web/App Users → Non-Technical Nancy |
| Accessible User Ash | references/persona-library.md § Category 2: Web/App Users → Accessible User Ash (mandatory accessibility persona for web/app projects) |
Reference paths above resolve relative to the parent skill delivery-team/skills/user-feedback/.
Invocation Pattern
Load ../../references/persona-invocation.md for the shared persona-agent prompt template and overlay handling. Then load the specific persona profile from the parent skill's references/persona-library.md Category 2 block. Spawn one sub-agent per persona per the parent skill's Phase 3 procedure.
Web/App Context Hints
When preparing the artifact for web/app personas, include device targets (desktop/tablet/mobile), browser/runtime support, and any onboarding flows. Accessible User Ash must be included in every web/app focus group regardless of count.
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 First seen · 35 lines · 75 tokens per session scan A 1a76368a86e3
user-feedback-personas-web-app is a skill published in the GitHub repository P47Phoenix/Claude-Plugins (2 stars, last pushed 2d ago), licensed MIT. It adds 75 tokens to every session and 471 once invoked, about $0.0003 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
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…