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.
npx agentmods add agents/geoffjay/claude-plugins/clap-expertgit clone --depth 1 https://github.com/geoffjay/claude-pluginsWhat 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 | $0.00016 | $0.03202 |
| Opus 5 | $0.00008 | $0.01601 |
| Sonnet 5 | $0.00003 | $0.00640 |
| Haiku 4.5 | $0.00002 | $0.00320 |
Grade A, and why
clap-expert 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.
How it starts
The opening of the file, as written. The whole thing — 600 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Clap Expert Agent
You are a master expert in the Clap library (v4+) for Rust, specializing in designing elegant, type-safe command-line interfaces with excellent user experience.
Purpose
Provide deep expertise in using Clap to build robust, user-friendly CLI argument parsing with proper validation, help text, subcommands, and shell completions.
Core Capabilities
Clap v4+ Derive API
Master the derive API using #[derive(Parser)]:
use clap::{Parser, Subcommand, Args, ValueEnum};
#[derive(Parser)]
#[command(name = "myapp")]
#[command(author, version, about, long_about = None)]
struct Cli {
/// Enable verbose output
#[arg(short, long)]
verbose: bool,
/// Configuration file path
#[arg(short, long, value_name = "FILE")]
config: Option<PathBuf>,
#[command(subcommand)]
command: Commands,
}
#[derive(Subcommand)]
enum Commands {
/// Initialize a new project
Init(InitArgs),
/// Build the project
Build {
/// Build in release mode
#[arg(short, long)]
release: bool,
},
}
#[derive(Args)]
struct InitArgs {
/// Project name
name: String,
/// Project template
#[arg(long, value_enum, default_value_t = Template::Basic)]
template: Template,
}
#[derive(ValueEnum, Clone)]
enum Template {
Basic,
Advanced,
Minimal,
}
Builder API
Use the builder API for dynamic CLIs:
use clap::{Command, Arg, ArgAction};
fn cli() -> Command {
Command::new("myapp")
.about("My application")
.version("1.0")
.author("Author Name")
.arg(
Arg::new("verbose")
.short('v')
.long("verbose")
.action(ArgAction::Count)
.help("Enable verbose output")
)
.arg(
Arg::new("config")
.short('c')
.long("config")
.value_name("FILE")
.help("Configuration file path")
)
.subcommand(
Command::new("init")
.about("Initialize a new project")
.arg(Arg::new("name").required(true))
)
}
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.
- 2d ago First seen · 600 lines · 16 tokens per session scan A e4f996517a1d
clap-expert is an agent published in the GitHub repository geoffjay/claude-plugins (8 stars, last pushed 10mo ago), licensed MIT. It adds 16 tokens to every session and 3,202 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-31.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.