stable

A Git checkpoint command that saves current changes, then records them with a timestamped tag, branch, and documentation.

In plain words
What is it for?
Saving a documented version of a project that you can inspect or use as the starting point for later work.
Why use it?
It gives you a clearly named restore point before or after a significant change.

Command

Install

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.

agentmods
npx agentmods add commands/ruizrica/toolkit/stable
Clone the repo
git clone --depth 1 https://github.com/ruizrica/toolkit
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 892 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00892
Opus 5 $0.00000 $0.00446
Sonnet 5 $0.00000 $0.00178
Haiku 4.5 $0.00000 $0.00089

Measured 2d ago against content hash 17d6423dabb0, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

stable 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 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.

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.

docs/commands/stable.md · 148 lines

How it starts

The opening of the file, as written. The whole thing — 148 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/stable

Create a stable checkpoint with tags and comprehensive documentation. This command first runs /save to commit current changes, then creates a timestamped tag and checkpoint branch.

Usage

/stable [description]

Arguments

Argument Required Description
description No Optional description for the checkpoint

How It Works

  1. Save - Run /save to commit all current changes
  2. Create Tag - Create annotated tag: stable-YYYYMMDD-HHMMSS
  3. Create Branch - Create checkpoint branch from the tag
  4. Generate Docs - Create comprehensive stable-readme.md
  5. Commit Docs - Add the documentation to the repository

What Gets Created

Item Example Description
Tag stable-20260130-103000 Annotated git tag
Branch checkpoint/stable-20260130-103000 Checkpoint branch
Documentation stable-readme.md Checkpoint documentation

Documentation Contents

The generated stable-readme.md includes:

Checkpoint Information

  • Tag name and commit hash
  • Timestamp and source branch
  • Total file count

Restore Instructions

  • How to view the checkpoint
  • How to create a new branch from it
  • How to continue development

Project State

  • Recent commit history
  • File structure listing
  • Environment variables (sanitized)
  • Dependencies (npm/pip)
  • Changes since last stable checkpoint
  • Remote repository information

Usage Examples

  • Compare with current state
  • Merge into another branch
  • Push to remote

Example

/stable v1.0-auth-complete

Output:

✅ Created stable checkpoint:
  📌 Tag: stable-20260130-103000
  🌿 Branch: checkpoint/stable-20260130-103000
  🔢 Commit: a1b2c3d

Documentation Example

# Stable Checkpoint Documentation

## Checkpoint Information
- **Tag:** `stable-20260130-103000`
- **Branch:** `checkpoint/stable-20260130-103000`
- **Commit:** `a1b2c3d4e5f6...`
- **Timestamp:** 20260130-103000
- **Created from branch:** main
- **Total files:** 47

## How to Restore This Checkpoint

### To view this checkpoint:
git checkout stable-20260130-103000

### To create a new branch from this checkpoint:
git checkout -b feature/new-branch stable-20260130-103000

### To restore and continue development:
git checkout checkpoint/stable-20260130-103000

## Recent Commits
- a1b2c3d Add user authentication
- b2c3d4e Implement OAuth flow
- c3d4e5f Add login page

## Dependencies
{
  "express": "^4.18.0",
  "passport": "^0.6.0"
}

## Changes Since Last Checkpoint
15 files changed, 847 insertions(+), 123 deletions(-)

Read the full file on GitHub · 148 lines

Changes

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.

  1. 2d ago First seen · 148 lines · 0 tokens per session scan A 17d6423dabb0

Subscribe to this mod's changes

stable 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 892 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.