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/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-add-sub)<a href="https://agentmods.dev/commands/agamjn/rising/reddit-add-sub"><img src="https://agentmods.dev/badge/commands/agamjn/rising/reddit-add-sub.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.00062 | $0.01524 |
| Opus 5 | $0.00031 | $0.00762 |
| Sonnet 5 | $0.00012 | $0.00305 |
| Haiku 4.5 | $0.00006 | $0.00152 |
Grade A, and why
reddit-add-sub scanned grade A with 1 finding 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 7d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -sS --fail-with-body -A "$UA" --connect-timeout 10 --max-time 30 \ How it starts
The opening of the file, as written. The whole thing — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You help the user expand their subreddit list. The common trigger: their existing posting subs have gone stale (same 7-8 subs, running out of fresh angles), or they've discovered a new use case / audience segment and want subs that match it. Your job is to research NEW candidates from the angle they give, validate them, let them curate interactively, and append the approved ones.
Pre-flight check
Confirm the CWD is set up. Require subreddits.md, product.md, goal.md, and .rising/config.json. If any are missing, stop: "This folder isn't set up. Run /reddit-setup first."
Read $ARGUMENTS for the angle/goal/feedback. If empty, ask the user:
"What angle, audience, or use case do you want new subreddits for? A few ways founders use this:
- a new use case you've discovered ('people using us for X')
- an audience segment ('indie game devs', 'AI music creators')
- a complaint about the current list ('my vibecoding subs are tapped out, find adjacent communities') Give me the angle and i'll go research fresh subs."
Wait for their answer before continuing.
Step 1 — Load context and the existing list
Read product.md and goal.md for grounding. Read subreddits.md and extract the names of every sub already listed (both posting and non-posting sections). This is your exclude list, never propose a sub that's already there.
Internalize the user's angle from $ARGUMENTS. Everything you propose should serve that specific angle, not just the generic product.
Step 2 — Generate candidates
Two sources, combine them:
- Brainstorm subs that fit the angle. Think about where this specific audience or use case actually hangs out, plus adjacent and competitor communities.
- Search Reddit for subs you might not know. Derive 3-5 keywords from the angle and run these in parallel (single message, multiple Bash calls):
USERNAME=$(jq -r .reddit_username .rising/config.json)
UA="script:com.github.agamjn.rising:v0.1.0 (by /u/${USERNAME})"
curl -sS --fail-with-body -A "$UA" --connect-timeout 10 --max-time 30 \
"https://www.reddit.com/subreddits/search.json?q=<keyword>&limit=25" \
-o ".rising/cache/sub-search-<keyword>.json"
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.
- 7d ago First seen · 125 lines · 62 tokens per session scan A bfa2f125ebac
reddit-add-sub is a command published in the GitHub repository agamjn/rising (17 stars, last pushed 3mo ago), licensed MIT. It adds 62 tokens to every session and 1,524 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). 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.
output-folder
Print the absolute path to the user-visible ContentForge output folder and open it in the OS file manager.
create-content
Run the full 10-phase content production pipeline — research, draft, fact-check, humanize, and publish.