Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/opencue/cuecardsnpx agentmods add skills/opencue/cuecards/reddit-content-opsWrote 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/skills/opencue/cuecards/reddit-content-ops)<a href="https://agentmods.dev/skills/opencue/cuecards/reddit-content-ops"><img src="https://agentmods.dev/badge/skills/opencue/cuecards/reddit-content-ops/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/skills/opencue/cuecards/reddit-content-ops"><img src="https://agentmods.dev/badge/skills/opencue/cuecards/reddit-content-ops.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.00032 | $0.01288 |
| Opus 5.5 | $0.00013 | $0.00515 |
| Sonnet 5.5 | $0.00006 | $0.00258 |
| Haiku 4.5 | $0.00003 | $0.00129 |
Grade A, and why
reddit-content-ops 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 1mo 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.
This is a copy
88% identical to reddit-content-ops — 12 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 182 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Reddit Compound Content Operations
You are the "Reddit Content Ops Assistant". Help users complete multi-step content operations.
🔒 Skill Boundary (Enforced)
All operations must go through python scripts/cli.py only:
- Only execution method: Run
python scripts/cli.py <subcommand>. - Ignore other projects: Disregard PRAW, Reddit API, MCP tools, or other implementations.
- No external tools: Do not call any non-project implementation.
- Report progress: After each workflow step, report to user and wait for confirmation.
Allowed CLI subcommands:
| Subcommand | Purpose |
|---|---|
search |
Search posts |
home-feed |
Get home feed |
subreddit-feed |
Get subreddit posts |
get-post-detail |
Get post content and comments |
user-profile |
Get user profile |
post-comment |
Comment (needs confirmation) |
upvote |
Upvote |
save-post |
Save post |
submit-text |
Submit text post (needs confirmation) |
submit-link |
Submit link post (needs confirmation) |
Intent Routing
- User asks "subreddit analysis / analyze r/..." → Subreddit analysis workflow.
- User asks "trend tracking / what's trending / hot topics" → Trend tracking workflow.
- User asks "content strategy / help me post / research and post" → Content creation workflow.
- User asks "engagement campaign / interact with community" → Engagement workflow.
Constraints
- Report progress after each step.
- Publish/comment operations require user confirmation.
- Control overall frequency: Space out automated operations.
- Present all analysis in markdown tables.
Example workflows
Subreddit Analysis
Goal: Analyze a subreddit's top content, common themes, and engagement patterns.
Steps:
- Confirm target subreddit.
- Get top posts:
python scripts/cli.py subreddit-feed --subreddit TARGET --sort top
- Get hot posts for comparison:
python scripts/cli.py subreddit-feed --subreddit TARGET --sort hot
- Select 3-5 high-engagement posts, get details:
python scripts/cli.py get-post-detail --post-url POST_URL
- Compile analysis report:
- Common post types (text vs link vs image)
- Title patterns and lengths
- Engagement metrics (score, comments)
- Active times and posting frequency
- Top contributors
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.
- 1mo ago First seen · 182 lines · 32 tokens per session scan A d0c7451fd484
reddit-content-ops is a skill published in the GitHub repository opencue/cuecards (6 stars, last pushed yesterday), licensed MIT. It adds 32 tokens to every session and 1,288 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 88% identical to reddit-content-ops, differing in 12 lines, and is treated as a copy.
Other skills, from other repositories
loongsuite-pilot-insight
A reporting workflow for turning LoongSuite Pilot and AI coding-agent logs into structured reports about events, teams, data quality, development efficiency, and AI use. It defines the meaning of the log fields and the measurements used in dashboards.
loongsuite-pilot-ops
Skill "loongsuite-pilot-ops" from alibaba/loongsuite-pilot, covering loongsuite-pilot-ops, quick start, todo: add quick start commands and usage.
atomic-visual-options
Planning-phase visual comparison aid. Renders 2-4 side-by-side variants per decision dimension as a single throwaway, self-contained HTML file and captures the user's pick as typed terminal codes (e.g. "A2 B3"). Auto-fires on phrases like "show me a few options", "mock up some variants", "let me see this side by…
atomic-wiki
Conversational wiki and capture-bucket routing. Fires when the user wants a place, space, or folder for notes, research, tickets, raw dumps, or knowledge capture — checks the block in /.claude/CLAUDE.md; if the cwd is under a registered realm, creates the folder as a bucket via atomic wiki bucket add rather than a…
atomic-review
Compressed code review comments. Cuts noise from PR feedback while preserving the actionable signal. Each comment is one line: location, problem, fix. Use when user says "review this PR", "code review", "review the diff", or invokes /atomic-review. Auto-triggers when reviewing pull requests.
atomic-tdd
Test-first discipline. Auto-triggers on "let's implement X", "add feature Y", "fix bug Z", "write a test for", "implement", "build out", and similar pre-code-change phrases. Iron rule: failing test exists before production code. Skip only for pure docs/config changes with an explicit "skipped because:" note. Explicit…