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/EditorialOS/pinterest-marketing-strategistWrote 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/editorialos/pinterest-marketing-strategist/setup)<a href="https://agentmods.dev/commands/editorialos/pinterest-marketing-strategist/setup"><img src="https://agentmods.dev/badge/commands/editorialos/pinterest-marketing-strategist/setup/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/commands/editorialos/pinterest-marketing-strategist/setup"><img src="https://agentmods.dev/badge/commands/editorialos/pinterest-marketing-strategist/setup.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.00033 | $0.01089 |
| Opus 5 | $0.00016 | $0.00544 |
| Sonnet 5 | $0.00007 | $0.00218 |
| Haiku 4.5 | $0.00003 | $0.00109 |
Grade A, and why
setup 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 — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/setup
Configure once. Every /create and /track reads this.
Trigger
Run when starting fresh, adding a new brand, changing boards, updating the image library location, or shifting Pinterest goals. Safe to re-run — updates existing config without losing history.
What Setup Captures
1 — Brand Identity
- Brand name — as it should appear in pin descriptions
- What you sell or promote — products, services, content, SaaS, destinations
- Brand voice — adjectives, vocabulary rules, tone. If a brand guide exists in ~~docs, extract from there.
- Visual style — clean/bold/editorial/minimal/colorful. Informs image selection and text overlay choices.
- Off-limits — words, tones, or visual styles to avoid ("never say 'hustle'", "no stock photo aesthetic")
2 — Target Audience
- Who finds you on Pinterest — demographics, interests, planning behavior
- What they search for — actual Pinterest search terms your audience uses
- Planning stage — are they dreaming (saves), deciding (clicks), or buying (conversions)?
- Device — 85% of Pinterest is mobile. All pin sizing assumes mobile-first.
3 — Board Structure
For each board:
- Board name — descriptive, keyword-rich (Pinterest indexes board names)
- Board theme — what content belongs here
- Board goal — traffic, saves, awareness, or sales
- Board description — 2-3 sentences with keywords (for Pinterest SEO)
Minimum recommended: 4 boards. Maximum recommended: 10 for active management.
4 — Image Library
This is the critical setup step that makes composed pins possible.
Option A — Cloudinary (recommended) If ~~images is connected, provide:
- Cloudinary folder path containing approved brand images
- Any tag conventions used ("product", "lifestyle", "headshot", "seasonal")
- Whether text overlay is permitted on images
Option B — Google Drive If images live in ~~docs:
- Folder path within Drive (e.g.,
images/orbrand-assets/pinterest/) - Any subfolder conventions (e.g.,
images/products/,images/lifestyle/)
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 · 114 lines · 0 tokens per session scan A ff8bb86cf8bf
setup is a command published in the GitHub repository EditorialOS/pinterest-marketing-strategist (2 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 33 tokens to every session and 1,089 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-31.
Other commands, from other repositories
save
Save current work state for next session. Creates/updates .planning/ files (CHECKPOINT.md, STATE.md, settings.json) so Heimdall resumes with full context. NOT a rewind — saves forward progress. Run before closing a session or at any milestone.
maintain
Run automated maintenance — seeker finds bugs from pod logs and raises GitHub issues, fixer picks them up and creates PRs. Can run as a one-shot or scheduled via /schedule.
autonomy
Set Heimdall autonomy (1=Guided, 2=Checkpoint, 3=Full Auto) — how much the agent does before asking. Use with a number, +/- to cycle, or no argument to show current.
level
Deprecated alias for /hmd:autonomy. Sets Heimdall autonomy (1=Guided, 2=Checkpoint, 3=Full Auto). Still works; prints a one-line rename notice.
status
Show current Heimdall state — project phase, active agents, quality gates, conflicts.
dashboard
Build a shareable HTML dashboard of your hunt — funnel, status, categories, recruiter scores — from the tracker.