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/try-works/recursive-mode/recursive-lockgit clone --depth 1 https://github.com/try-works/recursive-modeWhat 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.00325 |
| Opus 5 | $0.00000 | $0.00162 |
| Sonnet 5 | $0.00000 | $0.00065 |
| Haiku 4.5 | $0.00000 | $0.00032 |
Grade A, and why
recursive-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 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.
What it actually says
recursive-lock (prompt template)
Paste this into chat if your agent does not support custom slash commands.
Usage Pattern
Lock recursive artifact: [run-id] [artifact]
Script (Recommended)
python "<SKILL_DIR>/scripts/recursive-lock.py" --repo-root . --run-id "<run-id>" --artifact "<artifact>.md"
python3 "<SKILL_DIR>/scripts/recursive-lock.py" --repo-root . --run-id "<run-id>" --artifact "<artifact>.md"
powershell -ExecutionPolicy Bypass -File "<SKILL_DIR>/scripts/recursive-lock.ps1" -RepoRoot . -RunId "<run-id>" -Artifact "<artifact>.md"
pwsh -NoProfile -File "<SKILL_DIR>/scripts/recursive-lock.ps1" -RepoRoot . -RunId "<run-id>" -Artifact "<artifact>.md"
What It Does
- Validates the target artifact before locking
- Refuses to lock if required gates or lint-critical structure are invalid
- Refuses to lock strict Phase 3 artifacts that are missing RED or GREEN evidence
- Refuses to lock pragmatic Phase 3 artifacts that are missing an explicit exception rationale plus compensating evidence
- Refuses to lock Phase 5 artifacts whose declared QA mode is missing the required sign-off or execution evidence
- Sets
Status: LOCKED - Writes
LockedAt - Computes canonical
LockHash
Example
Lock recursive artifact: <run-id> 04-test-summary.md
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.
- 2d ago First seen · 37 lines · 0 tokens per session scan A 45378887379c
recursive-lock is a command published in the GitHub repository try-works/recursive-mode (129 stars, last pushed 1mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 325 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-30.
Other commands, from other repositories
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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.