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/pattyboi101/indiestack/backupgit clone --depth 1 https://github.com/Pattyboi101/indiestackWrote 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/pattyboi101/indiestack/backup)<a href="https://agentmods.dev/commands/pattyboi101/indiestack/backup"><img src="https://agentmods.dev/badge/commands/pattyboi101/indiestack/backup.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.00389 |
| Opus 5 | $0.00000 | $0.00195 |
| Sonnet 5 | $0.00000 | $0.00078 |
| Haiku 4.5 | $0.00000 | $0.00039 |
Grade A, and why
backup scanned grade A 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 4d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s -X POST -H "X-Hub-Secret: $HUB_SECRET" -H "Content-Type: application/json" \ What it actually says
Backup Production Database
Working directory: ~/indiestack
1. Create backup directory
mkdir -p ~/indiestack/backups
2. Download database from Fly
cd ~/indiestack && ~/.fly/bin/flyctl ssh console -C "cat /data/indiestack.db" > backups/indiestack-$(date +%Y%m%d-%H%M%S).db
3. Verify backup
LATEST=$(ls -t ~/indiestack/backups/*.db | head -1)
SIZE=$(du -h "$LATEST" | cut -f1)
echo "Backup: $LATEST ($SIZE)"
sqlite3 "$LATEST" "SELECT COUNT(*) || ' tools' FROM tools; SELECT COUNT(*) || ' makers' FROM makers; SELECT COUNT(*) || ' categories' FROM categories;"
If the file is 0 bytes or sqlite3 fails, the backup is bad — alert the user.
4. Clean old backups (keep last 5)
cd ~/indiestack/backups && ls -t *.db | tail -n +6 | xargs rm -f 2>/dev/null
5. Report
Tell the user:
- Backup filename and size
- Tool/maker/category counts as sanity check
- Number of backups stored locally
- Reminder: these are local-only backups
6. Log to hub (best effort)
Skip if HUB_URL is not set.
curl -s -X POST -H "X-Hub-Secret: $HUB_SECRET" -H "Content-Type: application/json" \
"$HUB_URL/activity" -d '{"actor":"patrick","action":"backed up database","detail":"SIZE"}'
Replace SIZE with the backup file size.
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.
- 4d ago First seen · 52 lines · 0 tokens per session scan A f1785bc788f3
backup is a command published in the GitHub repository Pattyboi101/indiestack (4 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 389 tokens. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
review-renovate
Review and merge renovate PRs with automerge configuration updates.
monitor-ci
Monitors pull request CI checks until they are resolved (pass or fail).
plan-regression-tests
Plan regression tests for existing code with it.skip statements.
config
Command "config" from sdebruyn/fabric-dw-mcp-cli, covering configuration & defaults, http retry budget, sql retry budget, mcp workspace allowlist {#mcp-workspace-allowlist} and mcp server log level.
database-setup
Use when a project needs to store data and has no database yet. Setting up Supabase, creating tables, writing queries, and connecting them to the frontend. Written for designers.
ingest
Manually add knowledge to the Weaviate store.