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.
git 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/commands/landim32/awesome-ai-skills/social-media-album-cycle)<a href="https://agentmods.dev/commands/landim32/awesome-ai-skills/social-media-album-cycle"><img src="https://agentmods.dev/badge/commands/landim32/awesome-ai-skills/social-media-album-cycle/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/commands/landim32/awesome-ai-skills/social-media-album-cycle"><img src="https://agentmods.dev/badge/commands/landim32/awesome-ai-skills/social-media-album-cycle.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.00042 | $0.02299 |
| Opus 5 | $0.00021 | $0.01149 |
| Sonnet 5 | $0.00008 | $0.00460 |
| Haiku 4.5 | $0.00004 | $0.00230 |
Grade A, and why
social-media-album-cycle 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 — 143 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/social-media-album-cycle — Stamp a track's fixed 28-post launch cycle
Stamps the fixed 28-post template of a track's launch cycle onto
social-media/albuns/<album-slug>/<NN-track-slug>/posts/. Each launch cycle has
exactly 28 days = 28 posts (daily cadence from 2026-07-05; launches every 4
weeks, always Saturday). 1 cycle = 1 folder <NN-slug>/posts/ (chronological
allocation rule from band-album-campaign): folder <NN> covers track N's warm-up
and its launch.
The 28-post template block and on-disk tokens (status values,
FALTANTE, the(faixa anterior)/(faixa atual)markers) are kept verbatim because the generated posts target a PT-BR audience and the template must be preserved exactly. The surrounding documentation is in English.
Input
$ARGUMENTS = <album-slug> <NN-track-slug> (e.g. genesis 03-homem-de-barro).
- Read the launch anchors from
albuns/<album-slug>/plano.md: F2=2026-07-04, F3=2026-08-01, F4=2026-08-29, F5=2026-09-26, F6=2026-10-24, F7=2026-11-21, F8=2026-12-19, F9=2027-01-16, F10=2027-02-13. - Determine track N (target) and track N-1 (previous).
Cycle semantics (slots 1..28)
Folder <NN>'s cycle starts on the day after track N-1's launch (slot 1) and
ends on track N's launch (slot 28 = track N's anchor date):
- "faixa atual" = track N (names the folder, launched on slot 28).
- "faixa anterior" = track N-1 (launched the day before slot 1).
- slot K = the K-th day of the cycle (slot 1 = day after the previous launch; slot 28 = track N's launch day).
Execution
For each slot 1..28, materialize the <network>.md files in
posts/<slot-date>/ per the template and the distribution notes below, delegating
post authoring to social-post-authoring and the domain post types to
band-music-reflection (reflection) and band-album-campaign. Sync
cronograma/agenda via social-media-scheduling.
THE FIXED TEMPLATE (28 slots) — verbatim, preserving (faixa anterior)/(faixa atual)
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 · 143 lines · 42 tokens per session scan A 3e63d38bc9e1
social-media-album-cycle is a command published in the GitHub repository landim32/awesome-ai-skills (1 stars, last pushed 2mo ago), licensed MIT. It adds 42 tokens to every session and 2,299 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 commands, from other repositories
skill-safety
Hostile audit of coding-agent configuration the project installed rather than wrote: skills, subagents, commands, plugins, hooks, and rule files obtained from a marketplace, a git URL, a gist, or a teammate. Assume every installed instruction file is attacker-authored until read, and that the attacker's goal is to be…
cr
Tool-driven implementation of unresolved PR/MR review comments on GitHub, GitLab or Bitbucket: fetch every comment thread plus the out-of-thread notices (review bodies, bot summaries), evaluate each for technical validity, implement valid ones one at a time with a full validation pass after each, and scan the codebase…
reliability
Hostile audit of behavior when a dependency fails, a call is retried, or a message is redelivered: assume every retry double-applies, every external call hangs forever, and every crash lands in the worst window — then prove where. A call that is idempotent, bounded, timed-out, and backed-off survives; anything else is…
_conventions
Read this file before executing any command file. Every rule here applies to every command unless the command file explicitly overrides it.
agent-rules
Audits the project's agent rule configuration end-to-end: validates every rule file, classifies every rule in the root instruction file as correctly placed or misplaced, and generates concrete new-rule suggestions from audit artifacts and project conventions. Assume every rule file has defects until proven otherwise.
cache
Hostile audit of caching correctness: assume every cache serves stale data after a write, shares a key across entities that must not share one, grows without bound, and stampedes on expiry — then prove where. A cache is a correctness liability until its key, its invalidation, its bound, and its expiry behavior are all…