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/citedy/citedy-seo-agentWrote 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/citedy/citedy-seo-agent/citedy-content-workflow)<a href="https://agentmods.dev/rules/citedy/citedy-seo-agent/citedy-content-workflow"><img src="https://agentmods.dev/badge/rules/citedy/citedy-seo-agent/citedy-content-workflow/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/citedy/citedy-seo-agent/citedy-content-workflow"><img src="https://agentmods.dev/badge/rules/citedy/citedy-seo-agent/citedy-content-workflow.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.00020 | $0.01038 |
| Opus 5 | $0.00010 | $0.00519 |
| Sonnet 5 | $0.00004 | $0.00208 |
| Haiku 4.5 | $0.00002 | $0.00104 |
Grade A, and why
citedy-content-workflow 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 — 152 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Citedy Content Creation Workflow
Follow this workflow when the user wants to create and distribute SEO content using Citedy.
Step 1 — Scout: Discover What to Write About
Option A — Trend-based
scout.x(query, limit)
scout.reddit(query, subreddits, limit)
Use when the user wants to capitalize on current conversations and viral topics.
Option B — Competitor-based
competitors.discover(domain)
competitors.scout(competitorDomain)
Use when the user wants to outrank specific sites or understand the market landscape.
Pick a keyword or topic from the results and carry it forward.
Step 2 — Plan: Identify Gaps and Schedule
gaps.generate(domain, competitorDomains)
schedule.gaps(domain)
gaps.generatereturns a ranked list of content opportunities the user's site is missing.schedule.gapsshows which gaps are already on the calendar and which are open.
Select the highest-priority gap or confirm the user's chosen topic.
Step 3 — Generate: Create the Article
article.generate({
keyword,
language, // default: "en", supports 55 languages
persona, // optional: writing voice/style
illustrations, // true = include AI-generated images
voiceover, // true = include TTS audio
internalLinks, // true = auto-link to existing content
sourceContent // optional: pass ingested content as source
})
article.generate returns generated article payload directly. For history or follow-up retrieval, use article.list.
Step 4 — Enhance: Illustrations and Voice-Over
Illustrations and voice-over are included in article.generate options — no separate step needed when enabled.
If missing media, regenerate via article.generate with illustrations: true and/or audio: true.
Step 5 — Adapt: Create Social Versions
adapt.generate({
articleId,
platforms: ["x", "linkedin", "facebook", "reddit", "instagram"]
})
Each platform gets a version optimized for its format and character limits:
- X — thread or single post, punchy hook
- LinkedIn — professional tone, structured paragraphs
- Facebook — conversational, engagement-focused
- Reddit — value-first, no hard sell
- Instagram — caption + hashtag suggestions
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 · 152 lines · 20 tokens per session scan A 49b9b3507960
citedy-content-workflow is a cursor rule published in the GitHub repository citedy/citedy-seo-agent (19 stars, last pushed 3mo ago), licensed MIT. It adds 20 tokens to every session and 1,038 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 cursor rules, from other repositories
mpa-strict-rules
MPA-First Development Mandate - Strict rules for building performant, resilient Multi-Page Applications.
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.