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.
git clone --depth 1 https://github.com/lyarwood/kubevirt-ai-helpersWrote 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.
[](https://agentmods.dev/commands/lyarwood/kubevirt-ai-helpers/echo)<a href="https://agentmods.dev/commands/lyarwood/kubevirt-ai-helpers/echo"><img src="https://agentmods.dev/badge/commands/lyarwood/kubevirt-ai-helpers/echo/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/lyarwood/kubevirt-ai-helpers/echo"><img src="https://agentmods.dev/badge/commands/lyarwood/kubevirt-ai-helpers/echo.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00004 | $0.00435 |
| Opus 5 | $0.00002 | $0.00217 |
| Sonnet 5 | $0.00001 | $0.00087 |
| Haiku 4.5 | $0.00000 | $0.00044 |
Grade A, and why
echo 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 10d 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.
This is a copy
100% identical to echo — 4 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Name
hello-world:echo
Synopsis
/hello-world:echo [name]
Description
The hello-world:echo command prints a greeting message to the console. By default, it prints "Hello world", but when provided with a name argument hello-world:echo $1, it prints "Hello ${1}". This command serves as a basic example of a Claude Code plugin implementation, demonstrating the minimal structure required for a functional plugin command.
It provides a reference implementation for plugin developers. It demonstrates:
- Basic command structure
- Shell command execution within a plugin
- Handling arguments
- Minimal configuration requirements
The spec sections is inspired by https://man7.org/linux/man-pages/man7/man-pages.7.html#top_of_page
Implementation
- The command executes a simple bash
echostatement - Accepts an optional name argument (
$1) - If
$1is provided, outputs "Hello $1" - If no argument is provided, outputs "Hello world"
- Output is sent directly to standard output
- The command is stateless and has no side effects
Implementation logic:
if [ -n "$1" ]; then
echo "Hello $1"
else
echo "Hello world"
fi
Return Value
- Claude agent text: "Hello world" (default) or "Hello $1" (when name is provided)
Examples
-
Basic usage (no arguments):
/hello-world:echoOutput:
Hello world -
With a name argument:
/hello-world:echo AliceOutput:
Hello Alice -
With multiple words as name:
/hello-world:echo "John Doe"Output:
Hello John Doe
Arguments:
- $1: The name to be printed "Hello ${1}"
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.
- 10d ago First seen · 76 lines · 4 tokens per session scan A aea35b24016d
echo is a command published in the GitHub repository lyarwood/kubevirt-ai-helpers (2 stars, last pushed 7d ago), licensed Apache-2.0. It adds 4 tokens to every session and 435 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to echo, differing in 4 lines, and is treated as a copy.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.