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/danielraffel/generous-corp-marketplaceWrote 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/danielraffel/generous-corp-marketplace/lock)<a href="https://agentmods.dev/commands/danielraffel/generous-corp-marketplace/lock"><img src="https://agentmods.dev/badge/commands/danielraffel/generous-corp-marketplace/lock.svg" alt="Measured on agentmods" 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.00007 | $0.00406 |
| Opus 5 | $0.00003 | $0.00203 |
| Sonnet 5 | $0.00001 | $0.00081 |
| Haiku 4.5 | $0.00001 | $0.00041 |
Grade A, and why
lock 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 8d 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.
What it actually says
Worktree Lock Command
Lock a worktree to prevent it from being removed accidentally.
Usage
/worktree-manager:lock <worktree-path> [--reason="explanation"]
Instructions for Claude
When user invokes this command:
-
Parse arguments:
- Extract worktree path (required)
- Extract optional
--reason="text"→reason: "text"
-
Call MCP tool:
- Use
mcp__worktree__worktree_lock - Pass
worktree_pathand optionalreason
- Use
-
Display results:
- Show lock confirmation:
- ✅ Worktree locked:
- Reason: (if provided)
- Explain that worktree cannot be removed until unlocked
- Mention /worktree-manager:unlock to unlock
- Show lock confirmation:
-
Error handling:
- Worktree doesn't exist → suggest checking path
- Already locked → inform user it's already locked
- Permission errors → explain issue
Examples
Lock without reason:
User: /worktree-manager:lock ~/worktrees/important-feature
Claude: ✅ Worktree locked: ~/worktrees/important-feature
Cannot be removed until unlocked with /worktree-manager:unlock
Lock with reason:
User: /worktree-manager:lock ~/worktrees/feature-x --reason="In active development"
Claude: ✅ Worktree locked: ~/worktrees/feature-x
Reason: In active development
Use Cases
- Protect worktrees with uncommitted experiments
- Prevent cleanup during long-running tasks
- Mark worktrees as "do not touch"
- Team collaboration safety
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.
- 8d ago First seen · 64 lines · 7 tokens per session scan A aa80a5cb99fe
lock is a command published in the GitHub repository danielraffel/generous-corp-marketplace (11 stars, last pushed 9d ago), licensed MIT. It adds 7 tokens to every session and 406 once invoked, about $0.0000 per session on Opus 5. 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-30.
Other commands, from other repositories
commit
A command that examines staged Git changes and proposes a commit message using the Conventional Commits format, such as feat, fix, or docs. Git is a tool for tracking changes to code.
release-notes
Generate consistent, well-structured release notes from git history. Triggered on release tags following semver patterns (v..) to produce categorized changelog with breaking changes, features, fixes, and contributor attribution.
doctor
Diagnosticar y reparar problemas del framework Don Cheli, git y entorno. Usa cuando el usuario dice "doctor", "problemas del framework", "don cheli no funciona", "repair Don Cheli", "debug setup", "setup broken", "framework broken", "reparar entorno". Detecta y repara issues de configuración, git y dependencias…
repo-audit
Audit a codebase (local or remote GitHub/GitLab) against architecture principles and requirements, surfacing drift, risk, and missing decisions.
handoff
Export a Waybill Bundle by default, or import one when requested.
release-plan
A release-planning command for a software change. It documents the release scope, rollback plan, gradual or full rollout, and monitoring before waiting for human approval.