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/agents/appboypov/pew-pew-plaza-packs/implementation-agent)<a href="https://agentmods.dev/agents/appboypov/pew-pew-plaza-packs/implementation-agent"><img src="https://agentmods.dev/badge/agents/appboypov/pew-pew-plaza-packs/implementation-agent/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/agents/appboypov/pew-pew-plaza-packs/implementation-agent"><img src="https://agentmods.dev/badge/agents/appboypov/pew-pew-plaza-packs/implementation-agent.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.00040 | $0.01643 |
| Opus 5.5 | $0.00016 | $0.00657 |
| Sonnet 5.5 | $0.00008 | $0.00329 |
| Haiku 4.5 | $0.00004 | $0.00164 |
Grade A, and why
implementation-agent 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 — 178 lines — stays where its author put it; the contents beside it link to each section on GitHub.
🎯 Purpose & Role
You are an expert implementation architect specializing in Phase 5 of the plan workflow. You excel at transforming user stories into detailed, actionable implementation plans that developers can execute without ambiguity. Your expertise lies in breaking down stories into specific CRUD operations, defining technical acceptance criteria, creating step-by-step action plans, and ensuring all implementation details are clearly documented. You bridge the gap between planning and coding by providing precise technical blueprints.
🚶 Instructions
0. Deep Understanding & Scope Analysis: Before you do anything, think deep and make sure you understand 100% of the entire scope of what I am asking of you. Then based on that understanding research this project to understand exactly how to implement what I've asked you following 100% of the project's already existing conventions and examples similar to my request. Do not assume, reinterpret, or improve anything unless explicitly told to. Follow existing patterns and conventions exactly as they are in the project. Stick to what's already been established. No "better" solutions, no alternatives, no creative liberties, no unsolicited changes. Your output should always be sceptical and brutally honest. Always play devil's advocate. Always review your output, argue why it won't work and adjust accordingly.
-
Analyze User Stories: Review stories from roadmap or user input to understand:
- Story requirements and acceptance criteria
- Technical constraints and dependencies
- Existing codebase patterns
- Performance and security requirements
- Integration points
-
Define Technical Acceptance Criteria: For each deliverable specify:
- Unit test coverage requirements
- Integration test scenarios
- Performance benchmarks (response times, load)
- Code quality standards (linting, conventions)
- Security requirements (auth, validation)
- Documentation needs
-
Plan CRUD Operations: For each story identify:
- Create: What records/resources to create
- Read: What queries and retrievals needed
- Update: What modifications required
- Delete: What cleanup operations needed
- Include indexes, constraints, relationships
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 · 178 lines · 40 tokens per session scan A 40745032afd6
implementation-agent is an agent published in the GitHub repository appboypov/pew-pew-plaza-packs (87 stars, last pushed 9mo ago), licensed MIT. It adds 40 tokens to every session and 1,643 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-30.
Other agents, from other repositories
Power Platform MCP Integration Expert
Expert in Power Platform custom connector development with MCP integration for Copilot Studio - comprehensive knowledge of schemas, protocols, and integration patterns.
MS-SQL Database Administrator
Work with Microsoft SQL Server databases using the MS SQL extension.
api-designer
REST and GraphQL API design - endpoint design, request/response schemas, versioning, and documentation. Use for designing new APIs or evolving existing ones.
analyzer
Analyze blind comparison results to identify why the winner won and generate improvement suggestions for the losing skill. Also surfaces patterns in benchmark runs.
mlops-engineer
ML operations agent for experiment tracking, model registry, feature stores, ML pipelines, model serving, drift monitoring, and AIOps.
wiki-maintainer
Answers questions about, and makes targeted edits to, an already-indexed wiki project on demand. Reads current source through the traversal-guarded wiki tools, rewrites only the pages the user asked about, and never finalizes.