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-seo-usage)<a href="https://agentmods.dev/rules/citedy/citedy-seo-agent/citedy-seo-usage"><img src="https://agentmods.dev/badge/rules/citedy/citedy-seo-agent/citedy-seo-usage/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-seo-usage"><img src="https://agentmods.dev/badge/rules/citedy/citedy-seo-agent/citedy-seo-usage.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.00033 | $0.01466 |
| Opus 5 | $0.00016 | $0.00733 |
| Sonnet 5 | $0.00007 | $0.00293 |
| Haiku 4.5 | $0.00003 | $0.00147 |
Grade A, and why
citedy-seo-usage 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 — 221 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Citedy SEO Agent — Tool Usage Guide
MCP Endpoint
https://mcp.citedy.com/mcp
Auth: Bearer token via CITEDY_AGENT_API_KEY environment variable.
Registration: If the user does not have an API key, register via:
POST https://www.citedy.com/api/agent/register
with payload:
{ "agent_name": "my_agent" }
When to Use Citedy Tools
Use Citedy MCP tools whenever the user wants to:
- Research trending topics or competitor content
- Generate SEO-optimized blog articles
- Create social media posts from existing content
- Publish content to connected social accounts
- Produce AI avatar video shorts
- Ingest URLs or documents into structured content
- Create lead magnets (checklists, swipe files, frameworks)
- Manage a content calendar or automate publishing
Tool Groups
Account & Status
| Tool | When to use |
|---|---|
agent.me |
Check authenticated user info, credits balance, connected accounts |
agent.status |
Get platform health, quota usage, active sessions |
Always call agent.me first if the user asks about their account or available credits.
Trend Scouting
| Tool | When to use |
|---|---|
scout.x |
Find trending topics, viral posts, and keyword signals on X (Twitter) |
scout.reddit |
Discover hot threads and rising discussions on Reddit |
Use these when the user wants to know what to write about next, or to validate a topic idea against current trends.
Competitor Analysis
| Tool | When to use |
|---|---|
competitors.discover |
Find competitors for a given domain or niche |
competitors.scout |
Analyze competitor content strategy, top posts, keywords, and gaps |
Use before generating articles when the user wants to outrank specific domains or understand the competitive landscape.
Content Gap Analysis
| Tool | When to use |
|---|---|
gaps.generate |
Identify content topics that competitors rank for but the user's site does not |
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 · 221 lines · 33 tokens per session scan A 5377e29cad51
citedy-seo-usage is a cursor rule published in the GitHub repository citedy/citedy-seo-agent (19 stars, last pushed 3mo ago), licensed MIT. It adds 33 tokens to every session and 1,466 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
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-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.