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/save-progressgit 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/save-progress)<a href="https://agentmods.dev/commands/hoshikitsunoda/figma-plugins-vibe-coding-template/save-progress"><img src="https://agentmods.dev/badge/commands/hoshikitsunoda/figma-plugins-vibe-coding-template/save-progress.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 | $0.00000 | $0.00323 |
| Opus 5 | $0.00000 | $0.00161 |
| Sonnet 5 | $0.00000 | $0.00065 |
| Haiku 4.5 | $0.00000 | $0.00032 |
Grade A, and why
save-progress 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 4d 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
Commits all current changes with an AI-generated commit message.
What it does:
- Summarizes recent changes by analyzing the git diff
- Stages all changes and commits with a descriptive message
- Optionally pushes to remote
Usage: /save_progress
Steps
-
Check for changes
- Run
git status --porcelain - If no changes, tell user: "No changes to save. Your work is already committed."
- Stop here if nothing to commit
- Run
-
Analyze changes
- Run
git diff --statto see what files changed - Run
git diffto understand the actual changes - Summarize what was done in 1-2 sentences
- Run
-
Stage and commit
- Run
git add -A - Generate a commit message following conventional format:
- Use present tense ("Add feature" not "Added feature")
- Keep under 72 characters
- Be specific about what changed
- Run
git commit -m "<generated message>" - Show the commit message to user
- Run
-
Ask about pushing
- Ask: "Want me to push this to the remote repository?"
- If yes, run
git push - If push fails (no remote, auth issues), explain the error in plain language
Example commit messages:
- "Add batch layer renaming with prefix/suffix options"
- "Fix selection handler to include nested children"
- "Update UI with color picker component"
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.
- 4d ago First seen · 42 lines · 0 tokens per session scan A 3045a7e89efa
save-progress 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 323 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
cr
When user uses /cr slash command, review uncommitted code changes with reusable language-aware rules, preferring project-local review commands or rules when they exist.
commit
智能创建 git 提交，分析代码变更并生成符合项目规范的提交信息.
pr-review
Review the current branch changes and suggest PR content.
changelog
Summarize staged git changes into a concise changelog/commit message.
wrap
End-of-session ritual. Updates handoff, priorities, daily log, and triggers synapse hygiene. Optional git commit with --commit flag.
push
Push code, automatically run /commit if not yet committed, compute elapsed time and log work to Jira accurately. Handles all edge cases: no-ticket, no-state, re-push, multi-task, duplicate worklog, corrupt state, negative elapsed, wrong commit author.