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/yonatangross/orchestkitWrote 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/yonatangross/orchestkit/careful)<a href="https://agentmods.dev/commands/yonatangross/orchestkit/careful"><img src="https://agentmods.dev/badge/commands/yonatangross/orchestkit/careful/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/yonatangross/orchestkit/careful"><img src="https://agentmods.dev/badge/commands/yonatangross/orchestkit/careful.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.00084 | $0.01249 |
| Opus 5.5 | $0.00034 | $0.00500 |
| Sonnet 5.5 | $0.00017 | $0.00250 |
| Haiku 4.5 | $0.00008 | $0.00125 |
Grade C, and why
careful scanned grade C 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 15d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
description: "Blocks destructive shell commands once invoked: a PreToolUse Bash guard denies rm -rf outside temp dirs, force pushes and remote branch deletes, git reset --hard, DROP TABLE / DROP DATABASE / TRUNCATE, kube How it starts
The opening of the file, as written. The whole thing — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Auto-generated from skills/careful/SKILL.md
Source: https://github.com/yonatangross/orchestkit
careful, block destructive commands for this session
Invoking this skill registers a PreToolUse hook on Bash (the hooks: block above).
Claude Code keeps a skill's hooks registered for the rest of the session, on every
later turn, so careful stays on until the session ends. There is no off switch:
start a new session to work without it.
What it blocks
| Rule | Blocks | Still allowed |
|---|---|---|
rm-rf |
rm with recursive and force flags (-rf, -fr, -r -f, --recursive --force), xargs rm -rf, and any target the shell expands: $TMPDIR/x, $TMP, $TEMP, $X, $( ), globs, braces, ~ |
the same command when every target is a LITERAL absolute path that lands, after following existing symlinks, strictly inside /tmp, /private/tmp or the configured TMPDIR (trusted only when it is two or more levels deep); write /tmp/build, not $TMPDIR/build, because a command can reassign TMPDIR first (TMPDIR=/ ; rm -rf $TMPDIR/usr); rm -r; rm -f file |
git-push-force |
git push --force, -f (also inside -uf), --force-with-lease[=...], a +branch refspec, to any branch |
git push, git push -u origin <branch> |
git-push-delete |
git push origin --delete <b>, -d <b>, :<b> |
git push origin <b>:<b> |
git-reset-hard |
git reset --hard |
git reset --soft, git reset HEAD <file> |
sql-drop |
DROP TABLE, DROP DATABASE, DROP SCHEMA anywhere in the command, heredocs included |
a SELECT that mentions drop |
sql-truncate |
TRUNCATE TABLE, or a TRUNCATE <name> statement sent to a SQL client |
truncate -s 0 file.log |
kubectl-delete |
kubectl ... delete |
kubectl get, kubectl logs |
terraform-destroy |
terraform destroy, terraform apply -destroy, the same with tofu |
terraform plan, terraform apply |
Matching is on shell words, not substrings: a commit message or grep pattern that
quotes git push --force is text, not a push. Compound commands are split on
;, &&, | and newlines, and the bodies of bash -c, eval, $( ) and the
remote command of ssh host '...' are checked as well.
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.
- 15d ago First seen · 77 lines · 84 tokens per session scan C bd31fa4b7ed5
careful is a command published in the GitHub repository yonatangross/orchestkit (295 stars, last pushed today), licensed MIT. It adds 84 tokens to every session and 1,249 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-02.
Other commands, from other repositories
quick-push
Git add all, commit with Claude, and push to current/new feature branch.
new-feature-branch
Branch-from-fresh-main boilerplate — checkout main, pull, create branch with a meaningful name, push empty so it can be protected.
speckit.git.initialize
Initialize a Git repository with an initial commit.
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.