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/handbookgit clone --depth 1 https://github.com/ruizrica/toolkitWrote 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/ruizrica/toolkit/handbook)<a href="https://agentmods.dev/commands/ruizrica/toolkit/handbook"><img src="https://agentmods.dev/badge/commands/ruizrica/toolkit/handbook.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 | $0.00000 | $0.00694 |
| Opus 5 | $0.00000 | $0.00347 |
| Sonnet 5 | $0.00000 | $0.00139 |
| Haiku 4.5 | $0.00000 | $0.00069 |
Grade A, and why
handbook 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 4d 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 — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/handbook
Generate a comprehensive, AI-optimized project handbook. This command analyzes your codebase and creates structured documentation designed to help AI assistants understand and work with your project.
Usage
/handbook [--path PROJECT_PATH] [--output FILENAME] [--verbose]
Arguments
| Argument | Required | Default | Description |
|---|---|---|---|
--path |
No | . |
Path to the project to analyze |
--output |
No | HANDBOOK.md |
Output filename |
--verbose |
No | false | Show detailed analysis progress |
Output Structure
The handbook is organized into four layers:
Layer 1: System Overview
- Purpose - What the project does and why it exists
- Tech Stack - Languages, frameworks, and tools used
- Architecture - High-level system design
Layer 2: Module Map
- Core Modules - Primary functionality areas
- Data Layer - Database, storage, and data flow
- Utilities - Helper functions and shared code
Layer 3: Integration Guide
- APIs - External and internal API documentation
- Interfaces - How components communicate
- Configuration - Settings and environment variables
Layer 4: Extension Points
- Design Patterns - Patterns used throughout the codebase
- Customization Areas - Where and how to extend functionality
Examples
# Generate handbook for current project
/handbook
# Analyze a specific project
/handbook --path ./my-project
# Custom output file
/handbook --output PROJECT_DOCS.md
# Full options
/handbook --path ./api --output API_HANDBOOK.md --verbose
Sample Output
# Project Handbook: MyApp
## Layer 1: System Overview
### Purpose
MyApp is a task management application that enables teams to...
### Tech Stack
- **Frontend**: React 18, TypeScript, Tailwind CSS
- **Backend**: Node.js, Express, PostgreSQL
- **Infrastructure**: Docker, AWS Lambda
### Architecture
The application follows a microservices architecture with...
## Layer 2: Module Map
### Core Modules
- `src/auth/` - Authentication and authorization
- `src/tasks/` - Task CRUD operations
- `src/teams/` - Team management
...
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.
- 4d ago First seen · 115 lines · 0 tokens per session scan A 4f32bd8eb7ab
handbook is a command published in the GitHub repository ruizrica/toolkit (5 stars, last pushed 19d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 694 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
git
Git operations with intelligent commit messages and workflow optimization.
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.