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/hoshikitsunoda/figma-plugins-vibe-coding-template/resetgit 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/reset)<a href="https://agentmods.dev/commands/hoshikitsunoda/figma-plugins-vibe-coding-template/reset"><img src="https://agentmods.dev/badge/commands/hoshikitsunoda/figma-plugins-vibe-coding-template/reset.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.00000 | $0.00311 |
| Opus 5 | $0.00000 | $0.00156 |
| Sonnet 5 | $0.00000 | $0.00062 |
| Haiku 4.5 | $0.00000 | $0.00031 |
Grade A, and why
reset 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 5d 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
Resets the codebase to template state and starts guided plugin creation.
What it does:
- Checks for uncommitted changes and warns before proceeding
- Resets all files to main branch via
git checkout main -- . - Runs
pnpm installto ensure dependencies are up to date - Asks user to describe their plugin idea
- Follows scaffolding behavior: asks clarifying questions before writing code
Usage: /reset
Important: This will overwrite all current code. Make sure to commit or save any work you want to keep first.
Steps
-
Check for uncommitted changes
- Run
git status --porcelainto check for changes - If there are changes, warn the user: "You have uncommitted changes that will be lost. Are you sure you want to continue?"
- If user says no, stop here
- Run
-
Reset to main
- Run
git checkout main -- . - If this fails, explain the error and stop
- Run
-
Install dependencies
- Run
pnpm install
- Run
-
Start plugin creation
- Ask: "What plugin would you like to build? Describe what it should do."
- After user responds, follow the scaffolding behavior defined in the rules:
- Ask clarifying questions (triggers, outputs, edge cases)
- Confirm the approach before coding
- Update
manifest.jsonwith the new plugin name and id
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.
- 5d ago First seen · 35 lines · 0 tokens per session scan A 2f39b1a8d716
reset 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 311 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.
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.