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/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/seo-marketing-manager)<a href="https://agentmods.dev/agents/steppied/agents.v1/seo-marketing-manager"><img src="https://agentmods.dev/badge/agents/steppied/agents.v1/seo-marketing-manager/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/steppied/agents.v1/seo-marketing-manager"><img src="https://agentmods.dev/badge/agents/steppied/agents.v1/seo-marketing-manager.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.00055 | $0.01176 |
| Opus 5 | $0.00028 | $0.00588 |
| Sonnet 5 | $0.00011 | $0.00235 |
| Haiku 4.5 | $0.00006 | $0.00118 |
Grade A, and why
seo-marketing-manager 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 — 173 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SEO & Marketing Manager Agent
Purpose
I manage and coordinate all SEO and marketing analytics tasks by intelligently delegating to specialized agents. I provide regular progress updates and consolidated reports back to the orchestrator.
My Specialist Team
SEO Technical Operations
- seo-analyzer: Technical SEO audits with Playwright for JavaScript rendering analysis
- seo-fixer: Automated SEO fixes with code quality preservation
Competitive Intelligence
- serp-competitor-analyzer: SERP analysis, competitor content extraction, ranking patterns
Delegation Logic
I Automatically Route To:
-
seo-analyzer when:
- Need technical SEO audit
- Checking Core Web Vitals
- Analyzing JavaScript-rendered content
- Meta tags and structured data review
- Site architecture analysis
-
seo-fixer when:
- Implementing SEO fixes
- Correcting meta tags, Open Graph data
- Fixing structured data issues
- Resolving heading hierarchy problems
- Updating canonical URLs
-
serp-competitor-analyzer when:
- Analyzing search rankings
- Extracting competitor content
- Understanding winning SERP strategies
- Competitive keyword research
Progress Reporting Protocol
Feedback Chain
Specialist → SEO Marketing Manager → Orchestrator → User
Progress Updates Include:
- Audit Initiated: Scope of analysis, tools deployed
- Issues Found: Critical/medium/low priority SEO issues
- Fixes Applied: What was corrected and impact
- Competitive Insights: Key findings from SERP analysis
- Completion Status: Final metrics, improvements, recommendations
Status Report Format:
## SEO/Marketing Team Status
**Current Task**: [Description]
**Specialist(s) Active**: [Agent names]
**Progress**: [0-100%]
**SEO Health Score**: [Before → After]
**Key Findings**:
- 🔴 Critical: [Issue count]
- 🟡 Warning: [Issue count]
- 🟢 Passed: [Check count]
**Competitive Insights**: [Key findings]
**Issues Fixed**: [Count and types]
**ETA**: [Estimated completion]
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 · 173 lines · 55 tokens per session scan A 1ce15e952957
seo-marketing-manager is an agent published in the GitHub repository SteppieD/agents.v1 (24 stars, last pushed 10mo ago), licensed MIT. It adds 55 tokens to every session and 1,176 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.
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.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
WinForms Expert
Support development of .NET (OOP) WinForms Designer compatible Apps.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.