Borrowing it
Nothing to install: this file belongs to opencue/cuecards. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/opencue/cuecards/main/.claude/commands/audit-seo.mdgit clone --depth 1 https://github.com/opencue/cuecardsWrote 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/commands/opencue/cuecards/audit-seo)<a href="https://agentmods.dev/commands/opencue/cuecards/audit-seo"><img src="https://agentmods.dev/badge/commands/opencue/cuecards/audit-seo.svg" alt="Measured on agentmods" 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.00027 | $0.00618 |
| Opus 5 | $0.00014 | $0.00309 |
| Sonnet 5 | $0.00005 | $0.00124 |
| Haiku 4.5 | $0.00003 | $0.00062 |
Grade A, and why
audit-seo 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 3d 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.
What it actually says
/audit-seo — SEO Health Check for cuecards
Audit the cuecards repo for SEO completeness and correctness.
What to check
1. JSON-LD structured data in README.md
- Verify
<script type="application/ld+json">block is NOT inside an HTML comment - Validate JSON parses cleanly:
python3 -c "import json; json.loads(open('README.md').read().split('application/ld+json\">')[1].split('</script>')[0])" - Check
@type,name,description,url,codeRepository,offersare all present
2. web/public/robots.txt
- Exists:
test -f web/public/robots.txt - Contains
Sitemap:directive pointing to sitemap.xml - Does not disallow
/globally
3. web/public/sitemap.xml
- Exists:
test -f web/public/sitemap.xml - Valid XML:
python3 -c "import xml.etree.ElementTree as ET; ET.parse('web/public/sitemap.xml')" - All
<loc>URLs use HTTPS
4. web/public/llms.txt
- Exists and contains the product name and at least one
##section
5. content/seo/ completeness
- All 5 files present:
ls content/seo/ | wc -l= 5 keywords.ymlhas at least 3 clusterspage-titles.ymlcovers home, getting_started, faq at minimummeta-descriptions.yml≤ 155 chars per entry: check withpython3 -c "import yaml; d=yaml.safe_load(open('content/seo/meta-descriptions.yml')); [print(k,len(v)) for k,v in d['pages'].items() if len(v)>155]"
6. content/geo/ completeness
- All 5 files present:
ls content/geo/ | wc -l= 5 entity-profile.jsonvalidates:python3 -m json.tool content/geo/entity-profile.json > /dev/null
Report format
Output a table:
| Check | Status | Notes |
|---|---|---|
| JSON-LD live in README | ✅/❌ | ... |
| robots.txt | ✅/❌ | ... |
| sitemap.xml | ✅/❌ | ... |
| llms.txt (web) | ✅/❌ | ... |
| content/seo/ (5 files) | ✅/❌ | ... |
| content/geo/ (5 files) | ✅/❌ | ... |
| meta-descriptions ≤155 | ✅/❌ | list any violations |
End with a prioritised fix list for any ❌ items.
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.
- 3d ago First seen · 55 lines · 27 tokens per session scan A 3450acc567cf
audit-seo is a command published in the GitHub repository opencue/cuecards (5 stars, last pushed today), licensed MIT. It adds 27 tokens to every session and 618 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-09-03.
Other commands, from other repositories
atomic-help
Route a lost user to the right atomic verb, skill, agent, or binary subcommand. Bare invocation reads git state and recommends one next step. Topic keyword or freeform intent → focused pointer. tour → guided walkthrough of the system. Help router, not duplicated docs.
atomic-plan
Write a design doc (concepts, business rules, approaches) and a checkpoint-table spec (contract) for non-trivial work; inline spec only for trivial. Gauges triviality; loops spec authoring with subagents. Human-facing artifact, Mermaid diagrams allowed.
subagent-implementation
Orchestrate implement→review subagent loop until task complete. Reads the approved spec, writes a thin brief to .claude/.scratchpad/, dispatches fresh-context subagents, loops until reviewer signs off, commits per green iteration, then updates repo docs.
follow-up
Review and act on pending reminders. Bare invocation shows all reminders as an indexed list; cron-fired invocation (/follow-up due ) surfaces the specific reminder and waits for a response; /follow-up review lists stale project follow-up entries for per-item disposition (extend/close/promote/skip). Transport-aware…
quick-fix
Run the implement→review subagent loop without the planning phase — for straightforward fixes with a known cause and one obvious approach, regardless of how many files the change spreads across. Skips the spec gate, worktree gate, and finalize ceremony (implementation log, docs, signals) that /subagent-implementation…
documentation
Bootstrap and maintain project documentation surfaces. Two modes: bootstrap (discover doc files, index them in CLAUDE.md) and authoring (scan for unindexed docs, match diff against indexed surfaces, walk stale/incomplete/missing items with Yes/Later/Remind/Skip).