check-order

check-order is a command for Claude Code from jfrog/agent-belt. It costs 29 tokens per session (152 once invoked), scanned A, original, Apache-2.0.

A command that looks up one order by its ID through an order database and returns a fixed, pipe-separated line.

In plain words
What is it for?
Use it to retrieve an order’s customer, status, and tracking information.
Why use it?
It gives downstream programs a predictable format for reading order details.

Command for Claude Code

Install

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.

agentmods
npx agentmods add commands/jfrog/agent-belt/check-order
Clone the repo
git clone --depth 1 https://github.com/jfrog/agent-belt

Made for: Claude Code.

Wrote 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.

agentmods badge for check-order

README.md
[![agentmods](https://agentmods.dev/badge/commands/jfrog/agent-belt/check-order.svg)](https://agentmods.dev/commands/jfrog/agent-belt/check-order)
Your own site
<a href="https://agentmods.dev/commands/jfrog/agent-belt/check-order"><img src="https://agentmods.dev/badge/commands/jfrog/agent-belt/check-order.svg" alt="Measured on agentmods" height="20"></a>
Per session 29 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 152 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00029 $0.00152
Opus 5 $0.00015 $0.00076
Sonnet 5 $0.00006 $0.00030
Haiku 4.5 $0.00003 $0.00015

Measured 4d ago against content hash 4fe259e871f3, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

check-order 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 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.

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.

examples/fixtures/programmatic-setup/.claude/commands/check-order.md · 18 lines

What it actually says

Look up the order whose id is provided as the argument. Use the mcp__orders_db__get_order tool. Reply with exactly one line in this strict pipe-separated format and nothing else - no preamble, no markdown, no trailing skill marker:

ORDER|<id>|<customer>|<status>|<tracking>

Use the value none for fields that are null. If no order id was provided or the lookup failed, reply with ORDER|error|<reason>.

Argument: $ARGUMENTS

Changes

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.

  1. 4d ago First seen · 18 lines · 29 tokens per session scan A 4fe259e871f3

Subscribe to this mod's changes

check-order is a command published in the GitHub repository jfrog/agent-belt (18 stars, last pushed yesterday), licensed Apache-2.0. It adds 29 tokens to every session and 152 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.