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/ivan-magda/claude-code-plugin-templateWrote 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/ivan-magda/claude-code-plugin-template/hello)<a href="https://agentmods.dev/commands/ivan-magda/claude-code-plugin-template/hello"><img src="https://agentmods.dev/badge/commands/ivan-magda/claude-code-plugin-template/hello/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/ivan-magda/claude-code-plugin-template/hello"><img src="https://agentmods.dev/badge/commands/ivan-magda/claude-code-plugin-template/hello.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.00010 | $0.00288 |
| Opus 5.5 | $0.00004 | $0.00115 |
| Sonnet 5.5 | $0.00002 | $0.00058 |
| Haiku 4.5 | $0.00001 | $0.00029 |
Grade A, and why
hello 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 1mo 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
Hello Command
Greet the user warmly and enthusiastically. This is a demonstration command from the Hello World plugin that shows how Claude Code plugins work.
Instructions
- If the user provided a name in
$ARGUMENTS, greet them personally (e.g., "Hello, Alice! 👋") - If no name was provided, use a friendly generic greeting (e.g., "Hello, there! 👋")
- After the greeting, briefly explain that this is an example plugin demonstrating Claude Code's plugin system
- Mention that plugins can provide custom commands, agents, hooks, Skills, and MCP servers
- Keep the tone warm, friendly, and encouraging
Example responses
With name (/hello World):
Hello, World! 👋
This is a sample command from the Hello World plugin, demonstrating how Claude Code plugins work. Plugins can add custom commands, agents, hooks, Skills, and MCP servers to extend Claude Code's capabilities!
Without name (/hello):
Hello, there! 👋
This is a sample command from the Hello World plugin, demonstrating how Claude Code plugins work. Plugins can add custom commands, agents, hooks, Skills, and MCP servers to extend Claude Code's capabilities!
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.
- 1mo ago First seen · 33 lines · 10 tokens per session scan A 42c6976998f4
hello is a command published in the GitHub repository ivan-magda/claude-code-plugin-template (70 stars, last pushed 3mo ago), licensed MIT. It adds 10 tokens to every session and 288 once invoked, about $0.0000 per session on Opus 5.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
atomic-help
Route a lost user to the right atomic verb, skill, agent, or binary subcommand. Bare invocation reads git state and recommends one next step. Topic keyword or freeform intent → focused pointer. tour → guided walkthrough of the system. Help router, not duplicated docs.
atomic-plan
Write a design doc (concepts, business rules, approaches) and a checkpoint-table spec (contract) for non-trivial work; inline spec only for trivial. Gauges triviality; loops spec authoring with subagents. Human-facing artifact, Mermaid diagrams allowed.
follow-up
Review and act on pending reminders. Bare invocation shows all reminders as an indexed list; cron-fired invocation (/follow-up due ) surfaces the specific reminder and waits for a response; /follow-up review lists stale project follow-up entries for per-item disposition (extend/close/promote/skip). Transport-aware…
documentation
Bootstrap and maintain project documentation surfaces. Two modes: bootstrap (discover doc files, index them in CLAUDE.md) and authoring (scan for unindexed docs, match diff against indexed surfaces, walk stale/incomplete/missing items with Yes/Later/Remind/Skip).
watch-ci
Spawn a background Haiku-backed subagent to watch CI for the current branch (or specified target). Provider-agnostic — the subagent inspects project signals to identify the CI system (GitHub Actions, GitLab CI, CircleCI, etc.) and picks the right CLI. Returns immediately; reports back when CI reaches a terminal state.
report-issue
Open a atomic GitHub issue via gh. Bug report or feature request — auto-detect from user's description.