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/thatrebeccarae/claude-marketingWrote 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/rules/thatrebeccarae/claude-marketing/research-digest)<a href="https://agentmods.dev/rules/thatrebeccarae/claude-marketing/research-digest"><img src="https://agentmods.dev/badge/rules/thatrebeccarae/claude-marketing/research-digest/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/rules/thatrebeccarae/claude-marketing/research-digest"><img src="https://agentmods.dev/badge/rules/thatrebeccarae/claude-marketing/research-digest.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.00036 | $0.01729 |
| Opus 5 | $0.00018 | $0.00864 |
| Sonnet 5 | $0.00007 | $0.00346 |
| Haiku 4.5 | $0.00004 | $0.00173 |
Grade A, and why
research-digest 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 9d 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 — 257 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Research Digest
Generate structured research briefs from RSS feeds, web sources, and industry publications.
Core Capabilities
- Pull from RSS feeds, web search, and curated sources
- Assess source credibility and recency
- Cross-reference findings across multiple sources
- Extract trends, data points, and expert opinions
- Identify counter-arguments and nuance
- Produce actionable research briefs
Workflow
1. Source Collection
Gather raw material from:
- RSS feeds — industry blogs, news sites, newsletters (via any RSS reader/API)
- Web search — targeted queries for recent coverage
- Industry reports — analyst reports, whitepapers, earnings calls
- Social/community — Reddit, Twitter/X, LinkedIn discussions
2. Source Assessment
Evaluate each source on:
| Criterion | Weight | Scale |
|---|---|---|
| Credibility | 30% | Original research > analysis > aggregation > opinion |
| Recency | 25% | Last 7 days > 30 days > 90 days > older |
| Relevance | 25% | Directly on topic > adjacent > tangential |
| Uniqueness | 20% | Novel data > unique angle > common knowledge |
3. Synthesis
- Identify convergent themes (3+ sources saying the same thing)
- Flag divergent views (contradictions between sources)
- Extract specific data points with citations
- Note the "so what" — why this matters for the target audience
4. Brief Generation
Produce a structured markdown brief.
Brief Structure
# Research Brief: [Topic]
**Date:** YYYY-MM-DD
**Depth:** Quick scan / Standard / Deep dive
**Sources reviewed:** [count]
## Executive Summary
- [Key finding 1]
- [Key finding 2]
- [Key finding 3]
## Key Findings
### Finding 1: [Headline]
[2-3 paragraph analysis with source citations]
### Finding 2: [Headline]
[2-3 paragraph analysis with source citations]
## Data Points
| Metric | Value | Source | Date |
|--------|-------|--------|------|
## Expert Perspectives
- "[Quote]" — [Name, Title, Source]
## Counter-Arguments & Nuance
- [Opposing view with source]
## Content Angles
- [Angle 1: how to use this research in content]
- [Angle 2]
## Sources
1. [Source name] — [URL] — [Credibility: High/Medium/Low]
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.
- 9d ago First seen · 257 lines · 36 tokens per session scan A 5560aa9335a9
research-digest is a cursor rule published in the GitHub repository thatrebeccarae/claude-marketing (133 stars, last pushed 3mo ago), licensed MIT. It adds 36 tokens to every session and 1,729 once invoked, about $0.0002 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 cursor rules, from other repositories
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.