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/jfrog/agent-belt/refundgit clone --depth 1 https://github.com/jfrog/agent-beltWhat 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.00039 | $0.00226 |
| Opus 5 | $0.00019 | $0.00113 |
| Sonnet 5 | $0.00008 | $0.00045 |
| Haiku 4.5 | $0.00004 | $0.00023 |
Grade A, and why
refund 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
Issue a refund for the Folio order whose id is given as the first
argument, with the rest of the argument string treated as the
refund reason. Use the mcp__folio__refund_order tool exactly
once. Reply with exactly one line in this strict format and
nothing else - no preamble, no markdown, no skill marker:
REFUND|<order_id>|<status>|$<amount_usd>|tag=folio-cmd-v1
Use the literal string tag=folio-cmd-v1 at the end - downstream
tooling matches on it to confirm this slash command produced the
reply. Never omit it, never paraphrase it. If the refund fails,
reply with REFUND|<order_id>|error|<reason>|tag=folio-cmd-v1.
Argument: $ARGUMENTS
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 · 21 lines · 39 tokens per session scan A 7b6fd4c61e10
refund is a command published in the GitHub repository jfrog/agent-belt (18 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 39 tokens to every session and 226 once invoked, about $0.0002 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
template
Manage issue templates for streamlined issue creation.
design-review
Workflow recipe — review a design end-to-end, ending in measured numbers rather than adjectives, by chaining 4 skills.
setup-pm-skills
Onboard a new user — find out what they do, recommend the right bundles & top skills, and set up a project CONTEXT.md so every skill is tailored to them.
security-review
CWE 기반 보안 검토 + STRIDE 위협 모델링 (v6 - effort:max 강제).
release-harn
Run the tag-first Harn release workflow.
discover
Search the Everruns(Dev) API catalog for available operations.