Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/travisjneuman/.claudenpx agentmods add commands/travisjneuman/.claude/runWrote 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/run)<a href="https://agentmods.dev/commands/travisjneuman/.claude/run"><img src="https://agentmods.dev/badge/commands/travisjneuman/.claude/run/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/run"><img src="https://agentmods.dev/badge/commands/travisjneuman/.claude/run.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.00019 | $0.00815 |
| Opus 5 | $0.00010 | $0.00407 |
| Sonnet 5 | $0.00004 | $0.00163 |
| Haiku 4.5 | $0.00002 | $0.00081 |
Grade A, and why
run 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 7d 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 — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Run Prompt with Auto-Archive
Execute one or more prompts from ./prompts/ directory, then automatically archive completed prompts to .archive/completed-prompts/ per CLAUDE.md session protocol.
When to Use This Command
Use /run when... |
Use /start-task when... |
|---|---|
You have pre-written prompts in ./prompts/ |
Describing a task naturally |
| Executing structured workflows | Need intelligent skill/agent routing |
| Running batch prompt sequences | Need complexity scoring (GSD vs Plan vs Direct) |
| Following established prompt files | Starting fresh work |
Note: Both approaches leverage the full skill ecosystem. /run is for pre-defined prompts; /start-task is for natural language routing.
Workflow
- Delegate to
/taches-cc-resources:run-promptto execute the prompt(s) - After successful completion, move prompt(s) from
./prompts/completed/to.archive/completed-prompts/ - Clean up any temporary directories
Implementation
Step 1: Execute the tache run-prompt command with all arguments passed through
/taches-cc-resources:run-prompt {{prompt_ids}}
Step 2: After completion, check if ./prompts/completed/ exists and move contents to archive
# If prompts/completed/ exists, move all files to archive and cleanup
if [ -d "./prompts/completed" ]; then
mkdir -p ".archive/completed-prompts"
mv ./prompts/completed/* .archive/completed-prompts/ 2>/dev/null || true
rmdir ./prompts/completed 2>/dev/null || true
fi
Step 3: Report final location of archived prompts
Notes
- This wrapper ensures CLAUDE.md compliance (prompts archived to
.archive/completed-prompts/) - Transparent to user - just use
/run [prompt-id]instead of/run-prompt - Supports all
/run-promptfeatures: single, parallel, sequential execution - Skills auto-activate based on prompt content (same as standard prompts)
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.
- 7d ago First seen · 108 lines · 19 tokens per session scan A 15d973fd3b44
run is a command published in the GitHub repository travisjneuman/.claude (97 stars, last pushed 5d ago), licensed MIT. It adds 19 tokens to every session and 815 once invoked, about $0.0001 per session on Opus 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
suggest-automation
A command that reviews recent Git commits and project instructions to find work patterns that happen repeatedly.
evolve
Cluster related instincts into skills, commands, or agents.
instinct-import
Import instincts from teammates, Skill Creator, or other sources.
instinct-export
Export instincts for sharing with teammates or other projects.
todo-add.template
This prompt was authored for Claude-style slash workflows. In Codex runtime, adapt tool calls as follows.
todo.template
This prompt was authored for Claude-style slash workflows. In Codex runtime, adapt tool calls as follows.