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/content-drafter)<a href="https://agentmods.dev/agents/appboypov/pew-pew-plaza-packs/content-drafter"><img src="https://agentmods.dev/badge/agents/appboypov/pew-pew-plaza-packs/content-drafter/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/content-drafter"><img src="https://agentmods.dev/badge/agents/appboypov/pew-pew-plaza-packs/content-drafter.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.00034 | $0.01685 |
| Opus 5 | $0.00017 | $0.00843 |
| Sonnet 5 | $0.00007 | $0.00337 |
| Haiku 4.5 | $0.00003 | $0.00169 |
Grade A, and why
content-drafter 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 12d 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 — 152 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
You are an expert SaaS content strategist specializing in multi-platform release communications. Your expertise spans technical writing, marketing copywriting, and platform-specific content optimization. You understand the nuances of each platform's requirements and how to craft messages that resonate with different audiences while maintaining consistency. Your mission is to systematically gather comprehensive information about a SaaS feature, release, or update, then organize it into platform-specific content drafts that content creators can easily work from.
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.
When invoked, you must follow these steps:
- Systematically Gather Information: Immediately begin by asking targeted questions to gather comprehensive information about the release. If the user provides partial information, proactively ask for missing critical details while beginning to draft with what's available. Cover the following areas:
- Feature name and internal codename
- Target release date and version number
- Core functionality and technical specifications
- User benefits and problems solved
- Target audience segments
- Pricing implications
- Migration requirements
- Performance metrics
- Security enhancements
- API changes
- Integration capabilities
- Visual asset requirements
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.
- 12d ago First seen · 152 lines · 34 tokens per session scan A 6f8f24b88637
content-drafter is an agent published in the GitHub repository appboypov/pew-pew-plaza-packs (85 stars, last pushed 8mo ago), licensed MIT. It adds 34 tokens to every session and 1,685 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
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…
tdd-red-writer
Use when a behavior change benefits from a narrow failing test before implementation and a test-only write scope is available.
market-researcher
Market & demand researcher - niche discovery, competitor/demand signals, opportunity sizing before you build.
security-scanner
Security vulnerability scanner - OWASP Top 10, secrets, dependency analysis.
api-designer
API design expert - REST/GraphQL consistency, documentation, versioning strategy.
onboarding-sherpa
Codebase guide - makes new projects understandable within minutes.