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 big-emotion/agent-atelier --skill content-strategistgit clone --depth 1 https://github.com/big-emotion/agent-atelierWrote 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/big-emotion/agent-atelier/content-strategist)<a href="https://agentmods.dev/skills/big-emotion/agent-atelier/content-strategist"><img src="https://agentmods.dev/badge/skills/big-emotion/agent-atelier/content-strategist/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/big-emotion/agent-atelier/content-strategist"><img src="https://agentmods.dev/badge/skills/big-emotion/agent-atelier/content-strategist.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.00137 | $0.01711 |
| Opus 5.5 | $0.00055 | $0.00684 |
| Sonnet 5.5 | $0.00027 | $0.00342 |
| Haiku 4.5 | $0.00014 | $0.00171 |
Grade A, and why
content-strategist 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 10d 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 — 151 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Content Strategist
Headings are fixed. Section headings are fixed identifiers: copy them exactly as written in the deliverable templates (English, with the same hash marks), whatever the language of the profile. Only the text under a heading is written in the profile's language.
Decides what to publish next, on which channel, how often, and for whom.
It is the consumer of the comms pipeline; its evidence comes from the dated
report written by /audience-audit.
Who this answers to
The operator is usually the decision-maker, not a social media specialist. Every output is a directive with its reason attached — publish this, there, this often, because this number says so. Never a menu of options with the choice handed back. Never platform jargon without the plain meaning beside it. When a decision is genuinely theirs, put one question with a recommendation, not an open field.
The rule that makes this skill worth invoking
Never propose a subject without stating how the comparable published content performed. If a subject, pillar or format has already shipped, its numbers come with the proposal or the proposal does not leave. If the numbers were never collected, say that rather than implying success.
What the project must supply
Three things, kept in the project's own reference files so the skill reasons from knowledge rather than pointing at folders:
- The channel doctrine — what each channel is for, which audience it reaches, what belongs there, how often, and which metric judges it.
- The plan already running — pillars, cadence, channel sequence, metric ranking, and every place measurement now contradicts it.
- The published state — what shipped where, what it measured, the caption register, the production method, and the decisions still open.
Read all three before answering anything. They are the difference between a plan and a guess.
Step 1 — Load the audience report
Read the most recent report. No report, or one older than 30 days → stop and
run /audience-audit first. Read its handoff section, the page verdicts and
the acquisition table.
What ships with it
1 file 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.
- 10d ago Changed · +19 lines a3b5662f657b
- 1mo ago First seen · 132 lines · 137 tokens per session scan A 4569a024a4e4
content-strategist is a skill published in the GitHub repository big-emotion/agent-atelier (3 stars, last pushed 2d ago), licensed MIT. It adds 137 tokens to every session and 1,711 once invoked, about $0.0005 per session on Opus 5.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-08.
Other skills, from other repositories
add-azuredevops
Adds Azure DevOps connector to a Power Apps code app. Use when querying work items, creating bugs, managing pipelines, or making ADO API calls.
pr-watch
Local PR watcher. Monitors CI status, automatically fixes failing checks by reading failure logs and applying targeted fixes, then optionally merges when all checks pass. Local CLI analog to Claude Code's cloud auto-fix feature.
ci-fixer
A CI job fails on a named revision and the fix belongs in code, config or tests, not in the CI provider.
push-ci
Push to remote and monitor CI. Validates branch safety, executes git push WITH explicit user approval, then monitors CI run status via gh CLI. Use when: user says 'push', 'push and watch CI', 'ship it', 'push-ci'. Not for: committing (use /smart-commit), creating PRs (use /create-pr), merging (use /merge-prep).
azure-devops
Manage Azure DevOps projects, work items, repos, PRs, pipelines, wikis, test plans, security alerts, variable groups, environments/approvals, branch policies, and attachments. Use when user asks to: manage sprints, create/update work items, list repos, create PRs, run pipelines, search code, manage wiki pages, check…
cloudflare-workers-ci-cd
Complete CI/CD guide for Cloudflare Workers using GitHub Actions and GitLab CI. Use for automated testing, deployment pipelines, preview environments, secrets management, or encountering deployment failures, workflow errors, environment configuration issues.