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/ruizrica/toolkit/setupgit clone --depth 1 https://github.com/ruizrica/toolkitWhat 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.00516 |
| Opus 5 | $0.00000 | $0.00258 |
| Sonnet 5 | $0.00000 | $0.00103 |
| Haiku 4.5 | $0.00000 | $0.00052 |
Grade A, and why
setup 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.
How it starts
The opening of the file, as written. The whole thing — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/setup
Bootstrap command for project initialization and memory-first context setup.
Usage
/setup
What it does
- Validates that the current directory is inside a git repository.
- Checks for
agent-memoryinPATHand fails fast with a clear message if missing. - Runs
agent-memory indexover the repository. - Creates project context files if missing:
claude.mdagents.md(reference only, no duplicated context content)
- Prints a compact post-setup summary and next
/worktreeusage steps.
Idempotent behavior
- If
claude.mdalready exists, the command skips re-writing it. - If
agents.mdalready exists, the command skips re-writing it. - Re-running
/setupis safe and should not overwrite existing files.
Constraints satisfied
- Memory tool primacy is explicitly documented in generated
claude.md. agent-memoryis required and checked before any file generation.- Both
claude.mdandagents.mdare created only when absent. - Git repository validation runs before any operations.
Generated claude.md includes
- Primary context guidance: use memory lookup before file reads.
- Memory query guidance using commands such as
agent-memory query,agent-memory recall, and related variants. - Stack and structure notes for this repository.
- Coding conventions and architectural notes.
Generated agents.md format
agents.md is intentionally minimal and references the context file only:
# Agent Configuration
See [claude.md](./claude.md) for project context, coding standards, and memory tool usage guidelines.
## Memory Tool Usage
This project uses the agent-memory CLI. Refer to claude.md for detailed instructions on context retrieval.
Example output
Running agent-memory index ...
agent-memory index complete.
Setup summary:
- agent-memory index: done
- claude context file: created (./claude.md)
- agents file: created (./agents.md)
Next steps:
1) Run /worktree to create your first isolated worktree (auto-generates branch)
2) Run /worktree again for additional worktrees, or use /worktree [path] [branch] for custom names
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 · 74 lines · 0 tokens per session scan A 806fb1917656
setup is a command published in the GitHub repository ruizrica/toolkit (5 stars, last pushed 17d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 516 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
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.
constitution
Create or update the project constitution from interactive or provided principle inputs.
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.