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 commands/seite-sh/seite/content-calendargit clone --depth 1 https://github.com/seite-sh/seiteWrote 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/seite-sh/seite/content-calendar)<a href="https://agentmods.dev/commands/seite-sh/seite/content-calendar"><img src="https://agentmods.dev/badge/commands/seite-sh/seite/content-calendar.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.00000 | $0.02533 |
| Opus 5 | $0.00000 | $0.01267 |
| Sonnet 5 | $0.00000 | $0.00507 |
| Haiku 4.5 | $0.00000 | $0.00253 |
Grade A, and why
content-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 5d 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.
This is a copy
100% identical to content-calendar — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 302 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Content Calendar Command
Generate a dated, month-long content calendar mapped to topic clusters, keywords, and publishing cadence using existing research data.
Usage
/content-calendar - Generate calendar for current month (2 posts/week)
/content-calendar [posts-per-week] - Custom cadence (e.g., /content-calendar 3)
/content-calendar [posts-per-week] [month] - Custom cadence and month (e.g., /content-calendar 3 next-month)
/content-calendar [posts-per-week] [month] [focus-cluster] - Filter to a specific cluster (e.g., /content-calendar 2 april "content marketing")
What This Command Does
Bridges the gap between /priorities (what to work on) and execution (when to publish). Produces a dated publishing schedule with:
- Specific publish dates assigned to each piece
- Content categorized by type (quick win, rewrite, new article, trending)
- Week-by-week strategy (quick wins first, cluster building later)
- Exact commands to run for each piece
- Parking lot for next month's opportunities
Parameters
| Parameter | Default | Description |
|---|---|---|
| Posts per week | 2 | Number of pieces to publish each week |
| Month | Current month | Target month name or "next-month" |
| Focus cluster | None | Optional topic cluster filter |
Process
1. Parse Parameters
Extract from user input:
- Posts per week: Number (default: 2). Calculate total pieces = posts_per_week × weeks in target month.
- Target month: Parse month name (e.g., "april", "next-month", "june"). Default to current month. Determine the year, first day, last day, and number of weeks.
- Focus cluster: Optional text filter. If provided, prioritize items matching this cluster.
2. Run Research Scripts
Check if today's reports already exist before running each script. Skip any script whose report for today is already in research/.
python3 research_quick_wins.py
Generates research/quick-wins-YYYY-MM-DD.md
python3 research_topic_clusters.py
Generates research/topic-clusters-YYYY-MM-DD.md
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.
- 5d ago First seen · 302 lines · 0 tokens per session scan A 62e1a487b450
content-calendar is a command published in the GitHub repository seite-sh/seite (20 stars, last pushed 21d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,533 tokens. A static security scan graded it A with 0 findings. It is 100% identical to content-calendar, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
awesome-chatgpt
Search awesome-ChatGPT-repositories for open-source GitHub repositories related to ChatGPT and LLMs.
init
Scaffold a new MindBase project (v2 layout). Usage: /mb:init [template] [-- mission ...].
commit
智能生成 Git 提交信息并提交.
pr
Handle the full workflow from current branch state to an open, CI-monitored pull request.
doctor.es
Diagnostica problemas de inferencia LLM en Mac: asiai doctor verifica el estado de los motores, conflictos de puertos, carga de modelos y estado de la GPU.
claude-request
Send a prompt to Claude Code via the LLM gateway with session tracking.