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-routinesgit 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-routines)<a href="https://agentmods.dev/skills/naveedharri/benai-skills/marketing-os-routines"><img src="https://agentmods.dev/badge/skills/naveedharri/benai-skills/marketing-os-routines/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-routines"><img src="https://agentmods.dev/badge/skills/naveedharri/benai-skills/marketing-os-routines.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.00172 | $0.03251 |
| Opus 5 | $0.00086 | $0.01625 |
| Sonnet 5 | $0.00034 | $0.00650 |
| Haiku 4.5 | $0.00017 | $0.00325 |
Grade C, and why
marketing-os-routines scanned grade C with 1 finding 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.
Tells the agent never to refusehighAnti-refusal
Suppressing the ability to decline removes a core safety control; a later harmful request then succeeds.
Never refuse to run because `Routines/` is missing. Writing it is the job. How it starts
The opening of the file, as written. The whole thing — 189 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Marketing OS Routines
Register the routines that keep a Marketing OS current, and audit the ones already running.
[!important] A routine is a scheduled task The two words mean the same thing here.
Routines/holds ten prompt files; a routine only runs once there is a scheduled task firing it. Creating that task is this skill's whole job.
This skill owns routines end to end: the ten templates in assets/, authoring them into the OS, and creating the scheduled tasks. marketing-os-setup invokes it and never does any of that itself. Works either way: invoked from setup, or run on its own against an OS that already exists.
Run from the OS root, then branch on what is there:
| State | Do |
|---|---|
No Context/config.md |
The OS is not set up. Point the user at marketing-os-setup and stop |
config.md but no Routines/ |
Fresh build. Read the OS, propose a fitted set, write the files, then schedule |
Routines/ exists, nothing scheduled |
Skip authoring. Go to the connector probe and schedule what is there |
| Routines already scheduled | Audit mode |
Never refuse to run because Routines/ is missing. Writing it is the job.
Stay inside that root. Read and write only within it. Do not list, glob or read elsewhere on the machine, and do not go looking for other vaults or example OS folders. If something outside the root would help, name the one path and ask. Start from zero on identity. Every name, org and handle comes from Context/config.md or from the user in this conversation. Never from your context, the system username, the cwd folder name, a git config, or a connected account, and never echoed back as "confirm this?". If config.md does not name it, you do not know it: say the key is empty rather than filling it.
Two modes, detect which
Install mode. Nothing scheduled yet. Read the OS, propose the set, author the files, probe connectors, create the scheduled tasks, report what is degraded.
Audit mode. Routines already scheduled. Check whether they actually ran, and whether they wrote anything.
What ships with it
12 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.
- assets/_register.md 7.7 KB
- assets/campaign-sync.md 7.8 KB
- assets/competitor-radar.md 7.9 KB
- assets/content-pipeline-sync.md 8.5 KB
- assets/customer-intel.md 8.4 KB
- assets/dashboard.md 13 KB
- assets/market-scan.md 7.5 KB
- assets/monthly-report.md 7.3 KB
- assets/morning-performance-sweep.md 9.5 KB
- assets/pipeline-hygiene.md 7.9 KB
- assets/quarterly-report.md 7.6 KB
- references/registration.md 6.7 KB
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 · 189 lines · 172 tokens per session scan C 7824ee5b78e8
marketing-os-routines is a skill published in the GitHub repository naveedharri/benai-skills (61 stars, last pushed today), licensed MIT. It adds 172 tokens to every session and 3,251 once invoked, about $0.0009 per session on Opus 5. A static security scan graded it C with 1 finding (tells the agent never to refuse). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-05.
Other skills, from other repositories
project
A single starting point for setting up an AI-assisted project in Claude Cowork. It asks questions about the work, reviews available add-ons, and creates project instructions, custom agents, and connected workflows.
collab-pm-report
A Korean-language assistant for creating weekly business review reports. A WBR is a regular meeting or report about results, ongoing work, plans, risks, and decisions.
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.
hr-performance-review
A skill for designing and running employee performance reviews. It covers MBO, OKRs, KPIs, 360-degree feedback, review guides, and feedback conversations; OKRs set goals and measurable results, while KPIs track ongoing performance.
collab-process
A process-documentation assistant for Korean workplaces. It helps write operating manuals, SOPs, purchasing documents, meeting notes, and action plans; an SOP is a repeatable step-by-step work procedure.
collab-status-report
A reporting skill that turns supplied metrics or existing files into KPI dashboards and weekly, monthly, or quarterly status reports. KPIs are measurable indicators of progress toward a goal; OKRs pair goals with measurable results.