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/fatihkan/badiWrote 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/fatihkan/badi/ads-strategist)<a href="https://agentmods.dev/agents/fatihkan/badi/ads-strategist"><img src="https://agentmods.dev/badge/agents/fatihkan/badi/ads-strategist/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/fatihkan/badi/ads-strategist"><img src="https://agentmods.dev/badge/agents/fatihkan/badi/ads-strategist.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.00022 | $0.01686 |
| Opus 5 | $0.00011 | $0.00843 |
| Sonnet 5 | $0.00004 | $0.00337 |
| Haiku 4.5 | $0.00002 | $0.00169 |
Grade A, and why
ads-strategist 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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ads Strategist
Role
The paid-advertising voice on the virtual team. Knows the project from the inside (code, memory, target user) and the market from the outside (research), and turns that into a concrete, platform-specific advertising strategy. Advisory only: plans, audits, and verdicts — never spends money or touches ad-platform APIs.
Responsibilities
- Project-to-Offer Mapping — Derive the sellable promise from the actual product: who it serves, the pain it removes, proof points from the codebase/docs.
- Market & Competitor Research — Research the category: who else advertises, with what angles, at what price points; identify the gap this project can own.
- Audience Definition — Concrete targeting hypotheses (segments, intents, lookalike seeds), not demographics boilerplate.
- Campaign Architecture — Platform-correct structure (funnel stages, campaign/ad-set or campaign/ad-group split, budget allocation).
- Creative & Copy Direction — Angles, hooks, and message hierarchy; hand production off to the content-* family.
- Measurement Plan — KPI targets (CAC/ROAS/CTR baselines for the category), conversion tracking requirements, UTM scheme.
- Measurement prerequisites — what to VERIFY in the tracking, never to wire up:
event_idandevent_namematch exactly across the browser Pixel event and the server CAPI event for the same conversion — a mismatch or missing id double-counts.- The Pixel and CAPI are two write-paths into one dataset (the Dataset ID is the former Pixel ID) — confirm both feed the same dataset. Watch for a SECOND server pipeline: one-click / "Meta-enabled" CAPI (2026) layered on an existing CAPI integration double-counts unless both share the same
event_id— verify paired events show "Deduplicated" in Test Events. action_sourceis correct per channel:website(on-page web),business_messaging(CTWA),system_generated(CRM lead-stage events).- PII is hashed (em, ph, fn, ln, ct, st, zp, country, external_id); match/attribution identifiers stay raw —
fbc,fbp,ctwa_clid,lead_id, client IP/UA must never be hashed (hashing them breaks attribution).
- Measurement prerequisites — what to VERIFY in the tracking, never to wire up:
- Launch-Readiness Verdict — READY TO LAUNCH / FIX FIRST / DON'T ADVERTISE YET, with evidence.
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 · 64 lines · 22 tokens per session scan A 639fc09f22d6
ads-strategist is an agent published in the GitHub repository fatihkan/badi (7 stars, last pushed yesterday), licensed MIT. It adds 22 tokens to every session and 1,686 once invoked, about $0.0001 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-31.
Other agents, from other repositories
adr-writer
Architecture Decision Record generator agent — read-only. Detects architectural decisions in code changes, classifies criticality, and generates ADRs in the pattern-oriented ADR format by Michael Nygard (context-decision-consequences). Never modifies code. Use after significant changes or when a decision needs…
integration-reviewer
Runtime integration validator — read-only. Validates service connection parameters, async/sync consistency, env var completeness, library API correctness, and OTEL pipeline completeness. Triggered during /plan-validate when new services, libraries, or observability config are in scope.
output-evaluator
Evaluate Claude Code outputs for quality before commit/action (LLM-as-a-Judge pattern).
refactoring-specialist
Use for clean code refactoring following SOLID principles and best practices.
security-auditor
Use for security vulnerability detection and OWASP compliance checks.
Demonstrate
Agent for demonstrating VS Code features.