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/.agents/skills/source-command-audit-seo/SKILL.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/skills/opencue/cuecards/source-command-audit-seo)<a href="https://agentmods.dev/skills/opencue/cuecards/source-command-audit-seo"><img src="https://agentmods.dev/badge/skills/opencue/cuecards/source-command-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.00034 | $0.00659 |
| Opus 5 | $0.00017 | $0.00329 |
| Sonnet 5 | $0.00007 | $0.00132 |
| Haiku 4.5 | $0.00003 | $0.00066 |
Grade A, and why
source-command-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.
How it starts
The opening of the file, as written. The whole thing — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
source-command-audit-seo
Use this skill when the user asks to run the migrated source command audit-seo.
Command Template
/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 |
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 · 62 lines · 34 tokens per session scan A a88cdf99a766
source-command-audit-seo is a skill published in the GitHub repository opencue/cuecards (5 stars, last pushed today), licensed MIT. It adds 34 tokens to every session and 659 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-09-03.
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…