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/contextualize)<a href="https://agentmods.dev/commands/appboypov/pew-pew-plaza-packs/contextualize"><img src="https://agentmods.dev/badge/commands/appboypov/pew-pew-plaza-packs/contextualize/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/contextualize"><img src="https://agentmods.dev/badge/commands/appboypov/pew-pew-plaza-packs/contextualize.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.00032 | $0.14514 |
| Opus 5 | $0.00016 | $0.07257 |
| Sonnet 5 | $0.00006 | $0.02903 |
| Haiku 4.5 | $0.00003 | $0.01451 |
Grade A, and why
contextualize 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 7d 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.
This is a copy
84% identical to question-mode — 806 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 1,689 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.
🔍 Contextualize: Deep Project Research & Document Enhancement
💡 Transform any concept or document into a fully contextualized artifact by researching project patterns, conventions, and relationships, then updating the source with comprehensive context.
🎯 End Goal
💡 The clean, measurable objective that determines whether any following section provides value.
Successfully contextualize any document (meta-concept or otherwise) by:
- Understanding the source document's core purpose and current context
- Researching comprehensively across the entire project for patterns and relationships
- Applying feedback strategies to refine understanding through systematic questioning
- Updating the source document(s) with enhanced context, relationships, and cross-references
- Ensuring the document aligns with all project conventions and integrates seamlessly
Deliverables
- Enhanced source document(s) with comprehensive contextual understanding
- Cross-references to related project artifacts via wikilinks
- Usage examples discovered from project research
- Alignment with established project patterns and conventions
- Clear relationships to other framework components
Acceptance Criteria
- Source document purpose is fully understood
- Comprehensive project research is completed across all relevant artifact types
- Question-mode refinement reveals additional context needs
- Source document is updated (not replaced) with enhanced context
- All wikilinks and cross-references are properly integrated
- Document follows project conventions exactly
- Relationships to other concepts are clearly documented
👤 Persona
Role
Deep Research Analyst and Documentation Enhancement Specialist
Expertise
- Comprehensive understanding of PLX framework structure and components
- Pattern recognition across different artifact types
- Document analysis and contextual relationship mapping
- Project convention alignment and consistency validation
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.
- 7d ago First seen · 1,689 lines · 32 tokens per session scan A d205114cbe8e
contextualize is a command published in the GitHub repository appboypov/pew-pew-plaza-packs (85 stars, last pushed 8mo ago), licensed MIT. It adds 32 tokens to every session and 14,514 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 84% identical to question-mode, differing in 806 lines, and is treated as a copy.
Other commands, from other repositories
security
Rapid security assessment focused on OWASP Top 10 vulnerabilities.
costs
Open ccboard costs analysis tab.
content-idea
Content idea generation command. Creates a structured idea list for a topic, theme, or platform.
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.