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 landim32/awesome-ai-skills --skill social-media-schedulinggit clone --depth 1 https://github.com/landim32/awesome-ai-skillsWrote 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/landim32/awesome-ai-skills/social-media-scheduling)<a href="https://agentmods.dev/skills/landim32/awesome-ai-skills/social-media-scheduling"><img src="https://agentmods.dev/badge/skills/landim32/awesome-ai-skills/social-media-scheduling/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/landim32/awesome-ai-skills/social-media-scheduling"><img src="https://agentmods.dev/badge/skills/landim32/awesome-ai-skills/social-media-scheduling.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.00064 | $0.01319 |
| Opus 5 | $0.00032 | $0.00660 |
| Sonnet 5 | $0.00013 | $0.00264 |
| Haiku 4.5 | $0.00006 | $0.00132 |
Grade A, and why
social-media-scheduling 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.
How it starts
The opening of the file, as written. The whole thing — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Social Media Scheduling
Owns the time/state layer of a campaign under social-media/: the post status
lifecycle, the per-network scheduling windows, and the synchronization between the
posts (single source of truth) and their derived views (cronograma.md /
agenda.md). It is platform mechanics only — the folder tree of a specific
campaign is defined by the domain pack (e.g. an album pack), but the status
semantics and the derived-view sync rules here apply to any campaign.
The literal status tokens and artifact section labels are kept verbatim (the generated files target a PT-BR audience). The documentation is in English.
Status lifecycle — 6 values
falta-conteudo → planejado → agendado → publicado (happy path)
+ cancelado (excluded by a rule)
+ aguardando (posts with no date yet)
falta-conteudo— the slot's date exists (slot reserved) but the post has no theme/material/caption defined yet. Frontmatter has the date and item, butTipo,Material,Legendaand post-specific hashtags are "a definir". Counts as ⚠️ FALTANTE non-blocking in cronograma/agenda.planejado— ready in this repo (Material, copy, hashtags) but not yet queued in the network's composer.agendado— the user has queued the post in the network's composer; the network will publish on the scheduled date.publicado— the post is live.cancelado— excluded by some rule.aguardando— ready but waiting for a trigger external to the calendar (post with no fixed date). See the domain pack that defines dateless posts.
Never publish. After the user reports what was published or changed, update
each post's Status and the derived views.
Per-network pre-schedule windows
Each network has its own rolling pre-queue limit. The calendar can plan posts far into the future, but the actual queuing inside each platform's composer happens in chunks as time progresses.
| Network | Pre-schedule window |
|---|---|
| Instagram (Meta Business Suite) | 29 days |
| Threads (mirrors Instagram) | 29 days (inherited) |
| TikTok | 30 days |
| X.com | no practical limit — accepts > 30 days, track the frontier |
| YouTube | no practical limit — accepts long windows, track the frontier |
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 · 102 lines · 64 tokens per session scan A d74883fd86e0
social-media-scheduling is a skill published in the GitHub repository landim32/awesome-ai-skills (1 stars, last pushed 2mo ago), licensed MIT. It adds 64 tokens to every session and 1,319 once invoked, about $0.0003 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
laravel-specialist
Build and configure Laravel 10+ applications, including creating Eloquent models and relationships, implementing Sanctum authentication, configuring Horizon queues, designing RESTful APIs with API resources, and building reactive interfaces with Livewire. Use when creating Laravel models, setting up queue workers…
cloud-architect
Designs cloud architectures, creates migration plans, generates cost optimization recommendations, and produces disaster recovery strategies across AWS, Azure, and GCP. Use when designing cloud architectures, planning migrations, or optimizing multi-cloud deployments. Invoke for Well-Architected Framework, cost…
devops-engineer
Creates Dockerfiles, configures CI/CD pipelines, writes Kubernetes manifests, and generates Terraform/Pulumi infrastructure templates. Handles deployment automation, GitOps configuration, incident response runbooks, and internal developer platform tooling. Use when setting up CI/CD pipelines, containerizing…
django-storages-s3
Use when configuring Django to store static and media files on AWS S3 with django-storages. Invoke when working with the STORAGES setting, S3 buckets, presigned URLs, CloudFront, or boto3-backed file storage in settings.py. Configures the Django 4.2+ STORAGES dict, public/private custom backends, presigned GET/POST…
fine-tuning-expert
Use when fine-tuning LLMs, training custom models, or adapting foundation models for specific tasks. Invoke for configuring LoRA/QLoRA adapters, preparing JSONL training datasets, setting hyperparameters for fine-tuning runs, adapter training, transfer learning, finetuning with Hugging Face PEFT, OpenAI fine-tuning…
kubernetes-specialist
Use when deploying or managing Kubernetes workloads. Invoke to create deployment manifests, configure pod security policies, set up service accounts, define network isolation rules, debug pod crashes, analyze resource limits, inspect container logs, or right-size workloads. Use for Helm charts, RBAC policies…