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/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/checklist)<a href="https://agentmods.dev/commands/juanmhidalgo/claude-plugins/checklist"><img src="https://agentmods.dev/badge/commands/juanmhidalgo/claude-plugins/checklist/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/juanmhidalgo/claude-plugins/checklist"><img src="https://agentmods.dev/badge/commands/juanmhidalgo/claude-plugins/checklist.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.00041 | $0.00458 |
| Opus 5 | $0.00020 | $0.00229 |
| Sonnet 5 | $0.00008 | $0.00092 |
| Haiku 4.5 | $0.00004 | $0.00046 |
Grade A, and why
checklist 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 6d 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
Context
- Branch: !
git branch --show-current - Staged files: !
git diff --cached --name-only
Security Checklist Verification
Area focus: $ARGUMENTS (if empty, run all areas).
For each checklist item, verify against the actual codebase using Grep and Read. Report each item as:
- PASS — verified in code
- FAIL — violation found (include file:line)
- N/A — not applicable to this codebase
- UNKNOWN — could not determine (needs manual review)
If area is specified
Run only the matching section from the checklist (auth, input, data, infra, or deps).
If no area specified
Run all sections, starting with the highest-risk areas:
- Authentication & Authorization
- Input Validation
- Data Protection
- Infrastructure & Headers
- Dependencies
Output
## Security Checklist Report
### [Area Name]
- [PASS] Item description
- [FAIL] Item description — `file:line` — details
- [N/A] Item description — reason
Summarize with pass/fail/na counts per area and overall assessment.
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.
- 6d ago First seen · 73 lines · 41 tokens per session scan A b7cb44de449d
checklist is a command published in the GitHub repository juanmhidalgo/claude-plugins (8 stars, last pushed yesterday), licensed MIT. It adds 41 tokens to every session and 458 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-09-03.
Other commands, from other repositories
speckit.hashloom.gate
Verify the feature's seams through the hashloom cache: cached-green precheck before implementation, hard verify --radius gate after.
methodology
Display the Agent Triforce checklist methodology reference.
lsp-setup
Set up LSP (Language Server Protocol) integration for real-time code intelligence.
brainstorm
Start a brainstorming session to design a feature before implementation.
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.