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/travisjneuman/.claudeWrote 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/travisjneuman/.claude/pull-repos)<a href="https://agentmods.dev/commands/travisjneuman/.claude/pull-repos"><img src="https://agentmods.dev/badge/commands/travisjneuman/.claude/pull-repos/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/travisjneuman/.claude/pull-repos"><img src="https://agentmods.dev/badge/commands/travisjneuman/.claude/pull-repos.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.00013 | $0.01291 |
| Opus 5.5 | $0.00005 | $0.00516 |
| Sonnet 5.5 | $0.00003 | $0.00258 |
| Haiku 4.5 | $0.00001 | $0.00129 |
Grade A, and why
pull-repos 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 12d 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 — 177 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pull Repos
Pull the parent repo, ignored marketplace clones, and configured project directories with a single command.
Usage
/pull-repos [action]
What It Does
- Pulls parent repo (
~/.claude- travisjneuman/.claude) - Pulls all manifest marketplace clones (read-only repos in
plugins/marketplaces/) - Pulls custom project directories recursively (if configured)
- Reports detached HEAD repos and skips them (never switches branches)
- Enforces no_push on marketplace clones and non-Travis-owned custom repos
Arguments
| Argument | Default | Options |
|---|---|---|
action |
pull |
pull, status |
Actions
pull (default)
Pull all repos and enforce no_push:
~/.claude/_pull-all-repos.sh
status
Check status without pulling:
~/.claude/_pull-all-repos.sh --status
Platform Compatibility
| Platform | Status | Notes |
|---|---|---|
| Windows | ✅ | Requires Git Bash (included with Git for Windows) |
| macOS | ✅ | Works with bash/zsh |
| Linux | ✅ | Works with bash (including Arch) |
What Gets Pulled
| # | Repository | Type | Push Access |
|---|---|---|---|
| 1 | .claude (travisjneuman/.claude) |
Parent | ✅ Push enabled |
| 2+ | .gitmodules marketplace entries |
Clones | ❌ no_push enforced |
| ... | Custom project directories | Mixed | ✅ Travis-owned only |
Features
- ✅ Auto-discovers marketplace entries - Add new manifest entries and they're automatically included
- ✅ Custom project directories - Add your own project folders (see below)
- ✅ Recursive project discovery - Finds nested repos such as frontend/backend checkouts inside a platform folder
- ✅ Reports detached HEAD - Detached repos are skipped and reported, never switched
- ✅ Detects correct branch - main/master/development per repo
- ✅ Enforces no_push - Marketplace clones and non-Travis-owned custom repos cannot push
- ✅ Safe - Dirty repos are skipped; pulls are fast-forward only; no merge/rebase/reset
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.
- 12d ago Changed 807164650151
- 24d ago Changed 62102fdd5926
- 25d ago Changed d1d88ed5ecc5
- 26d ago Changed · +1 lines b0a3a567da11
- 1mo ago First seen · 176 lines · 13 tokens per session scan A 0f24a8c64656
pull-repos is a command published in the GitHub repository travisjneuman/.claude (106 stars, last pushed yesterday), licensed MIT. It adds 13 tokens to every session and 1,291 once invoked, about $0.0001 per session on Opus 5.5. 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-09-03.
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.
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.
speckit.bug.fix
Apply the remediation from a bug assessment and record what was changed.