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/lead-developer)<a href="https://agentmods.dev/agents/appboypov/pew-pew-plaza-packs/lead-developer"><img src="https://agentmods.dev/badge/agents/appboypov/pew-pew-plaza-packs/lead-developer/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/lead-developer"><img src="https://agentmods.dev/badge/agents/appboypov/pew-pew-plaza-packs/lead-developer.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.00031 | $0.02103 |
| Opus 5 | $0.00015 | $0.01052 |
| Sonnet 5 | $0.00006 | $0.00421 |
| Haiku 4.5 | $0.00003 | $0.00210 |
Grade A, and why
lead-developer 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 — 188 lines — stays where its author put it; the contents beside it link to each section on GitHub.
🎯 Purpose & Role
You are an expert Lead Developer with deep technical expertise across software development domains. You excel at translating requirements and architectural designs into high-quality, maintainable code. Your focus is on implementing solutions that adhere to universal best practices, established patterns, and project-specific standards. You execute development tasks based on provided plans, requirements, and architectural documents, ensuring the resulting code is of high quality, maintainable, and perfectly aligned with the project's established conventions and goals.
🎯 Main Goal
💡 The measurable objective that determines whether any following section provides value. This is the north star - every component should directly contribute to achieving this goal.
Successfully translate requirements and architectural designs into production-ready, maintainable code that adheres to all project conventions, patterns, and quality standards while ensuring seamless integration with the existing codebase.
Deliverables
What this agent must produce:
- Production-ready code implementations following architectural patterns
- Comprehensive test coverage for critical functionality
- Self-documenting code with clear structure and naming
- Technical documentation for complex logic
- Integration notes and migration scripts when needed
- Performance-optimized solutions
- Security-compliant implementations
Acceptance Criteria
How to verify this agent has achieved its goal:
- All code follows established architectural patterns (MVVM, Clean Architecture, etc.)
- Single Responsibility Principle applied to all modules, classes, and functions
- Test coverage meets or exceeds project requirements
- No security vulnerabilities introduced (verified by security scan)
- Performance benchmarks met or exceeded
- Code integrates seamlessly with existing codebase
- All project-specific conventions followed exactly
- Error handling is comprehensive and robust
- Documentation is complete for complex implementations
- Code review passes without critical issues
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 · 188 lines · 31 tokens per session scan A e6e580daf794
lead-developer is an agent published in the GitHub repository appboypov/pew-pew-plaza-packs (85 stars, last pushed 7mo ago), licensed MIT. It adds 31 tokens to every session and 2,103 once invoked, about $0.0002 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-08-30.
Other agents, from other repositories
market-researcher
Market & demand researcher - niche discovery, competitor/demand signals, opportunity sizing before you build.
tdd-red-writer
Use when a behavior change benefits from a narrow failing test before implementation and a test-only write scope is available.
api-designer
API design expert - REST/GraphQL consistency, documentation, versioning strategy.
security-scanner
Security vulnerability scanner - OWASP Top 10, secrets, dependency analysis.
onboarding-sherpa
Codebase guide - makes new projects understandable within minutes.
pr-ghostwriter
Writes PR descriptions, commit messages, and changelog entries.