test-command

A test command that demonstrates how command arguments, shell execution, and a referenced script are handled.

In plain words
What is it for?
Use it to test a first argument, pass all supplied arguments, run a greeting command, and reference an external script file.
Why use it?
It provides a small example for checking whether command conversion and parameter substitution work as expected.

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/beixiyo/ai-sync/test-command
Clone the repo
git clone --depth 1 https://github.com/beixiyo/ai-sync

Made for: Claude Code.

Per session 3 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 87 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.00003 $0.00087
Opus 5 $0.00002 $0.00044
Sonnet 5 $0.00001 $0.00017
Haiku 4.5 $0.00000 $0.00009

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

Security

Grade A, and why

test-command 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.

test-data/.claude/commands/test-command.md · 22 lines

What it actually says

测试命令

这是一个测试命令,用于验证命令转换功能。

参数

  • $1: 第一个参数
  • $2: 第二个参数
  • $ARGUMENTS: 所有参数

执行命令

!echo "Hello, $1!"

脚本引用

@script.sh

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. 2d ago First seen · 22 lines · 3 tokens per session scan A b223ddc74a8a

Subscribe to this mod's changes

test-command is a command published in the GitHub repository beixiyo/ai-sync (9 stars, last pushed 26d ago), licensed MIT. It adds 3 tokens to every session and 87 once invoked, about $0.0000 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-31.