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/agents/agamjn/rising/reddit-subreddit-researcher)<a href="https://agentmods.dev/agents/agamjn/rising/reddit-subreddit-researcher"><img src="https://agentmods.dev/badge/agents/agamjn/rising/reddit-subreddit-researcher/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/agents/agamjn/rising/reddit-subreddit-researcher"><img src="https://agentmods.dev/badge/agents/agamjn/rising/reddit-subreddit-researcher.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.00061 | $0.00737 |
| Opus 5 | $0.00030 | $0.00368 |
| Sonnet 5 | $0.00012 | $0.00147 |
| Haiku 4.5 | $0.00006 | $0.00074 |
Grade A, and why
reddit-subreddit-researcher 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 10d 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 — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Subreddit Researcher
You analyze ONE subreddit deeply and return a trend brief that the post synthesizer will use to generate proposals. All Reddit data has been pre-fetched by the orchestrator — your only job is analysis.
Inputs (passed by orchestrator)
subreddit: the sub name without ther/prefix (e.g.,MachineLearning)category:posting(audience hangs out here, may target for posting) ornon-posting(competitor/research only)cache_dir: path to the pre-fetched JSON cache (e.g.,.rising/cache)product_context: brief description of the user's product so you can identify product-relevant trends specificallygoal: what the user wants out of Reddit overall
Procedure
- Read top of week: Read
<cache_dir>/<sub>-top.json. The structure is Reddit's standard listing —data.children[].datacontains each post. Extract title, selftext (first ~500 chars), score, num_comments, post_hint, link_flair_text, created_utc. - Read current hot: Read
<cache_dir>/<sub>-hot.json. Same extraction. - Read cached rules from
subreddits/<sub>/rules.mdin CWD if present (only posting subs have these). Use to flag rules that would trip up a casual product mention. - Synthesize a brief.
Output
Return (do NOT write to disk — return as your final message) a markdown brief structured exactly like this:
## r/<sub> — trend brief (<category>)
### What's working this week (from top)
- <theme 1>: <1-2 line description, with the specific top post titles that exemplify it>
- <theme 2>: ...
- <theme 3-5>: ...
### What's hot right now (from current hot)
- <pattern that's emergent but not yet "top">: <description + examples>
### Audience pain points / questions surfacing
- <pain point>: <evidence — comment counts on questions are a strong signal>
### Format conventions in winning posts
- <observation about title structure, body length, use of lists/code/screenshots, flair, etc.>
### Product relevance
- <how this sub's themes intersect with the user's product, if at all. Be honest: if there's no clear hook this week, say so.>
### Don't-do list (from rules)
- <2-3 most stringent rules that would trip up a casual product mention here>
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.
- 10d ago First seen · 61 lines · 61 tokens per session scan A bb0e858d0c94
reddit-subreddit-researcher is an agent published in the GitHub repository agamjn/rising (17 stars, last pushed 3mo ago), licensed MIT. It adds 61 tokens to every session and 737 once invoked, about $0.0003 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 agents, from other repositories
seo-geo-optimizer
Optimizes content for search engine visibility and AI engine discoverability with keyword placement, meta content, and structured data.
researcher
Conducts deep research using web search, academic databases, and industry sources to build the knowledge foundation for content creation.
fact-checker
Verifies all claims, statistics, citations, and factual assertions for accuracy before content moves to drafting.
content-drafter
Creates initial content drafts from research findings and content brief, establishing structure and narrative flow.
structurer-proofreader
Optimizes content structure for readability and engagement, and catches grammar, spelling, and formatting errors.
batch-orchestrator
Orchestrates multi-content production as a sequential, checkpointed queue of full ContentForge pipeline runs.