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.
git clone --depth 1 https://github.com/hoshikitsunoda/figma-plugins-vibe-coding-templateWrote 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/hoshikitsunoda/figma-plugins-vibe-coding-template/list-commands)<a href="https://agentmods.dev/commands/hoshikitsunoda/figma-plugins-vibe-coding-template/list-commands"><img src="https://agentmods.dev/badge/commands/hoshikitsunoda/figma-plugins-vibe-coding-template/list-commands/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/hoshikitsunoda/figma-plugins-vibe-coding-template/list-commands"><img src="https://agentmods.dev/badge/commands/hoshikitsunoda/figma-plugins-vibe-coding-template/list-commands.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.00000 | $0.00315 |
| Opus 5 | $0.00000 | $0.00158 |
| Sonnet 5 | $0.00000 | $0.00063 |
| Haiku 4.5 | $0.00000 | $0.00032 |
Grade A, and why
list-commands 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 8d 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.
What it actually says
Lists all available commands with descriptions.
What it does:
- Scans
.cursor/commands/directory - Shows each command with a brief description
- Helps users discover what they can do
Usage: /list_commands
Steps
-
Read command files
- List all
.mdfiles in.cursor/commands/ - Read the first line of each file (the title/description)
- List all
-
Format output
- Display as a simple table or list
- Show command name and one-line description
- Group by category if there are many commands
-
Display to user
- Output directly in chat (no file needed)
- Keep it scannable and concise
Output format:
Available commands:
Setup:
/new_plugin — Reset to template and start building a new plugin
/install — Install project dependencies
Development:
/preview_ui — Start browser preview for faster UI iteration
/build — Compile plugin for testing in Figma
/load_in_figma — Step-by-step instructions to load in Figma
/fix_error — AI diagnoses and fixes errors
Workflow:
/save_progress — Commit changes with AI-generated message
/undo_changes — Discard uncommitted changes
Discovery:
/explain_plugin — Explains how the current plugin works
/list_commands — Shows this list
Type any command to run it.
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.
- 8d ago First seen · 52 lines · 0 tokens per session scan A 9c8f84b5a860
list-commands is a command published in the GitHub repository hoshikitsunoda/figma-plugins-vibe-coding-template (21 stars, last pushed 8mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 315 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-30.
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.
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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.