lookup

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

A command that looks up a Folio customer by ID and reports how many orders they have.

In plain words
What is it for?
Use it when a Folio customer ID is provided and you need their name, order count, or an unknown-customer result.
Why use it?
It gathers the customer and order information in the exact one-line format needed by another system.

Command for Claude Code

Part of the folio-ops plugin — 1 skill, 1 command shipped together

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/lookup
Clone the repo
git clone --depth 1 https://github.com/jfrog/agent-belt

Made for: Claude Code.

Or install folio-ops, the plugin that ships this one along with the rest of its 1 skill, 1 command.

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 lookup

README.md
[![agentmods](https://agentmods.dev/badge/commands/jfrog/agent-belt/lookup.svg)](https://agentmods.dev/commands/jfrog/agent-belt/lookup)
Your own site
<a href="https://agentmods.dev/commands/jfrog/agent-belt/lookup"><img src="https://agentmods.dev/badge/commands/jfrog/agent-belt/lookup.svg" alt="Measured on agentmods" height="20"></a>
Per session 27 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 205 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.00027 $0.00205
Opus 5 $0.00014 $0.00102
Sonnet 5 $0.00005 $0.00041
Haiku 4.5 $0.00003 $0.00020

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

Security

Grade A, and why

lookup 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/folio/.claude/plugins/folio-ops/commands/lookup.md · 21 lines

What it actually says

Look up the Folio customer whose id is provided as the argument. Use mcp__folio__get_customer to fetch the customer, then mcp__folio__list_customer_orders to fetch their orders. Reply with exactly one line in this strict format and nothing else - no preamble, no markdown, no skill marker:

LOOKUP|<customer_id>|<name>|orders=<count>|tag=folio-ops-v1

The literal tag=folio-ops-v1 is what downstream tooling matches on to confirm this plugin's command produced the reply - never omit it, never paraphrase it. If the customer is unknown reply with LOOKUP|<customer_id>|error|unknown|tag=folio-ops-v1.

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 · 21 lines · 27 tokens per session scan A 9eaa1212f632

Subscribe to this mod's changes

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