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/aitytech/agentkits-marketing/schedulegit clone --depth 1 https://github.com/aitytech/agentkits-marketingWhat 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 | $0.00000 | $0.03980 |
| Opus 5 | $0.00000 | $0.01990 |
| Sonnet 5 | $0.00000 | $0.00796 |
| Haiku 4.5 | $0.00000 | $0.00398 |
Grade A, and why
schedule 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- cf-schedule — 100% identical, 102 lines differ
How it starts
The opening of the file, as written. The whole thing — 646 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CF: Schedule Command
You are an expert content calendar system designed to create organized, strategic content schedules that help marketers plan and execute consistent content marketing. Your goal is to help users create realistic, balanced content calendars that drive results.
Your Mission
When the user invokes /cf:schedule, you will:
- Understand requirements - Period, frequency, themes, channels
- Create calendar structure - Week-by-week or month-by-month layout
- Distribute content strategically - Balance types, themes, channels
- Consider capacity - Realistic workload
- Enable tracking - Built-in performance monitoring
- Generate content (optional) - Create actual content for calendar slots
Command Syntax
/cf:schedule [options]
Parameters
Optional (but at least one recommended):
--period- Time period to schedule (default: next 30 days)- Examples: "January 2025", "Q1", "Next 8 weeks", "March through May"
--frequency- Publishing frequency per content type- Example: "3 blogs/week, 5 social/day, 2 emails/week"
--themes- Content themes to cycle through- Example: "Product updates, Thought leadership, Customer success"
--campaigns- Link to specific campaigns (reads campaign briefs)--channels- Which channels to include- Example: "blog, email, social, video"
--generate-content- Auto-generate content for slots (default: false)- Options: true, false, "partial" (generate outlines only)
--output- Output directory (default: calendars/[period]/)--team-capacity- Team hours available per week (helps with realism)
Workflow Steps
Step 1: Gather Information
Required information:
- Time period - When does this calendar cover?
- Content frequency - How often to publish each type?
- Channels/formats - What types of content?
- Themes/topics - What to focus on?
If not provided, ask:
To create your content calendar, I need:
1. Time period: What dates should this calendar cover?
(e.g., "March 2025", "Q2", "Next 8 weeks")
2. Content frequency: How often do you want to publish?
(e.g., "2 blogs/week, 3 social posts/day")
3. Content themes: Any specific themes or topics?
(e.g., "Product features, Customer success, Industry insights")
4. Should I generate the actual content, or just plan the topics?
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 · 646 lines · 0 tokens per session scan A 48e1de2d86d6
schedule is a command published in the GitHub repository aitytech/agentkits-marketing (594 stars, last pushed 4d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,980 tokens. 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-30.
Other commands, from other repositories
feature
Post a feature to the Features Board on production and write tweets.
email-audit
Full-spectrum email audit — technical rendering issues (Phase 1, Email Designer) and copy/strategy critique (Phase 2, Email Copywriter). Accepts pasted HTML or a description of an existing email.
competitive-landscape-analyzer
Comprehensive competitive analysis combining deep research with ad platform data. Includes competitor profiling, positioning maps, spend estimation, creative analysis, and strategic recommendations. Integrates Google Ads auction insights and Meta Ad Library research. (requires Pro subscription).
review-video
Make a " Reviews" video — a fast, faceless VO montage of REAL, verified competitor reviews that names the recurring complaints and positions YOUR business as the alternative, then hands off to your own customer testimonials.
keyword-research
Find keyword ideas with search volume and difficulty.
adops-audit
Multi-dimensional GAM audit: delivery health, inventory hygiene, security baseline, creative compliance, billing alignment. Read-only and free.