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 azeemkafridi/bulkpublish-api --skill social-media-calendargit clone --depth 1 https://github.com/azeemkafridi/bulkpublish-apiWrote 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/azeemkafridi/bulkpublish-api/social-media-calendar)<a href="https://agentmods.dev/skills/azeemkafridi/bulkpublish-api/social-media-calendar"><img src="https://agentmods.dev/badge/skills/azeemkafridi/bulkpublish-api/social-media-calendar/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/azeemkafridi/bulkpublish-api/social-media-calendar"><img src="https://agentmods.dev/badge/skills/azeemkafridi/bulkpublish-api/social-media-calendar.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.00035 | $0.00228 |
| Opus 5 | $0.00017 | $0.00114 |
| Sonnet 5 | $0.00007 | $0.00046 |
| Haiku 4.5 | $0.00003 | $0.00023 |
Grade A, and why
social-media-calendar 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.
What it actually says
Social Media Calendar
Create a calendar that is realistic for the audience, campaign, connected channels, and BulkPublish limits.
Workflow
- Establish the date range, timezone, cadence, campaign constraints, target platforms, and approval requirements.
- Spread topics and formats across the calendar to avoid repetition and platform over-posting.
- Use
get_queue_slotwhen the user wants the next optimal available slot; do not claim an optimal time without checking it. - Check channels and quota before creating a large schedule.
- Use ISO 8601 timestamps and the user's stated timezone.
- Create drafts unless the user explicitly asks to schedule or publish. When approval is requested, set
requestApproval: trueand report the returned approval state.
Before execution, validate each post with platform-reference and media-preflight. Summarize the resulting calendar with post IDs, status, times, timezone, and any posts awaiting approval.
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 · 20 lines · 35 tokens per session scan A 5c28986724b1
social-media-calendar is a skill published in the GitHub repository azeemkafridi/bulkpublish-api (1 stars, last pushed yesterday), licensed MIT. It adds 35 tokens to every session and 228 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-09-04.
Other skills, from other repositories
explore-api
Explore an OpenAPI spec's structure using parse and walk tools.
diff-specs
Compare two OpenAPI spec versions, highlight breaking changes, and suggest migration steps.
fix-spec
Auto-fix common OpenAPI spec issues with a preview-first workflow.
validate-spec
Validate an OpenAPI spec, explain errors clearly, and suggest or apply fixes.
generate-code
Generate Go client, server, or type code from an OpenAPI spec.
kui-framework
Guide for building web applications with the Kui framework. Use when writing Kui ASGI/WSGI handlers, defining routes, binding parameters, configuring OpenAPI docs, or working with middleware/dependency injection.