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/backup-config)<a href="https://agentmods.dev/commands/travisjneuman/.claude/backup-config"><img src="https://agentmods.dev/badge/commands/travisjneuman/.claude/backup-config/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/backup-config"><img src="https://agentmods.dev/badge/commands/travisjneuman/.claude/backup-config.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.00005 | $0.01081 |
| Opus 5 | $0.00003 | $0.00541 |
| Sonnet 5 | $0.00001 | $0.00216 |
| Haiku 4.5 | $0.00001 | $0.00108 |
Grade B, and why
backup-config scanned grade B with 1 finding 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 9d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
cp ~/.claude/settings.json "$BACKUP_DIR/" How it starts
The opening of the file, as written. The whole thing — 182 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Backup Config
Backup and restore Claude Code configuration files.
Usage
/backup-config [action] [name]
Platform Compatibility
| Platform | Status | Notes |
|---|---|---|
| Windows | ✅ | Requires Git Bash (included with Git for Windows) |
| macOS | ✅ | Works with bash/zsh |
| Linux | ✅ | Works with bash |
All commands use POSIX utilities (mkdir, cp, ls, date).
Arguments
| Argument | Default | Options |
|---|---|---|
action |
create |
create, list, restore |
name |
auto-[timestamp] |
Custom backup name |
Backup Location
~/.claude/.backups/
Actions
create (default)
Create a new backup:
# Create backup directory
mkdir -p ~/.claude/.backups
# Generate backup name
BACKUP_NAME="${name:-backup-$(date +%Y%m%d-%H%M%S)}"
BACKUP_DIR=~/.claude/.backups/$BACKUP_NAME
mkdir -p "$BACKUP_DIR"
# Backup critical files
cp ~/.claude/settings.json "$BACKUP_DIR/"
cp ~/.claude/CLAUDE.md "$BACKUP_DIR/"
cp ~/.claude/.mcp.json "$BACKUP_DIR/" 2>/dev/null || true
# Create manifest
echo "Backup: $BACKUP_NAME" > "$BACKUP_DIR/manifest.txt"
echo "Created: $(date)" >> "$BACKUP_DIR/manifest.txt"
echo "Files:" >> "$BACKUP_DIR/manifest.txt"
ls -la "$BACKUP_DIR" >> "$BACKUP_DIR/manifest.txt"
echo "Backup created: $BACKUP_DIR"
list
List available backups:
echo "Available backups:"
echo ""
ls -lt ~/.claude/.backups/ | head -20
echo ""
echo "Total: $(ls ~/.claude/.backups/ | wc -l) backups"
restore
Restore from backup:
BACKUP_DIR=~/.claude/.backups/$name
if [ ! -d "$BACKUP_DIR" ]; then
echo "Backup not found: $name"
echo "Use '/backup-config list' to see available backups"
exit 1
fi
# Create safety backup first
mkdir -p ~/.claude/.backups/pre-restore-$(date +%Y%m%d-%H%M%S)
cp ~/.claude/settings.json ~/.claude/.backups/pre-restore-*/
# Restore files
cp "$BACKUP_DIR/settings.json" ~/.claude/
cp "$BACKUP_DIR/CLAUDE.md" ~/.claude/ 2>/dev/null || true
cp "$BACKUP_DIR/.mcp.json" ~/.claude/ 2>/dev/null || true
echo "Restored from: $BACKUP_DIR"
echo "Note: Restart Claude Code for changes to take effect"
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.
- 9d ago First seen · 182 lines · 5 tokens per session scan B 75c5fc658804
backup-config is a command published in the GitHub repository travisjneuman/.claude (97 stars, last pushed 7d ago), licensed MIT. It adds 5 tokens to every session and 1,081 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other commands, from other repositories
evolve
Cluster related instincts into skills, commands, or agents.
suggest-automation
A command that reviews recent Git commits and project instructions to find work patterns that happen repeatedly.
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.