schedule

schedule is a command for Claude Code from revaya-ai/revaya-aios-workspace-template. It costs 0 tokens per session (1,142 once invoked), scanned A, original, MIT.

An interactive content-scheduling command that selects developed ideas, assigns dates, and manages a content calendar. It can also review the existing schedule.

In plain words
What is it for?
Use it to choose what to produce next, schedule filming and publication, and inspect currently scheduled content.
Why use it?
It turns prepared content ideas into dated production and publishing plans using the project's strategy and pipeline data.

Command for Claude Code

Written for Claude Code: $ARGUMENTS substitution.

Good fit Use it to choose what to produce next, schedule filming and publication, and inspect currently scheduled content.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/revaya-ai/revaya-aios-workspace-template/schedule
Install

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.

Clone the repo
git clone --depth 1 https://github.com/revaya-ai/revaya-aios-workspace-template

Made for: Claude Code.

Wrote 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.

agentmods badge for schedule

README.md
[![agentmods](https://agentmods.dev/badge/commands/revaya-ai/revaya-aios-workspace-template/schedule/github.svg)](https://agentmods.dev/commands/revaya-ai/revaya-aios-workspace-template/schedule)
Your own site
<a href="https://agentmods.dev/commands/revaya-ai/revaya-aios-workspace-template/schedule"><img src="https://agentmods.dev/badge/commands/revaya-ai/revaya-aios-workspace-template/schedule/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.

agentmods 80×15 button for schedule

Your own site · 80×15
<a href="https://agentmods.dev/commands/revaya-ai/revaya-aios-workspace-template/schedule"><img src="https://agentmods.dev/badge/commands/revaya-ai/revaya-aios-workspace-template/schedule.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,142 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.01142
Opus 5 $0.00000 $0.00571
Sonnet 5 $0.00000 $0.00228
Haiku 4.5 $0.00000 $0.00114

Measured 11d ago against content hash 10a430b7c53b, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

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 11d 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.

.claude/commands/schedule.md · 161 lines

How it starts

The opening of the file, as written. The whole thing — 161 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/schedule — Schedule Content

Interactive scheduling session — pick developed ideas, assign dates, and manage the content calendar.

Variables

$ARGUMENTS (optional: "review" to review existing schedule instead of scheduling new content)

Instructions

You are running a Scheduling Session for the Content Pipeline. Help you pick which developed ideas to create next, assign dates, and manage the calendar.

Setup — Load Current State

  1. Read the strategy:

    • content/strategy.md — platform cadence, format types
  2. Query the pipeline:

    .venv/bin/python3 -c "
    import sys, sqlite3; sys.path.insert(0, '.')
    from scripts.content.db import get_connection
    conn = get_connection()
    
    # Developed ideas ready to schedule
    developed = conn.execute(\"\"\"
        SELECT id, title, channel, format_type, priority_score,
               edit_turnaround_days, audience_segment, offer_alignment, created_at
        FROM content_ideas WHERE production_status = 'developed'
        ORDER BY COALESCE(priority_score, 0) DESC, created_at DESC
    \"\"\").fetchall()
    
    # Currently scheduled
    scheduled = conn.execute(\"\"\"
        SELECT id, title, channel, format_type, film_by_date,
               publish_date, production_status
        FROM content_ideas WHERE production_status IN ('scheduled', 'filmed', 'editing')
        ORDER BY publish_date ASC
    \"\"\").fetchall()
    
    print('=== DEVELOPED (ready to schedule) ===')
    for r in developed:
        p = f'P{r[\"priority_score\"]}' if r['priority_score'] else '—'
        print(f'  #{r[\"id\"]} [{r[\"channel\"] or \"?\"}] {r[\"title\"]} ({p})')
    
    print()
    print('=== CURRENTLY SCHEDULED ===')
    for r in scheduled:
        print(f'  #{r[\"id\"]} [{r[\"channel\"] or \"?\"}] {r[\"title\"]} — publish: {r[\"publish_date\"] or \"TBD\"} ({r[\"production_status\"]})')
    
    conn.close()
    "
    
  3. Read active campaigns (if relevant):

    • content/offers-and-funnels.md — active campaigns to align scheduling with

Read the full file on GitHub · 161 lines

Changes

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.

  1. 11d ago First seen · 161 lines · 0 tokens per session scan A 10a430b7c53b

Subscribe to this mod's changes

schedule is a command published in the GitHub repository revaya-ai/revaya-aios-workspace-template (2 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,142 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-31.