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/deploygit clone --depth 1 https://github.com/Pattyboi101/indiestackWhat 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.00331 |
| Opus 5 | $0.00000 | $0.00166 |
| Sonnet 5 | $0.00000 | $0.00066 |
| Haiku 4.5 | $0.00000 | $0.00033 |
Grade A, and why
deploy 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 2d 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 -sL -o /dev/null -w "%{http_code}" https://indiestack.fly.dev/ What it actually says
Deploy to Production
Working directory: ~/indiestack
1. Smoke test
cd ~/indiestack && python3 smoke_test.py
If any test fails (ignore 429 rate limit errors), stop and fix before deploying.
2. Check for uncommitted changes
cd ~/indiestack && git status --short
If there are uncommitted changes, ask the user if they want to commit first. Do not proceed until resolved.
3. Deploy
Run in background:
cd ~/indiestack && ~/.fly/bin/flyctl deploy --local-only
If local Docker fails, fall back to remote:
cd ~/indiestack && ~/.fly/bin/flyctl deploy --remote-only
4. Verify
After deploy completes:
curl -sL -o /dev/null -w "%{http_code}" https://indiestack.fly.dev/
Expect 200. If not, alert the user immediately.
5. Notify
bash ~/.claude/telegram.sh "Deployed to production"
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":"deployed to production","detail":"flyctl deploy --local-only"}'
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.
- 2d ago First seen · 58 lines · 0 tokens per session scan A 6b7c0a855114
deploy is a command published in the GitHub repository Pattyboi101/indiestack (3 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 331 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
git
Git operations with intelligent commit messages and workflow optimization.
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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
constitution
Create or update the project constitution from interactive or provided principle inputs.