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 agentmods add skills/moizibnyousaf/marketing-cli/postiznpx skills add MoizIbnYousaf/marketing-cli --skill postizgit clone --depth 1 https://github.com/MoizIbnYousaf/marketing-cliWrote 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/moizibnyousaf/marketing-cli/postiz)<a href="https://agentmods.dev/skills/moizibnyousaf/marketing-cli/postiz"><img src="https://agentmods.dev/badge/skills/moizibnyousaf/marketing-cli/postiz.svg" alt="Measured on agentmods" 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.00159 | $0.04227 |
| Opus 5 | $0.00079 | $0.02114 |
| Sonnet 5 | $0.00032 | $0.00845 |
| Haiku 4.5 | $0.00016 | $0.00423 |
Grade A, and why
postiz 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 2d 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 — 249 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Postiz — Social Distribution Layer
You schedule pre-written social posts to LinkedIn, Reddit, Bluesky, Mastodon, Threads, Instagram, TikTok, YouTube, Pinterest, Discord, Slack, and any other provider a running postiz instance supports. You do NOT write copy. You do NOT tailor per platform. Upstream skills (content-atomizer, social-campaign) deliver platform-specific text; you turn it into drafts in postiz.
For Twitter/X threads, defer to typefully — its thread UX is canonical. You handle everything else.
North Star
Postiz is a distribution execution layer in the mktg playbook:
- You never generate or rewrite copy.
- You never choose the platform mix — that's the user's ask or social-campaign's plan.
- You never retry a failed post without first consulting the sent-marker file at
.mktg/publish/{campaign}-postiz.json— postiz has no idempotency key, and retries duplicate. - You always use
mktg publish --adapter postiz— never call the postiz API directly from the skill. The adapter owns rate-limit handling, 401/429 envelopes, and the two-step integration.id resolution.
On Activation
Run these 4 steps before anything else. Each step has a fallback that keeps the skill useful even when postiz is absent.
Step 1 — Verify the catalog is registered and configured
mktg catalog info postiz --json --fields configured,missing_envs,auth.credential_envs,resolved_base
catalog info <name> returns the full CatalogEntry plus computed configured/missing_envs/resolved_base fields. The command errors with exit code 1 (NOT_FOUND) if the catalog is not in catalogs-manifest.json — that's the "not registered" signal.
- Exit code 1 → postiz catalog is not registered. Tell the user:
mktg catalog add postiz --confirm. Stop. configured: false→ env vars are missing. Build the fix string frommissing_envsrather than hardcoding. Canonical expectation:POSTIZ_API_KEY(required) andPOSTIZ_API_BASE(defaults tohttps://api.postiz.comif unset; the catalog loader returnsresolved_base: nullin that case and the skill applies the default). Stop.configured: true→ proceed to Step 2.
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.
- 2d ago First seen · 249 lines · 159 tokens per session scan A 5c5d7c0da73d
postiz is a skill published in the GitHub repository MoizIbnYousaf/marketing-cli (31 stars, last pushed 19d ago), licensed MIT. It adds 159 tokens to every session and 4,227 once invoked, about $0.0008 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
linkedin-reply-handler
Draft a reply to a specific existing LinkedIn comment from its URL. Use when the user wants to reply to a comment on any post, or follow up after an author replied to them. Parses the commentUrn, resolves the correct parentComment target (LinkedIn flattens threads to 2 levels), and posts via Publora on approval. Not…
linkedin-comment-drafter
Draft a LinkedIn comment on someone else's post from its URL, or reshare (repost) it to your feed with optional commentary. Use when the user pastes a post URL and asks to comment, engage, be first commenter, or repost with their thoughts. Produces 1-3 variants in the user's voice, picks a reaction, and publishes via…
linkedin-employee-advocacy
Stand up and run a LinkedIn employee advocacy program for a marketing or sales team. Covers 14-day launch playbook, brand-guideline governance, per-post time budget, cadence benchmarks, and team ROI (reach, engagement, pipeline). Triggers on "employee advocacy", "get the team posting", "scale LinkedIn across team"…
ads-landing
Audit paid-ad landing pages for message match, mobile experience, performance, accessibility, trust, forms, consent, tracking, security, and conversion friction. Use for landing-page audit, post-click experience, LP audit, conversion-rate optimization, form optimization, ad-to-page message match, redirects, blocked…
ads-research
Refresh Claude Ads platform, API, policy, regulation, benchmark, issue, pull-request, fork, and repository evidence. Use for ads research refresh, expired refreshdue dates, stale API or platform claims, reverify-or-demote decisions, release-current claim validation, ecosystem review, current platform changes, or…
ads-amazon
Audit Amazon Ads profiles, regions, Sponsored Products, Sponsored Brands, Sponsored Display, DSP, portfolios, targeting, search terms, retail readiness, creative, budgets, ACOS, TACOS, reporting, and policy. Use for Amazon Ads, sponsored ads, Amazon PPC, ACOS, TACOS, ASIN advertising, Amazon DSP, or retail-media…