Borrowing it
Nothing to install: this file belongs to WingedGuardian/GENesis-AGI. 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/WingedGuardian/GENesis-AGI/main/.claude/commands/list-skills.mdgit clone --depth 1 https://github.com/WingedGuardian/GENesis-AGIWrote 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/wingedguardian/genesis-agi/list-skills)<a href="https://agentmods.dev/commands/wingedguardian/genesis-agi/list-skills"><img src="https://agentmods.dev/badge/commands/wingedguardian/genesis-agi/list-skills/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/commands/wingedguardian/genesis-agi/list-skills"><img src="https://agentmods.dev/badge/commands/wingedguardian/genesis-agi/list-skills.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.00052 | $0.00810 |
| Opus 5 | $0.00026 | $0.00405 |
| Sonnet 5 | $0.00010 | $0.00162 |
| Haiku 4.5 | $0.00005 | $0.00081 |
Grade A, and why
list-skills 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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
List Skills
Show a roster of the Genesis skill catalog (Tier-1 + Tier-2), grouped by
tier, with a one-line description each. This complements the automatic
skill-injection nudge (which surfaces one matching skill per prompt) — use
/list-skills to browse the catalog at will. Note: this lists the Genesis
catalog only, NOT Claude Code plugin skills (e.g. superpowers:*), which are
invoked separately and are not part of this catalog.
Arguments
Optional filter after /list-skills:
/list-skills— list everything./list-skills browser— only skills whose name, description, or keywords match "browser" (case-insensitive).
Steps
-
Read the catalog. The roster comes from the prebuilt catalog at
~/.genesis/skill_catalog.json. Keeping it fresh is the skill-injection hook's job — on every prompt it spawns a background regeneration (with the correct interpreter) whenever the file is missing or older than an hour, so/list-skillsonly READS the catalog and never regenerates it itself:cat ~/.genesis/skill_catalog.jsonStructure:
{ "generated_at", "tier1": [...], "tier2": [...] }, each entry{ name, description, keywords, tier, path }. Tier-1 skills live in.claude/skills/; Tier-2 insrc/genesis/skills/and~/.genesis/skill-library/.If the catalog is missing, empty, or not valid JSON, do NOT render an empty roster as though no skills exist:
- Missing or empty (e.g. a first-ever run before the hook's background
regeneration has landed): tell the user it is still being generated and to
run
/list-skillsagain shortly. - Present but not valid JSON (likely corrupt): the hook refreshes only on
age, so a retry will NOT fix it — tell the user to delete
~/.genesis/skill_catalog.json(the injection hook rebuilds it on the next prompt), then re-run/list-skills.
Either way, stop rather than showing an empty roster.
- Missing or empty (e.g. a first-ever run before the hook's background
regeneration has landed): tell the user it is still being generated and to
run
-
Present the roster. State up front that this is the Genesis skill catalog (Tier-1 + Tier-2), NOT session commands or Claude Code plugin skills (
superpowers:*etc.), and show the catalog'sgenerated_attimestamp so the user can judge freshness (it refreshes at most hourly, so a just-added skill may briefly lag). Group and sort by name within each group:- Tier 1 — always-indexed — the
tier1entries. - Tier 2 — specialized — the
tier2entries. - One line per skill:
**<name>** — <first sentence of its description>. Keep each to a single scannable line; truncate long descriptions rather than reflowing them. - Show the count per tier, the grand total, and the
generated_attime.
- Tier 1 — always-indexed — the
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 · 69 lines · 52 tokens per session scan A 33644474da7f
list-skills is a command published in the GitHub repository WingedGuardian/GENesis-AGI (96 stars, last pushed today), licensed MIT. It adds 52 tokens to every session and 810 once invoked, about $0.0003 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 commands, from other repositories
review-prs
Check open PRs for human feedback before picking new work.
brief-refresh
Audit docs for staleness and contradictions, propose new features.
next-issue
Fetch the next ready-for-agent issue by priority.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.