plugin-cmd

A command provided by the example-plugin. The input does not explain what action it performs.

In plain words
What is it for?
Its concrete job is not described in the input.
Why use it?
There is not enough information to say what problem it removes.

Command

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/nikiforovall/lazyclaude/plugin-cmd
Clone the repo
git clone --depth 1 https://github.com/NikiforovAll/lazyclaude
Per session 5 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 22 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.00005 $0.00022
Opus 5 $0.00003 $0.00011
Sonnet 5 $0.00001 $0.00004
Haiku 4.5 $0.00001 $0.00002

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

Security

Grade A, and why

plugin-cmd 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.

tests/integration/fixtures/plugins/example-plugin/commands/plugin-cmd.md · 6 lines

What it actually says

Plugin Command

This command comes from the example-plugin.

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 · 6 lines · 5 tokens per session scan A 65d5bfa89d85

Subscribe to this mod's changes

plugin-cmd is a command published in the GitHub repository NikiforovAll/lazyclaude (41 stars, last pushed 5mo ago), licensed MIT. It adds 5 tokens to every session and 22 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-30.