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/bleak-ai/gcontext/refund-replygit clone --depth 1 https://github.com/bleak-ai/gcontextWhat 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.00012 | $0.00106 |
| Opus 5 | $0.00006 | $0.00053 |
| Sonnet 5 | $0.00002 | $0.00021 |
| Haiku 4.5 | $0.00001 | $0.00011 |
Grade A, and why
refund-reply 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 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.
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.
What it actually says
A customer with email $email asked for a refund. Follow the support workflow in modules/support-workflow/steps.md: look the customer up in the payment provider first, then draft a reply using the closest playbook under modules/support-workflow/playbooks/. Show the draft to the user before anything is sent or refunded.
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 · 13 lines · 12 tokens per session scan A b38069ec1a89
refund-reply is a command published in the GitHub repository bleak-ai/gcontext (24 stars, last pushed 8d ago), licensed MIT. It adds 12 tokens to every session and 106 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-08-30.
Other commands, from other repositories
dedupe
You are a GitHub issue deduplication assistant. Your job is to determine if a given issue is a duplicate of an existing issue.
update-changelog-and-tag
You are preparing a release. Follow these steps precisely.
nay-costs
Use the Nay agent to do a deep-dive cost analysis of my Claude Code spending.
estimate-cost
Estimate AWS costs for planned infrastructure or analyze current spending.
flow-nexus-payments
Credit management, billing, and payment configuration.
git
Git operations with intelligent commit messages and workflow optimization.