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 agentmods add skills/p47phoenix/claude-plugins/alias-creatornpx skills add P47Phoenix/Claude-Plugins --skill alias-creatorgit 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/alias-creator)<a href="https://agentmods.dev/skills/p47phoenix/claude-plugins/alias-creator"><img src="https://agentmods.dev/badge/skills/p47phoenix/claude-plugins/alias-creator.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 | $0.00087 | $0.01937 |
| Opus 5 | $0.00044 | $0.00968 |
| Sonnet 5 | $0.00017 | $0.00387 |
| Haiku 4.5 | $0.00009 | $0.00194 |
Grade A, and why
alias-creator 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 yesterday.
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 — 200 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Alias Theme Creator
Create, edit, preview, and manage agent alias themes for the delivery team pipeline.
What Are Alias Themes?
Alias themes give each delivery team role a themed character name and personality. When a theme is active, every sub-agent speaks in character — Gandalf gives wise product advice, Gimli builds code with directness, Legolas catches bugs with elven precision.
Built-in themes are in delivery-flow/references/aliases/. Custom themes are stored per-repo in .delivery/aliases/.
Creating a Custom Theme
Interactive Creation
Walk the user through creating a theme step by step:
- Theme identity: Ask for theme name (kebab-case), display name, and personality strength (light/moderate/full)
- For each of the 13 roles, ask:
- Character name
- Personality description (1-2 sentences)
- Catchphrase (or "none")
- Communication style (free text)
- 2 example voice lines (how this character talks about delivery work)
- Validate: All 13 roles mapped, all required fields present
- Write: Save to
.delivery/aliases/<theme-name>.yml
Quick Creation from Description
If the user provides a theme concept (e.g., "Harry Potter theme"), generate all 13 role mappings automatically:
- Map each role to the best-fitting character based on traits
- Write personality notes that match the character's known behavior
- Generate catchphrases adapted from source material
- Present the full mapping for user review before saving
- User can edit individual roles before finalizing
Partial Themes
Themes don't need all 13 roles. Unmapped roles fall back to the Business theme. Mark partial themes:
theme: my-partial-theme
display_name: "My Partial Theme"
personality_strength: moderate
min_roles_version: 13
partial: true # indicates not all roles are mapped
The 13 Delivery Team Roles
Every theme maps these roles:
| Role ID | Role Name | What They Do |
|---|---|---|
product-owner |
Product Owner | Business value, user stories, PRDs, backlogs |
scrum-master |
Scrum Bag | Process facilitation, retros, velocity, ceremonies |
data-analyst |
Data Analyst | Metrics, analytics, A/B testing, dashboards |
developer |
Developer | Code implementation across 14 languages |
architect |
Architect | System design, ADRs, decomposition, C4 models |
qa-engineer |
QA Engineer | Test strategy, test cases, quality metrics |
devops |
DevOps Engineer | CI/CD, deployment, infrastructure, monitoring |
release-manager |
Release Manager | Release planning, versioning, rollback, feature flags |
tech-writer |
Technical Writer | API docs, user guides, runbooks, release notes |
ux-designer |
UX Designer | User flows, wireframes, usability, research |
ui-designer |
UI Designer | Design systems, components, accessibility, interactions |
game-ui-designer |
Game UI Designer | HUD, menus, inventory UI, game accessibility |
user-feedback |
User Feedback | Feedback facilitator (personas keep their own identities) |
What ships with it
1 file 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.
- yesterday First seen · 200 lines · 87 tokens per session scan A eca06fba5a57
alias-creator is a skill published in the GitHub repository P47Phoenix/Claude-Plugins (2 stars, last pushed 3mo ago), licensed MIT. It adds 87 tokens to every session and 1,937 once invoked, about $0.0004 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
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…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…