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 naveedharri/benai-skills --skill marketing-os-setupgit clone --depth 1 https://github.com/naveedharri/benai-skillsWrote 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/naveedharri/benai-skills/marketing-os-setup)<a href="https://agentmods.dev/skills/naveedharri/benai-skills/marketing-os-setup"><img src="https://agentmods.dev/badge/skills/naveedharri/benai-skills/marketing-os-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/skills/naveedharri/benai-skills/marketing-os-setup"><img src="https://agentmods.dev/badge/skills/naveedharri/benai-skills/marketing-os-setup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 83 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
- medium Memory Poisoning · line 208 Skill injects content designed to persist in agent memory or context across interactions. Persistent injection can alter agent behavior long after the initial interaction.Fix: Do not allow untrusted input to persist in agent memory or context. Validate all content before storing and implement memory isolation between sessions.
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.00200 | $0.03956 |
| Opus 5 | $0.00100 | $0.01978 |
| Sonnet 5 | $0.00040 | $0.00791 |
| Haiku 4.5 | $0.00020 | $0.00396 |
Grade A, and why
marketing-os-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 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.
How it starts
The opening of the file, as written. The whole thing — 213 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Marketing OS Setup
Build the user a Marketing OS. Not a folder of templates, a working operating layer: the intelligence in Context/, the routines that keep it current, and a dashboard that answers "what do I do today."
State the problem once
Every skill that carries its own copy of the ICP, the offer and the voice means updating one leaves the rest stale. This OS makes Context/ authoritative so every skill inherits a change instead of drifting.
Say that in a sentence and move on. Do not pitch it further, and do not go looking for evidence: if the user wants their own duplication counted, they will ask.
The five pillars, in this order
Order matters. Do not skip ahead, and do not build the dashboard before there is data.
| Pillar | What happens | Reference |
|---|---|---|
| 1. Connectors | Probe what is actually authenticated. Never present a checklist | references/connectors.md |
| 2. Context | Interview and write the constitution. The highest-value step | references/interview.md, references/context-templates.md |
| 3. Structure | Scaffold seven knowledge folders plus Routines/, and every folder index |
references/structure.md, references/folder-indexes.md |
| 4. Routines | Offer to set them up | marketing-os-routines owns the templates and the scheduling |
| 5. Dashboard | Write the spec, then offer to build it | marketing-os-dashboard owns the build |
Read references/conventions.md before writing a single file. It carries the invariants, and breaking one means the result is not this OS.
Three rules that come before everything else
Stay inside the OS root
Read and write only inside the OS root the user gave you. Nothing else on the machine is in scope.
Do not list, glob, grep or read outside that root. Do not go looking for their other vaults, their skill folders, their home directory, or an example OS shipped with a plugin. Do not start an exploration nobody asked for. If you think something outside the root would help, name the one path you want and ask for it. Wait for a yes.
What ships with it
7 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 · 213 lines · 200 tokens per session scan A 896267e397ef
marketing-os-setup is a skill published in the GitHub repository naveedharri/benai-skills (61 stars, last pushed today), licensed MIT. It adds 200 tokens to every session and 3,956 once invoked, about $0.0010 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-09-05.
Other skills, from other repositories
career-portfolio
A portfolio-building skill for Korean job seekers that organizes projects and explains their work for development, design, marketing, and planning roles.
marketing-meta-ads-manager
A skill that manages Facebook and Instagram advertising through Meta’s official connector using natural-language instructions.
hr-operations
A skill for designing remote-work and team-operation policies. It covers flexible work, asynchronous communication, collaboration tools, productivity tracking, and employee experience.
collab-conflict
A guide for handling difficult workplace colleagues and recurring communication conflicts.
collab-feedback-loop
A guide for giving and receiving workplace feedback about specific actions and their effects.
collab-meeting
A meeting facilitation aid that helps define the purpose, plan the agenda, guide discussion, record decisions, and assign follow-up actions.