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/ruizrica/toolkit/savegit clone --depth 1 https://github.com/ruizrica/toolkitWhat 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.00863 |
| Opus 5 | $0.00000 | $0.00432 |
| Sonnet 5 | $0.00000 | $0.00173 |
| Haiku 4.5 | $0.00000 | $0.00086 |
Grade B, and why
save scanned grade B with 1 finding 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 2d 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.
Asks the agent to reveal its instructionsmediumSystem prompt leakage
Directions to print, repeat or translate the system prompt extract configuration the operator did not intend to expose.
| **Resolve manually** | Leave conflicts, show instructions | How it starts
The opening of the file, as written. The whole thing — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/save
Save work by committing changes, merging WIP to main, and cleaning up the worktree and branch. This command handles both WIP worktree workflows and regular branch workflows.
Usage
/save [commit message]
Arguments
| Argument | Required | Default | Description |
|---|---|---|---|
| commit message | No | "WIP save" | Message for the commit |
How It Works
Step 1: Commit Current Changes
git add .
git diff --cached --quiet || git commit -m "[message]"
Only commits if there are staged changes.
Step 2: Detect Environment
Determines if currently in a linked worktree or regular branch:
- Linked worktree: Has worktree-specific git directory
- Regular branch: Standard git checkout
Step 3: Merge to Main
Merges the current branch into main with conflict handling.
Step 4: Cleanup
For worktree workflow:
- Removes the worktree directory
- Deletes the WIP branch
For regular branch:
- Deletes the feature branch
Conflict Handling
If merge conflicts occur, you're prompted to choose:
| Option | Description |
|---|---|
| Keep WIP changes | Your new work overwrites main (recommended) |
| Keep main changes | Discard your WIP, keep what's in main |
| Resolve manually | Leave conflicts, show instructions |
| Abort merge | Cancel merge, keep worktree for later |
Examples
# Save with default message
/save
# Save with custom message
/save "Add user authentication feature"
# Save after completing a feature
/save "Implement OAuth login with Google provider"
Workflow Diagram
┌─────────────────────────────────┐
│ Commit Current Changes │
│ git add . && git commit -m "..."│
└────────────────┬────────────────┘
│
┌────────────────▼────────────────┐
│ Detect Environment │
│ Worktree or Regular Branch? │
└────────────────┬────────────────┘
│
┌────────────────▼────────────────┐
│ Switch to Main Worktree │
│ (if in linked worktree) │
└────────────────┬────────────────┘
│
┌────────────────▼────────────────┐
│ Merge WIP Branch │
│ git merge wip-branch --no-edit │
└────────────────┬────────────────┘
│
┌──────┴──────┐
│ Success? │
└──────┬──────┘
▼ ▼
┌────────┐ ┌────────────┐
│ Yes │ │ No │
└───┬────┘ │ Handle │
│ │ Conflicts │
│ └─────┬──────┘
│ │
└──────┬──────┘
▼
┌────────────────────────────────┐
│ Cleanup │
│ Remove worktree, delete branch │
└────────────────────────────────┘
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.
- 2d ago First seen · 139 lines · 0 tokens per session scan B 8b8138e17c6b
save is a command published in the GitHub repository ruizrica/toolkit (5 stars, last pushed 17d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 863 tokens. A static security scan graded it B with 1 finding (asks the agent to reveal its instructions). 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.