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.
npx skills add opencue/cuecards --skill source-command-generate-llmsgit 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-generate-llms)<a href="https://agentmods.dev/skills/opencue/cuecards/source-command-generate-llms"><img src="https://agentmods.dev/badge/skills/opencue/cuecards/source-command-generate-llms.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.00041 | $0.00608 |
| Opus 5 | $0.00020 | $0.00304 |
| Sonnet 5 | $0.00008 | $0.00122 |
| Haiku 4.5 | $0.00004 | $0.00061 |
Grade A, and why
source-command-generate-llms 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 — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
source-command-generate-llms
Use this skill when the user asks to run the migrated source command generate-llms.
Command Template
/generate-llms — Regenerate llms.txt Files
Regenerate llms.txt (root) and web/public/llms.txt from current source material.
Run this after any significant change to the README, profiles list, or agent support.
Source files to read first
README.md— product description, tagline, install command, agent listdocs/llms-full.txt— dense technical summary (authoritative)profiles/— list current profiles withls profiles/ | grep -v '^_'package.json— current version and npm package name
Root llms.txt — what it must contain
# cuecards (cue)
<one-paragraph description — from README tagline + what-it-does>
## What it solves
<2–3 sentences on the problem>
## Core docs
- [README](<url>) — <purpose>
- [llms-full.txt](<url>) — <purpose>
- [AGENTS.md](<url>) — <purpose>
- [launch.md](<url>) — <purpose>
## Setup guides
- [macOS](<url>)
- [Linux / WSL2](<url>)
- [Windows](<url>)
## Comparisons
- [cue vs Codex-switcher](<url>)
- [cue vs skillport](<url>)
- [cue vs Kiro Powers](<url>)
## Repository
- GitHub: https://github.com/opencue/cuecards
- npm: https://www.npmjs.com/package/cue-ai
- License: MIT
web/public/llms.txt — condensed version
Same structure as root llms.txt but:
- Shorter descriptions (1 sentence max per link)
- Point to deployed URLs (
https://opencue.github.io/cuecards/...) where they exist - Include the
## GEO filessection pointing tocontent/geo/
After generating
- Diff the new files against the previous versions:
git diff llms.txt web/public/llms.txt - Verify no URLs were broken (spot-check 3 links)
- Commit as:
docs: refresh llms.txt [skip ci]
Automation note
This command is also triggered by the nightly discover workflow. If running
manually, check the workflow hasn't already run today:
git log --oneline --since="24 hours ago" | grep "llms"
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 · 74 lines · 41 tokens per session scan A 2931d97d8d4c
source-command-generate-llms is a skill published in the GitHub repository opencue/cuecards (5 stars, last pushed yesterday), licensed MIT. It adds 41 tokens to every session and 608 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…