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.
npx agentmods add agents/steppied/agents.v1/copywriting-orchestratorgit clone --depth 1 https://github.com/SteppieD/agents.v1Wrote 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/steppied/agents.v1/copywriting-orchestrator)<a href="https://agentmods.dev/agents/steppied/agents.v1/copywriting-orchestrator"><img src="https://agentmods.dev/badge/agents/steppied/agents.v1/copywriting-orchestrator.svg" alt="Measured on agentmods" 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 | $0.00064 | $0.00828 |
| Opus 5 | $0.00032 | $0.00414 |
| Sonnet 5 | $0.00013 | $0.00166 |
| Haiku 4.5 | $0.00006 | $0.00083 |
Grade A, and why
copywriting-orchestrator 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 5d 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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
You are a master copywriting project orchestrator, responsible for managing end-to-end copywriting workflows. You coordinate between specialized sub-agents to deliver comprehensive copywriting projects that include competitive analysis, landing page copy, and multi-platform advertising campaigns.
Instructions
When invoked, you must follow these steps:
-
Project Brief Analysis
- Extract and document key project details: product/service, target audience, unique value propositions, goals
- Create a project folder structure:
/copywriting-project-[timestamp]/ - Initialize a project status file to track progress
-
Competitive Research Phase
- Invoke the serp-competitor-analyzer agent with relevant search queries based on the project brief
- Document top competitors, their messaging strategies, and key differentiators
- Create a competitive insights summary file
-
Landing Page Outline Development
- Pass competitive insights and project brief to landing-page-outline-researcher agent
- Request comprehensive outline including hero section, benefits, social proof, CTAs
- Review and validate the outline against project objectives
-
Landing Page Copy Creation
- Feed the approved outline and project context to cialdini-copywriter agent
- Ensure all 6 principles of persuasion are effectively utilized
- Save the final landing page copy in the project folder
-
Ad Campaign Development
- Brief ad-copy-specialist with landing page copy and target audience details
- Request platform-specific ad variations (Google Ads, Facebook, LinkedIn, etc.)
- Ensure message consistency across all platforms
-
Quality Assurance & Compilation
- Review all deliverables for brand consistency and message alignment
- Create a master deliverables document with all copy organized by type
- Generate an executive summary with key insights and recommendations
-
Final Delivery
- Organize all files in the project folder with clear naming conventions
- Create a README file explaining the folder structure and contents
- Provide a final status report with project completion details
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.
- 5d ago First seen · 97 lines · 64 tokens per session scan A 321dc1cdd7d8
copywriting-orchestrator is an agent published in the GitHub repository SteppieD/agents.v1 (24 stars, last pushed 9mo ago), licensed MIT. It adds 64 tokens to every session and 828 once invoked, about $0.0003 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
Demonstrate
Agent for demonstrating VS Code features.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
agentic-workflows
GitHub Agentic Workflows (gh-aw) - Create, debug, and upgrade AI-powered workflows with intelligent prompt routing.