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 gtmagents/gtm-agents --skill editorial-opsgit clone --depth 1 https://github.com/gtmagents/gtm-agentsWrote 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/gtmagents/gtm-agents/editorial-ops)<a href="https://agentmods.dev/skills/gtmagents/gtm-agents/editorial-ops"><img src="https://agentmods.dev/badge/skills/gtmagents/gtm-agents/editorial-ops/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/gtmagents/gtm-agents/editorial-ops"><img src="https://agentmods.dev/badge/skills/gtmagents/gtm-agents/editorial-ops.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.00027 | $0.00679 |
| Opus 5 | $0.00014 | $0.00340 |
| Sonnet 5 | $0.00005 | $0.00136 |
| Haiku 4.5 | $0.00003 | $0.00068 |
Grade A, and why
editorial-ops 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 8d 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 — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Editorial Operations Skill
When to Use
- Building or refreshing quarterly editorial roadmaps tied to GTM objectives.
- Translating thought-leadership pillars into weekly blog, newsletter, and social programming.
- Auditing production capacity, approvals, and distribution SLAs to eliminate bottlenecks.
Framework
- North Star & Themes – lock the executive thesis and supporting pillars (see GTM Agents Marketing Director guidance @puerto/README.md#183-212).
- Cadence Grid – map channels (blog, podcast, webinar, newsletter, LinkedIn) vs. frequency, owner, and CTA.
- Production Swimlanes – ideation → outline → draft → edit → design → approvals → launch.
- Distribution Tree – primary asset → derivative snippets → paid boosts → lifecycle inserts.
- Measurement Layer – define KPI guardrails (reach, engagement, SQL influence, pipeline velocity) before content leaves drafting.
Workflow Checklist
- Weekly Editorial Stand-up (30 min): review status board, unblock owners, confirm launches.
- Content Readiness Criteria: complete brief, stakeholder quotes, sources cited, SEO target, CTA alignment.
- Approval Paths: highlight who signs off (Content Strategist, Brand, Legal) and expected turnaround.
- Escalation Matrix: Marketing Director + Project Manager contacts for scope or timeline changes.
Templates
- Editorial Calendar: See
assets/editorial_calendar_template.mdfor tracking content. - Distribution Brief: See
assets/distribution_brief.mdfor launch checklists. - Post-Launch Debrief template capturing performance vs. guardrails, learnings, and follow-up actions.
- Ops Dashboard view showing backlog aging, production velocity, and publication mix.
Tips
- Treat every flagship asset like a mini campaign: pair the lifecycle-mapping blueprint (Plan → Build → QA → Launch → Inspect) with editorial checkpoints.
- Partner with Marketing Analytics to instrument dashboards early; no asset ships without a measurement plan.
- Keep a "Parking Lot" section for emergent ideas so high-priority launches retain focus.
- Borrow GTM Agents's status packet format (see lifecycle-mapping skill) for weekly exec updates.
What ships with it
2 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.
- 8d ago First seen · 53 lines · 27 tokens per session scan A 5a3aa1597bfb
editorial-ops is a skill published in the GitHub repository gtmagents/gtm-agents (399 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 27 tokens to every session and 679 once invoked, about $0.0001 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-03.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
magpie-security-issue-import-from-md
Open one or more tracking issues from a markdown file containing a batch of security findings. Each finding becomes one tracker landing in the Needs triage board column. The file itself is the full report — there is no inbound reporter to reply to and no PR to inspect.
remove
Remove a deployed framework or addon from the current workspace.