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 m3taz-ahmed/ai-globals --skill content-marketinggit clone --depth 1 https://github.com/m3taz-ahmed/ai-globalsWrote 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/m3taz-ahmed/ai-globals/content-marketing)<a href="https://agentmods.dev/skills/m3taz-ahmed/ai-globals/content-marketing"><img src="https://agentmods.dev/badge/skills/m3taz-ahmed/ai-globals/content-marketing/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/m3taz-ahmed/ai-globals/content-marketing"><img src="https://agentmods.dev/badge/skills/m3taz-ahmed/ai-globals/content-marketing.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.00030 | $0.00593 |
| Opus 5 | $0.00015 | $0.00296 |
| Sonnet 5 | $0.00006 | $0.00119 |
| Haiku 4.5 | $0.00003 | $0.00059 |
Grade A, and why
content-marketing 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 12d 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.
What it actually says
[SKILL] content-marketing [OBJ] Build a compounding content asset engine: define pillars, produce evergreen + timely pieces, repurpose across formats, and distribute through every channel.
[RULES]
- [REQ] Pillar model: 3-5 core topics (pillars) → cluster articles/videos → internal links back to pillar. One pillar per quarter minimum depth.
- [REQ] Editorial calendar: 4-week rolling plan with format (long/post/video/thread), channel, owner, status. Cross-link
social-media-marketingfor scheduling andemail-marketingfor nurture. - [CMD] Context7 IDs:
gitroomhq/postiz-app(distribution),knadh/listmonk(newsletter),plausible/analytics(performance). - [REQ] Repurpose rule: 1 pillar → 1 long-form → 4 social posts → 1 email → 2 short videos → 1 infographic. Maximize output per input.
- [REQ] Quality bar: every piece has a hook, a promise, evidence (data/case), and a CTA. Use
copy-frameworks(AIDA/PAS) for the CTA block. - [REQ] SEO alignment: cluster content follows
seo-lordbrief (keywords, outline, E-E-A-T, internal links). Never orphan a cluster piece. - [REQ] Free-first tools: Postiz for distribution, Listmonk (AGPL) for newsletter, Plausible for measurement. Notion/Sheets as calendar fallback.
- [REQ] Arabic/RTL: produce ar + en versions for each pillar when audience is bilingual; mirror calendar; RTL typesetting checked before publish (link
arabic-freelance). - [REQ] Performance loop: monthly review of top/bottom 3 pieces by engagement+conversion; double down on winners, retire losers.
- [REQ] Evergreen refresh: update pillar content quarterly; set "content decay" alert (≥25% traffic drop) per
seo-lordopportunities.
[PROHIBIT]
- No content published without a channel + CTA assigned.
- No plagiarism or undisclosed AI ghostwriting where disclosure required.
- No Arabic asset shipped with broken RTL.
- No calendar that ignores measurement feedback.
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.
- 12d ago First seen · 39 lines · 30 tokens per session scan A 4660f5814688
content-marketing is a skill published in the GitHub repository m3taz-ahmed/ai-globals (5 stars, last pushed yesterday), licensed MIT. It adds 30 tokens to every session and 593 once invoked, about $0.0002 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-08-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…