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 agentmods add commands/janumansky/startup/listgit clone --depth 1 https://github.com/JanUmansky/startupWhat 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 | $0.00000 | $0.00654 |
| Opus 5 | $0.00000 | $0.00327 |
| Sonnet 5 | $0.00000 | $0.00131 |
| Haiku 4.5 | $0.00000 | $0.00065 |
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 yesterday.
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 — 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
-
Identify system commands:
- Treat these as system commands: hire, fire, update, list, define
- Do not include them in "Active Assistants".
-
Try roster-first:
- If ROSTER_FILE exists and contains an “Active Assistants” section, parse it and list assistants in that section.
-
Validate roster entries:
- For each assistant listed in roster, confirm COMMANDS_DIR + "/.md" exists.
- If missing, mark it as “missing file”.
-
If roster missing or empty:
- Fallback: scan COMMANDS_DIR for
*.mdfiles (excluding_roster.mdand system commands) - Consider each remaining file an assistant command.
- Fallback: scan COMMANDS_DIR for
-
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.
- For each assistant command file, attempt to extract:
-
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 |
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.
- yesterday First seen · 97 lines · 0 tokens per session scan A f0f0bd41d23b
list is a command published in the GitHub repository JanUmansky/startup (2 stars, last pushed 7mo 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.
Other commands, from other repositories
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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.