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/agamjn/rising/reddit-schedulegit clone --depth 1 https://github.com/agamjn/risingWrote 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/agamjn/rising/reddit-schedule)<a href="https://agentmods.dev/commands/agamjn/rising/reddit-schedule"><img src="https://agentmods.dev/badge/commands/agamjn/rising/reddit-schedule.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 | $0.00027 | $0.00417 |
| Opus 5 | $0.00014 | $0.00209 |
| Sonnet 5 | $0.00005 | $0.00083 |
| Haiku 4.5 | $0.00003 | $0.00042 |
Grade A, and why
reddit-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 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.
What it actually says
You register /reddit-daily as a scheduled task using Claude Code's built-in scheduling.
Pre-flight check
- Read
$ARGUMENTS. If empty, ask: "When should /reddit-daily run? (e.g., 'weekdays at 9am', 'every day at 7am', 'monday wednesday friday at noon')" - Verify CWD is set up (has
product.md, etc.) — same check as/reddit-daily. If not, refuse and tell the user to run/reddit-setupfirst.
Procedure
-
Get the absolute CWD:
pwd. -
Use the
scheduleskill (ormcp__scheduled-tasks__create_scheduled_taskdirectly if available) to register a task with:- Schedule: parsed from the user's natural-language input
- Working directory: the CWD captured above (so the daily run uses the right product folder)
- Prompt:
/reddit-daily - Name/label:
rising: <product folder name> daily
-
Confirm to the user:
Scheduled.
Product folder: <CWD>
Cadence: <human-readable cadence>
Next run: <when>
Use /reddit-schedule <new-cadence> to change it, or your scheduled-tasks UI to remove it.
Quality bar
- The schedule must include the working directory — without it, the scheduled run won't know which product folder to operate in.
- If multiple folders are set up, each should have its own scheduled task. Don't try to multiplex.
- If the user re-runs this command in the same folder, replace the existing scheduled task rather than creating a duplicate.
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 · 38 lines · 27 tokens per session scan A c4b7ef581a64
reddit-schedule is a command published in the GitHub repository agamjn/rising (17 stars, last pushed 3mo ago), licensed MIT. It adds 27 tokens to every session and 417 once invoked, about $0.0001 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-30.
Other commands, from other repositories
performance
Interactive ritual to discover what "done" actually means for you. Run once. Produces your personal Define Done config.
verify-done
5pm ritual. Check today's outcomes, log what shipped, flag what slipped, write tomorrow's 3.
define-done
Plan N days of binary outcomes (3 max/day), apply prompting principles, output branded HTML tracker.
brand-setup
Configure brand voice, terminology, compliance guardrails, and style guide for content production.
resume
Resume a ContentForge pipeline run that was interrupted partway through.
output-folder
Print the absolute path to the user-visible ContentForge output folder and open it in the OS file manager.