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/intellegix/intellegix-code-agent-toolkit/handoffgit clone --depth 1 https://github.com/intellegix/intellegix-code-agent-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.00960 |
| Opus 5 | $0.00000 | $0.00480 |
| Sonnet 5 | $0.00000 | $0.00192 |
| Haiku 4.5 | $0.00000 | $0.00096 |
Grade A, and why
handoff 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 — 160 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Handoff
Create a comprehensive handoff document for the current work session.
Task Context: $ARGUMENTS
Handoff Process
Step 1: Gather Session Information
- Identify all files modified in this session
- Summarize work completed
- Note any blockers or issues encountered
- List decisions made and their rationale
Step 2: Document Current State
-
Run relevant status commands:
git status git diff --stat git log --oneline -5 -
Check test status:
npm test -- --passWithNoTests 2>/dev/null || pytest --co -q 2>/dev/null || echo "No test runner detected"
Step 3: Create Handoff Document
Generate file at: .claude/handoffs/[YYYY-MM-DD]-[HH-MM]-[task-slug].md
Handoff Document Template
# Agent Handoff: [Task Name]
**Generated**: [Current Timestamp]
**Session Duration**: [Approximate time spent]
**Agent**: Claude Code
---
## Current Status
| Metric | Value |
|--------|-------|
| Overall Progress | X% complete |
| Phase | Planning / Implementation / Testing / Review |
| Blocked | Yes/No |
| Tests Passing | Yes/No/Partial |
## Work Completed This Session
### Tasks Finished
- [x] [Completed task 1]
- [x] [Completed task 2]
### Partial Progress
- [ ] [In-progress task] - [Current state, what's left]
## Files Modified
| File | Change Type | Description |
|------|-------------|-------------|
| `src/path/file.ts` | Created | New component for X |
| `src/path/other.ts` | Modified | Added Y method |
| `tests/path/test.ts` | Created | Tests for X |
## Key Decisions Made
### Decision 1: [Title]
- **Context**: [Why this decision was needed]
- **Choice**: [What was decided]
- **Rationale**: [Why this approach]
- **Alternatives Rejected**: [What else was considered]
## What Worked Well
- [Successful approach 1]
- [Successful approach 2]
## What Didn't Work
- **Attempted**: [Approach that failed]
- **Problem**: [Why it didn't work]
- **Resolution**: [What was done instead]
## Blockers & Dependencies
### Active Blockers
- **Blocker**: [Description]
- **Impact**: [What it's blocking]
- **Needed**: [What's needed to unblock]
- **Owner**: [Who can resolve this]
### External Dependencies
- [Dependency on external team/service]
## Context for Next Agent
### Current State of Codebase
[Brief description of relevant code state - what's implemented, what's scaffolded, what's missing]
### Important Files to Review First
1. `path/to/file1.ts` - [Why it's important]
2. `path/to/file2.ts` - [Why it's important]
### Environment Setup
```bash
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 · 160 lines · 0 tokens per session scan A 995cf8eb76c7
handoff is a command published in the GitHub repository intellegix/intellegix-code-agent-toolkit (57 stars, last pushed 8d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 960 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
README
Git workflow and quality assurance commands for the claude-skills repository.
agentlas-cloud
Staff a task only from the signed-in owner's Agent Cloud agents.
dispatcher
Pick the next-best repo to work on across the portfolio — rank free repos, recommend one, claim its lease atomically, and route to the entry command.
tldr
Re-apply TLDR rules for this turn (verdict first, no filler).
execute
Interactive workflow for workspace isolation, pane-delegated implementation, testing, review, and cleanup.
me-figure-discussion
Write or review thermal-fluid figure discussion with observation, physical mechanism, comparison, uncertainty, and claim limits.