agentmods.dev

startup: Command for Claude Code

.cursor/commands/list.md

list is a command for Claude Code, Cursor from JanUmansky/startup. It costs 0 tokens per session (654 once invoked), scanned A, original, MIT.

A command that lists the active coding-agent assistants available in a repository. It reads their command files and describes each assistant’s purpose and areas of focus.

In plain words
What is it for?
Use it to inspect the repository’s assistant roster, separate system commands from hired assistants, and see what each available assistant is meant to do.
Why use it?
It gives developers a quick view of which assistants are available and identifies missing assistant files.

Command for Claude CodeCursor

Written for Cursor and Claude Code: installed under .cursor/, but also a Claude Code command (commands/*.md).

This is JanUmansky/startup's own configuration. It tells Claude Code and Cursor how to work on startup itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything startup configures →

not rated 2repo 9mo ago A scan 0 tokens original MIT
View source ↗ JanUmansky/startup
Reuse

Borrowing it

Nothing to install: this file belongs to JanUmansky/startup. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/JanUmansky/startup/main/.cursor/commands/list.md
Clone the repo
git clone --depth 1 https://github.com/JanUmansky/startup

Made for: Claude Code, Cursor.

Wrote 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.

agentmods badge for list

README.md
[![agentmods](https://agentmods.dev/badge/commands/janumansky/startup/list/github.svg)](https://agentmods.dev/commands/janumansky/startup/list)
Your own site
<a href="https://agentmods.dev/commands/janumansky/startup/list"><img src="https://agentmods.dev/badge/commands/janumansky/startup/list/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.

agentmods 80×15 button for list

Your own site · 80×15
<a href="https://agentmods.dev/commands/janumansky/startup/list"><img src="https://agentmods.dev/badge/commands/janumansky/startup/list.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 654 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.00654
Opus 5.5 $0.00000 $0.00262
Sonnet 5.5 $0.00000 $0.00131
Haiku 4.5 $0.00000 $0.00065

Measured 2mo ago against content hash f0f0bd41d23b, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

list 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 2mo 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.

.cursor/commands/list.md · 97 lines

How it starts

The opening of the file, as written. The whole thing — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/list — Show active assistants (slash commands)

Definitions:

  • COMMANDS_DIR = the folder where command markdown files live (this file is already in it).
  • ROSTER_FILE = COMMANDS_DIR + "/_roster.md"

Goal: Display the active assistants and what they do.

Output requirements

  • Print a readable list of assistants with:
    • Command name (e.g., /bob)
    • One-line mission (from the assistant file, if possible)
    • Focus/scope highlights (bullets, short)
  • Separate "system commands" (hire/fire/update/list) from "hired assistants".

Steps

  1. Identify system commands:

    • Treat these as system commands: hire, fire, update, list, define
    • Do not include them in "Active Assistants".

  2. Try roster-first:

    • If ROSTER_FILE exists and contains an “Active Assistants” section, parse it and list assistants in that section.

  3. Validate roster entries:

    • For each assistant listed in roster, confirm COMMANDS_DIR + "/.md" exists.
    • If missing, mark it as “missing file”.

  4. If roster missing or empty:

    • Fallback: scan COMMANDS_DIR for *.md files (excluding _roster.md and system commands)
    • Consider each remaining file an assistant command.

  5. Enrich from assistant files:

    • For each assistant command file, attempt to extract:
      • Mission: first paragraph under “## Mission”
      • Optional: first 3 bullets under “### In scope”
    • If sections are missing, show “(no mission found)” etc.

  6. Present results:

    • First: System commands available (always show).
    • Then: Active assistants.

Output Format

Structure the response with emojis and tables:

🛠️ System Commands

Command Description
/hire Create a new specialist agent
/fire Remove an agent
/update Modify an agent's scope
/list Show this overview
/define Create project-wide rules

👥 Your Team

Agent Mission Focus
🧑‍💻 /dinesh Backend API Guardian validation, auth, routes
🔧 /gilfoyle DevOps Specialist infra, CI/CD, monitoring

Read the full file on GitHub · 97 lines

Changes

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.

  1. 2mo ago First seen · 97 lines · 0 tokens per session scan A f0f0bd41d23b

Subscribe to this mod's changes

list is a command published in the GitHub repository JanUmansky/startup (2 stars, last pushed 9mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 654 tokens. 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-31.

Related

list compared with commands from other repositories

list next to 6 commands from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
listJanUmansky/startupCommand29mo agoMITA0Claude Code, Cursor
checklistgithub/spec-kitCommand148kyesterdayMITA13Claude Code
clarifygithub/spec-kitCommand148kyesterdayMITA27Claude Code
specifygithub/spec-kitCommand148kyesterdayMITA13Claude Code
analyzegithub/spec-kitCommand148kyesterdayMITA26Claude Code
convergegithub/spec-kitCommand148kyesterdayMITA35Claude Code
implementgithub/spec-kitCommand148kyesterdayMITA14Claude Code