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/sergei-aronsen/claude-code-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/sergei-aronsen/claude-code-toolkit/pack)<a href="https://agentmods.dev/commands/sergei-aronsen/claude-code-toolkit/pack"><img src="https://agentmods.dev/badge/commands/sergei-aronsen/claude-code-toolkit/pack/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/sergei-aronsen/claude-code-toolkit/pack"><img src="https://agentmods.dev/badge/commands/sergei-aronsen/claude-code-toolkit/pack.svg" alt="Reviewed on agentmods" width="80" 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.00000 | $0.01216 |
| Opus 5.5 | $0.00000 | $0.00486 |
| Sonnet 5.5 | $0.00000 | $0.00243 |
| Haiku 4.5 | $0.00000 | $0.00122 |
Grade A, and why
pack 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 1mo 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 — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/pack — Repository Pack for AI Context
Purpose
Pack the current repository (or a remote one) into a single AI-friendly file
via Repomix. The output lands in
.claude/scratchpad/ and is ready to attach to any LLM — ChatGPT, Claude
web, Gemini, a teammate, an issue thread.
This is the manual counterpart to /council's automatic pack
augmentation. Use it when you want a snapshot outside the Council flow.
Usage
/pack # local repo, defaults (XML, compressed)
/pack --remote yamadashy/repomix # remote repo by shorthand
/pack --remote https://github.com/x/y # full URL
/pack --include "src/**,*.md" # filter
/pack --format markdown # md instead of xml
/pack --format json # json
/pack --to clipboard # copy to system clipboard (pbcopy/xclip)
/pack --no-compress # skip tree-sitter signature extraction
/pack --include-diffs --include-logs # add git context
Examples:
/pack— pack this repo, write.claude/scratchpad/pack-<timestamp>.xml/pack --remote nestjs/nest --include "packages/core/**"— pack a subset of an upstream repo/pack --to clipboard --format md— quick markdown handoff for ChatGPT/pack --include-diffs --include-logs— pack with full git history (last 50 commits)
When to Use
| Situation | Use /pack |
|---|---|
| Architectural review across 50+ files | yes |
| Handoff to another LLM (ChatGPT, web Claude) | yes |
| Attach codebase context to an issue / PR comment | yes |
| Snapshot for a teammate working in a different stack | yes |
| Look at the shape of an upstream library | yes (--remote) |
| Find a single function | no — use /find-function or Grep |
| Read one file | no — use Read |
| Open-ended exploration of 2-3 files | no — use Explore agent |
| Pre-Council context | no — Council does this automatically via --pack |
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.
- 1mo ago First seen · 135 lines · 0 tokens per session scan A 12ca30a90814
pack is a command published in the GitHub repository sergei-aronsen/claude-code-toolkit (5 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,216 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
minutes-ideas
Surface recent voice memos and ideas captured from any device. Use when the user asks "what ideas did I have?", "what were my recent memos?", "what did I record while walking?", or wants to recall a captured thought.
learn
Force claude-smart to extract learnings from this session now.
memory-store
Store an insight, decision, or pattern to memory.
analyze-context
USE WHEN you want to analyze project context before starting work on a task. Calls context + recall, then synthesizes goals, decisions, gotchas, and relevant memories into a pre-task brief.
cc-memory
Configure persistent memory that survives across sessions using a layered approach: split rule files for always-loaded context, auto-memory for organic learning, and optional MCP-backed long-term memory for large codebases.
lians-recall
Recall current (non-stale) facts from Lians memory, optionally as-of a past date.