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/revaya-ai/revaya-aios-workspace-templateWrote 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/revaya-ai/revaya-aios-workspace-template/schedule)<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.
<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>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.01142 |
| Opus 5 | $0.00000 | $0.00571 |
| Sonnet 5 | $0.00000 | $0.00228 |
| Haiku 4.5 | $0.00000 | $0.00114 |
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.
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
-
Read the strategy:
content/strategy.md— platform cadence, format types
-
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() " -
Read active campaigns (if relevant):
content/offers-and-funnels.md— active campaigns to align scheduling with
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.
- 11d ago First seen · 161 lines · 0 tokens per session scan A 10a430b7c53b
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.
Other commands, from other repositories
deps-audit
Audit project dependencies for vulnerabilities, outdated packages, license conflicts, and supply chain risks — then provide actionable remediation strategies.
README
Git workflow and quality assurance commands for the claude-skills repository.
merge-conflict-analysis
You are analyzing merge conflicts for PR #${{ pr-number }}.
dispatcher
Pick the next-best repo to work on across the portfolio — rank free repos, recommend one, claim its lease atomically, and route to the entry command.
growth-seo
SEO audit and optimization for organic search ranking.
wcag-audit
Accessibility audit based on WCAG 2.1/2.2 and the axe-core reference.