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/ruizrica/toolkitWrote 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/ruizrica/toolkit/stable)<a href="https://agentmods.dev/commands/ruizrica/toolkit/stable"><img src="https://agentmods.dev/badge/commands/ruizrica/toolkit/stable/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/ruizrica/toolkit/stable"><img src="https://agentmods.dev/badge/commands/ruizrica/toolkit/stable.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.00965 |
| Opus 5.5 | $0.00000 | $0.00386 |
| Sonnet 5.5 | $0.00000 | $0.00193 |
| Haiku 4.5 | $0.00000 | $0.00097 |
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 3d 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.
How it starts
The opening of the file, as written. The whole thing — 165 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Stable Checkpoint
First, run the /save command to commit all current changes.
Then create a stable checkpoint by:
- Creating a timestamped tag in format
stable-YYYYMMDD-HHMMSS - Creating a checkpoint branch from that tag
- Generating comprehensive documentation
Git Operations
# Get current timestamp
TIMESTAMP=$(date +"%Y%m%d-%H%M%S")
TAG_NAME="stable-${TIMESTAMP}"
BRANCH_NAME="checkpoint/${TAG_NAME}"
# Get current commit hash
COMMIT_HASH=$(git rev-parse HEAD)
# Create annotated tag
git tag -a "${TAG_NAME}" -m "Stable checkpoint created on ${TIMESTAMP}
This tag marks a stable state of the project.
Commit: ${COMMIT_HASH}"
# Create checkpoint branch
git branch "${BRANCH_NAME}" "${TAG_NAME}"
echo "✅ Created stable checkpoint:"
echo " 📌 Tag: ${TAG_NAME}"
echo " 🌿 Branch: ${BRANCH_NAME}"
echo " 🔢 Commit: ${COMMIT_HASH:0:7}"
Generate Documentation
Now create a comprehensive stable-readme.md file with:
# Get project information
FILE_COUNT=$(git ls-files | wc -l | tr -d ' ')
CURRENT_BRANCH=$(git branch --show-current)
RECENT_COMMITS=$(git log --oneline -10)
# Check for environment variables
if [[ -f .env ]]; then
ENV_VARS=$(grep -v '^#' .env | grep -v '^$' | sed 's/=.*/=<VALUE>/')
elif [[ -f .env.example ]]; then
ENV_VARS=$(grep -v '^#' .env.example | grep -v '^$')
else
ENV_VARS=""
fi
# Check for package.json dependencies
if [[ -f package.json ]]; then
DEPENDENCIES=$(jq '.dependencies' package.json 2>/dev/null || echo "{}")
else
DEPENDENCIES=""
fi
# Check for requirements.txt
if [[ -f requirements.txt ]]; then
PY_REQUIREMENTS=$(cat requirements.txt)
else
PY_REQUIREMENTS=""
fi
# Get last stable tag for comparison
LAST_STABLE=$(git tag -l "stable-*" | sort -V | tail -2 | head -1 || echo "")
if [[ -n "$LAST_STABLE" && "$LAST_STABLE" != "$TAG_NAME" ]]; then
CHANGES_SINCE=$(git diff --stat "${LAST_STABLE}..HEAD")
else
CHANGES_SINCE=""
fi
Create the documentation file stable-readme.md with:
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.
- 3d ago Changed · +17 lines 5d89e641c4cd
- 1mo ago First seen · 148 lines · 0 tokens per session scan A 17d6423dabb0
stable is a command published in the GitHub repository ruizrica/toolkit (5 stars, last pushed 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 965 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.
Other commands, from other repositories
commit-push-pr
Commit, push, and open a PR.
changelog-update
Actualiza CHANGELOG.md automáticamente analizando los commits desde la última versión/release. Clasifica los cambios por tipo (feat, fix, docs, etc.) usando los commits convencionales del workspace. Opcionalmente sugiere bump de versión semántica. Delega la redacción final a tech-writer.
changelog
Gera changelogs a partir do histórico git e valida commits convencionais. Uso: /changelog [opções].
commit
Smart conventional commit with security validation, branch flow enforcement, and auto-detection. Use for git commit, commit changes, save work, stage and commit.
commit
Automatically generate commit message based on changes and push to current branch. Analyzes git diff to create meaningful commit following conventional commits format. Optionally creates and pushes a git tag.
flow
Universal workflow entry point. Use /flow for skill-driven GitHub development. Verbs: start, commit, pr, review, address, merge, resolve, release, status, learn, setup, explain, debug, design, brainstorm, issue.