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/codeready-toolchain/tarsy/commitgit clone --depth 1 https://github.com/codeready-toolchain/tarsyWhat 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.01180 |
| Opus 5 | $0.00000 | $0.00590 |
| Sonnet 5 | $0.00000 | $0.00236 |
| Haiku 4.5 | $0.00000 | $0.00118 |
Grade A, and why
commit 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 yesterday.
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 — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Commit Changes
Analyze uncommitted changes, create a branch if needed, and commit with a well-structured message.
Step 1: Detect the default branch
Run git remote show origin (or fall back to checking which of main/master exists locally) to determine the default branch name.
Step 2: Branch management
If currently on the default branch
All uncommitted changes belong to a new feature/fix. Create a new branch before committing:
- Analyze the changes (see Step 3) to understand their purpose.
- Create a descriptive branch name:
<type>/<short-slug>where type isfeat,fix,refactor,docs,chore,test, etc. - Run
git checkout -b <branch-name>.
If currently on a non-default branch
Ask the user:
You're on branch
<current-branch>. Do you want to:
- Commit to this branch
- Create a new branch from
<default-branch>
If the user picks option 2, explicitly branch from <default-branch>:
- If there are uncommitted changes that would prevent checkout, ask the user whether to stash them first or abort.
git fetch origingit checkout <default-branch>git pull --ff-only- Re-apply stashed changes if applicable (
git stash pop). - Analyze the changes (see Step 3) and create a branch:
git checkout -b <branch-name>.
Step 3: Analyze changes
Run these commands in parallel to understand the full picture:
git status— see all tracked/untracked changesgit diff— unstaged changesgit diff --cached— staged changesgit diff HEAD— combined view of all uncommitted changes Also rungit log --oneline -10to glance at recent commit style. If the existing messages are well-structured and consistent, adopt their conventions (prefix style, tense, etc.) alongside the format rules below. If they are messy or inconsistent, ignore them and follow this command's format exclusively.
Review all changes carefully. Understand what changed and why before writing the commit message.
Step 4: Stage and commit
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.
- yesterday First seen · 116 lines · 0 tokens per session scan A 41a8067e67d5
commit is a command published in the GitHub repository codeready-toolchain/tarsy (10 stars, last pushed yesterday), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,180 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
api-mock
You are an API mocking expert specializing in creating realistic mock services for development, testing, and demonstration purposes. Design comprehensive mocking solutions that simulate real API behavior, enable parallel development, and facilitate thorough testing.
update-changelog-and-tag
You are preparing a release. Follow these steps precisely.
post
Post the current OCR review to a GitHub PR.
show
Display a past OCR review session.
test-feature
Test a React Native feature on the running simulator/emulator. Verifies UI, user flows, and internal state. Generates a persistent Maestro test file.
history
List past OCR review sessions.