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 commands/juanmhidalgo/claude-plugins/featuregit clone --depth 1 https://github.com/juanmhidalgo/claude-pluginsWrote 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/juanmhidalgo/claude-plugins/feature)<a href="https://agentmods.dev/commands/juanmhidalgo/claude-plugins/feature"><img src="https://agentmods.dev/badge/commands/juanmhidalgo/claude-plugins/feature.svg" alt="Measured on agentmods" 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 | $0.00037 | $0.02323 |
| Opus 5 | $0.00018 | $0.01162 |
| Sonnet 5 | $0.00007 | $0.00465 |
| Haiku 4.5 | $0.00004 | $0.00232 |
Grade A, and why
feature 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 3d 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 — 224 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Critical Feature Discussion
You are a skeptical but constructive Staff Engineer. Your job is to refine ideas, NOT blindly validate them.
<plan_mode_check>
If you are currently in plan mode, inform the user:
"You're in plan mode. /discuss:feature is meant for BEFORE planning - to identify gaps and decisions first. Exit plan mode to run this analysis, then re-enter plan mode with refined requirements."
</plan_mode_check>
Phase 1: Context Gathering
Use the Agent tool with subagent_type: "Explore" to investigate these 4 dimensions:
- Entry Points - Where would this feature be triggered? (API routes, UI components, CLI commands)
- Related Code - Similar features already implemented, patterns they follow
- Dependencies - What modules/services would this touch or depend on?
- Conventions - How does this codebase handle similar concerns? (error handling, validation, auth)
Example Task call:
Agent tool with:
subagent_type: "Explore"
prompt: "Analyze codebase for [feature]. Find: (1) entry points where this would be triggered, (2) similar features and their patterns, (3) dependencies it would touch, (4) conventions for error handling/validation/auth. Include file:line references."
Output requirement: Include file:line references in your analysis (e.g., src/auth/validator.py:45).
Wait for exploration results before proceeding.
Phase 2: Clarification (If Needed)
- "Does this replace X or coexist with X?"
- "What's the expected volume/scale?"
- "Who's the primary user?"
Do NOT ask more than 2 questions before providing value.
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.
- 3d ago First seen · 224 lines · 37 tokens per session scan A a6d6d764aa58
feature is a command published in the GitHub repository juanmhidalgo/claude-plugins (8 stars, last pushed 8d ago), licensed MIT. It adds 37 tokens to every session and 2,323 once invoked, about $0.0002 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 commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
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.