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 skills add iamwaqargulzar/Marketing-Agent-OS --skill participation-warmup-plannergit clone --depth 1 https://github.com/iamwaqargulzar/Marketing-Agent-OSWrote 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/skills/iamwaqargulzar/marketing-agent-os/participation-warmup-planner)<a href="https://agentmods.dev/skills/iamwaqargulzar/marketing-agent-os/participation-warmup-planner"><img src="https://agentmods.dev/badge/skills/iamwaqargulzar/marketing-agent-os/participation-warmup-planner/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/skills/iamwaqargulzar/marketing-agent-os/participation-warmup-planner"><img src="https://agentmods.dev/badge/skills/iamwaqargulzar/marketing-agent-os/participation-warmup-planner.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.00167 | $0.00869 |
| Opus 5 | $0.00084 | $0.00434 |
| Sonnet 5 | $0.00033 | $0.00174 |
| Haiku 4.5 | $0.00017 | $0.00087 |
Grade A, and why
participation-warmup-planner 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 7d 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.
This is a copy
61% identical to impeccable — 317 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Participation Warmup Planner
Quick Start
Use this skill for participation warmup planner. Start from the user’s concrete objective and available evidence; do not substitute generic marketing advice for task-specific analysis.
Skill Contract
- Reads: user-provided context; relevant project files;
.agents/product-marketing.mdwhen present; approved public or connected data sources. - Writes: recommendations and artifacts in the response by default. Persistent file/account changes require explicit request or authorization.
- Evidence: label consequential claims as
measured,user-provided,calculated,estimated, orproxy. Never upgrade uncertainty silently. - Side effects: do not publish, send, spend, delete, mutate accounts, or persist registry truth without user authorization.
- Freshness: verify current platform rules, search eligibility, ad policies, model/tool capabilities, laws, pricing, and other time-sensitive claims before acting.
Instructions
- Define the exact
participation warmup plannerobjective, audience/scope, constraints and success metric before recommending action. - Load shared product-marketing context when it materially changes the answer; ask only for missing facts that block a decision.
- Collect the minimum evidence needed for participation warmup planner. Distinguish direct observations from assumptions and proxies.
- Execute the participation warmup planner analysis or artifact using the domain checklist below; prefer specific outputs over generic best-practice lists.
- Prioritize actions by impact, confidence, effort and dependency. Identify what would falsify important assumptions.
- For external side effects, publishing, sending, spend changes, account changes or persistent writes, obtain authorization first.
- Finish with decision-ready output, evidence labels, open loops, and no more than three next-best skills.
Domain Checklist
- Channel role
- Audience behavior
- Native format norms
- Content/participation mix
- Community response rules
- Distribution loop
- Measurement
- Brand/safety escalation
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 7d ago First seen · 75 lines · 167 tokens per session scan A 865946a38967
participation-warmup-planner is a skill published in the GitHub repository iamwaqargulzar/Marketing-Agent-OS (5 stars, last pushed 8d ago), licensed Apache-2.0. It adds 167 tokens to every session and 869 once invoked, about $0.0008 per session on Opus 5. A static security scan graded it A with 0 findings. It is 61% identical to impeccable, differing in 317 lines, and is treated as a copy.
Other skills, from other repositories
hoo-task-board
Use to view or mirror the work queue - "task board", "show the queue", /organic-os:task-board. Mirrors to Notion when that connector exists; local queue.md is the source of truth.
reset
Use when the user wants to remove a site from organic-os, deregister a site, uninstall, "reset organic-os", "remove my site", "start over", or runs /organic-os:reset. Guided teardown that shows what exists and, per user choice, deregisters the site from the local registry - it never deletes the brain repo or revokes…
import-sop
Import agency Standard Operating Procedures — approval workflows, campaign launch checklists, escalation procedures, QA steps — and structure them into numbered, role-assigned steps with human-approval gates marked. SOPs save at the agency level so they apply across every client brand, not per-brand. Triggers on…
client-onboarding
Generate a complete onboarding package for a new marketing client — kickoff meeting agenda, 20-30 question discovery questionnaire, stakeholder map with RACI matrix, platform-by-platform access checklist, 30-60-90 day milestone plan, communication cadence, escalation protocol, welcome email template, internal team…
ansvisor-aeo-coach-standalone
Standalone (no-MCP) version of the Ansvisor AEO Coach. Use this only when the user's Claude client cannot connect to the Ansvisor MCP server (e.g. claude.ai web without a Connector configured). Fetches live data from the Ansvisor REST API directly with the user's API key via code execution. For clients that support…
seo-vertical-detect
Classify a website as ecommerce, local-business, blog-publisher, saas, docs, or generic (multiple may apply), and report detected locales, from the persisted PageSnapshot plus the platform detector's vertical hints. Used by seo-orchestrator to decide which conditional modules to run and how to reweight the scores.