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/amekala/ads-mcpWrote 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/commands/amekala/ads-mcp/refresh-brand-context)<a href="https://agentmods.dev/commands/amekala/ads-mcp/refresh-brand-context"><img src="https://agentmods.dev/badge/commands/amekala/ads-mcp/refresh-brand-context.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.1 | $0.00014 | $0.00171 |
| Opus 5 | $0.00007 | $0.00086 |
| Sonnet 5 | $0.00003 | $0.00034 |
| Haiku 4.5 | $0.00001 | $0.00017 |
Grade A, and why
refresh-brand-context 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 8d 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.
What it actually says
Re-scan all files in the project folder and pull fresh data from Adspirer MCP. Update CLAUDE.md with any changes.
- Scan folder for any new or updated brand docs (guidelines, media plans, audience profiles)
- Call
get_connections_statusto check current platform connections - Pull latest metrics:
get_campaign_performanceandget_meta_campaign_performanceare direct calls; other platforms go through their router ({"action": "execute", "tool_name": "..."}). Seeadspirer-mcp. - Call
get_business_profilefor any profile updates - Update CLAUDE.md with the refreshed data — merge new info, update performance numbers, note any changes
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.
- 8d ago First seen · 11 lines · 14 tokens per session scan A 4e12352faa1f
refresh-brand-context is a command published in the GitHub repository amekala/ads-mcp (89 stars, last pushed yesterday), licensed MIT. It adds 14 tokens to every session and 171 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-30.
Other commands, from other repositories
setup-context
Set up your Skill Memory — a pm-context.md every skill reads so outputs come back tailored to you.
brain
Set up or use your Professional Brain — init, ingest, recall, or review.
load
Load the shared Wingman context for this project.
purmemo
Run a purmemo workflow. These are memory-powered processes that automatically load your past context and guide you through structured tasks.
recall
Answer from reef memory, reading the pages before answering.
remember
Save something to your reef memory.