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.
git clone --depth 1 https://github.com/appboypov/pew-pew-plaza-packsWrote 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/commands/appboypov/pew-pew-plaza-packs/actor)<a href="https://agentmods.dev/commands/appboypov/pew-pew-plaza-packs/actor"><img src="https://agentmods.dev/badge/commands/appboypov/pew-pew-plaza-packs/actor/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/commands/appboypov/pew-pew-plaza-packs/actor"><img src="https://agentmods.dev/badge/commands/appboypov/pew-pew-plaza-packs/actor.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.00020 | $0.01287 |
| Opus 5 | $0.00010 | $0.00643 |
| Sonnet 5 | $0.00004 | $0.00257 |
| Haiku 4.5 | $0.00002 | $0.00129 |
Grade A, and why
create-actor 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 9d 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 — 181 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Prompt Command
When this command is used, check if any required information is missing. If so, ask the user to provide it. Otherwise, proceed with the request.
🎭 Create Actor Document
💡 Transform requirements into a well-defined actor that references roles using the established hierarchy.
🎯 End Goal
💡 The measurable objective that determines whether any following section provides value.
Successfully create a production-ready actor document that:
- Clearly defines the actor's identity and purpose
- References appropriate roles via flat wikilinks
- Follows the Actor→Role→Interaction hierarchy
- Integrates seamlessly with existing project structure
- Maintains proper wikilink conventions
Deliverables
- Complete actor document following actor-template structure
- Proper YAML frontmatter with name and description
- Clear purpose statement
- Key roles section with proper wikilink references
- Saved to /actors/ directory
Acceptance Criteria
- Actor identity clearly defined (person/system/entity)
- Purpose statement is concise and focused
- References roles (not interactions directly)
- Uses flat wikilinks without folder paths
- Follows naming conventions
- Saved with proper filename format
📋 Request
💡 Verb-first activity request with clear scope
Create a new actor document based on user requirements through systematic analysis and role identification.
🔄 Workflow
💡 Systematic methodology for actor creation following project hierarchy.
Step 1: Clarify Actor Identity
Deliverable: Clear understanding of actor type and core purpose Acceptance Criteria: Actor type and primary goal identified
If requirements are unclear, ask ONE focused question:
## 🎭 What type of actor are we creating?
A. Person (user, customer, staff member, expert)
B. System (application, service, platform, tool)
C. External Entity (organization, partner, regulatory body)
Step 2: Define Purpose and Context
Deliverable: Core purpose statement and project context Acceptance Criteria: Purpose clearly articulated in one sentence
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.
- 9d ago First seen · 181 lines · 20 tokens per session scan A 8c11ce3c8722
create-actor is a command published in the GitHub repository appboypov/pew-pew-plaza-packs (85 stars, last pushed 8mo ago), licensed MIT. It adds 20 tokens to every session and 1,287 once invoked, about $0.0001 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 commands, from other repositories
worktree-cleanup
A command for removing a Git worktree, which is a separate working folder linked to the same repository, after its pull request is merged.
costs
Open ccboard costs analysis tab.
mobile
Mobile project management command. React Native/Flutter/Expo/Swift/Kotlin scaffolding, version sync, build and release guides.
env-check
.env file validation. Detects missing, extra, empty, and placeholder values + .gitignore check.
callee-create-agent
Create a Callee agent or deterministic workflow.
ship
Ship command. Runs the pre-flight gate, decides the version bump, assembles the changelog, and opens the PR via the release-manager agent. Nothing ships unless the gate is green.