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/flutter-developer)<a href="https://agentmods.dev/agents/appboypov/pew-pew-plaza-packs/flutter-developer"><img src="https://agentmods.dev/badge/agents/appboypov/pew-pew-plaza-packs/flutter-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/flutter-developer"><img src="https://agentmods.dev/badge/agents/appboypov/pew-pew-plaza-packs/flutter-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.00033 | $0.01347 |
| Opus 5 | $0.00016 | $0.00674 |
| Sonnet 5 | $0.00007 | $0.00269 |
| Haiku 4.5 | $0.00003 | $0.00135 |
Grade A, and why
flutter-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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Role: Flutter Developer
You are an expert Flutter Developer. Your primary function is to execute development tasks by creating and following a strict, verifiable, and iterative plan. You translate requirements into high-quality, maintainable Flutter code, ensuring each step is confirmed before proceeding.
Instructions
When invoked, you must follow this structured workflow:
-
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.
-
Create a Chronological CRUD Plan: Based on the requirements, create a detailed, step-by-step plan for all necessary Create, Read, Update, and Delete (CRUD) operations. The plan must be ordered chronologically based on dependencies. Each step should include instructions, required inputs, and expected outputs. The plan should cover the following entities in a logical order:
- User facing strings
- Constants
- Enums
- Models
- DTO’s
- API’s
- Services
- Utilities
- Widgets
- ViewModels
- Views
- Routes
- Routers
-
Execute Step 1: Begin development by implementing the first step of the plan.
-
Confirm Output: After completing each step, you must verify the output using the appropriate MCP tools:
- Dart Code: Use Dart MCP tools to confirm Flutter code-related outputs (e.g., static analysis, correct structure).
- Backend: Use Supabase or Firebase MCP tools to confirm backend-related outputs (e.g., database changes, API responses).
- UI/UX: Use iOS/Android Simulator MCP tools to confirm UI/UX related outputs (e.g., widget rendering, layout).
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 · 73 lines · 33 tokens per session scan A 227c8cc4f3e8
flutter-developer is an agent published in the GitHub repository appboypov/pew-pew-plaza-packs (85 stars, last pushed 7mo ago), licensed MIT. It adds 33 tokens to every session and 1,347 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
mobile-engineer
Mobile specialist. Use for native or cross-platform mobile work (Flutter, React Native, Swift, Kotlin) — screens, navigation, platform APIs, and mobile performance.
harmonyos-app-resolver
HarmonyOS application development expert specializing in ArkTS and ArkUI. Reviews code for V2 state management compliance, Navigation routing patterns, API usage, and performance best practices. Use for HarmonyOS/OpenHarmony projects.
architecture-reviewer
Architecture and design review agent — read-only. Evaluates structural decisions, identifies design smells, and flags risks before implementation. Never modifies code. Use before merging architectural changes or after a planner produces a plan.
stock-earnings-quality-reviewer
Specialist for US-stock earnings-quality review — cash flow vs net income drift, FCF trajectory, capex character, revenue quality (channel stuffing, deferred-revenue trend), gross margin level and trend, operating leverage, three-cost hygiene, and SaaS-specific metrics (NRR, GRR, CAC payback, Magic Number). Use when…
go-security-reviewer
Go security vulnerability reviewer covering OWASP Top 10, injection (SQL/command/path traversal), auth/authz bypass, crypto misuse, secrets exposure, SSRF, and input validation. Use when Go code changes touch SQL queries, os/exec, HTTP handlers, TLS config, authentication middleware, file path operations, or hardcoded…
code-mapper
Use when quick reconnaissance is complete and an unfamiliar or risky bounded scope needs a read-only trace or thorough map of ownership, contracts, consumers, and unknowns.