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/vibehat/claude-task-manager/reuse-checkgit clone --depth 1 https://github.com/vibehat/claude-task-managerWrote 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/vibehat/claude-task-manager/reuse-check)<a href="https://agentmods.dev/commands/vibehat/claude-task-manager/reuse-check"><img src="https://agentmods.dev/badge/commands/vibehat/claude-task-manager/reuse-check.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.1 | $0.00000 | $0.00257 |
| Opus 5 | $0.00000 | $0.00129 |
| Sonnet 5 | $0.00000 | $0.00051 |
| Haiku 4.5 | $0.00000 | $0.00026 |
Grade A, and why
reuse-check 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
Reuse Check - Validate Before Creating
Use this command before creating any new files or components to ensure you're not duplicating existing functionality.
Usage: /reuse-check [what you want to create]
Validation Process
MANDATORY REUSE ANALYSIS FOR: $ARGUMENTS
STEP 1: EXHAUSTIVE SEARCH
- Search for existing similar functionality
- Check all relevant directories and files
- Document every related component found
STEP 2: REUSABILITY ASSESSMENT
- Can existing code be extended?
- Can existing patterns be followed?
- Are there utility functions to reuse?
- What architectural constraints exist?
STEP 3: JUSTIFICATION REQUIREMENT If creating new files is necessary, provide:
- Detailed explanation why extension won't work
- Specific architectural reasons for new creation
- Migration strategy from any duplicate functionality
- Integration plan with existing systems
STEP 4: COMPLIANCE CONFIRMATION
- ✓ All existing options explored
- ✓ Extension possibilities exhausted
- ✓ Creation fully justified with specific reasons
- ✓ Follows existing architectural patterns
FINAL DECISION: [EXTEND EXISTING] or [CREATE NEW - JUSTIFIED]
Remember: Creating new files without this analysis violates project rules.
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 · 43 lines · 0 tokens per session scan A 7b1007429ba0
reuse-check is a command published in the GitHub repository vibehat/claude-task-manager (21 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 257 tokens. 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
check_schema_version
Check the Flyway schema version of the SQLite database on a Docker volume.
paul:help
Show available PAUL commands and usage guide.
kill-mutants
Analyze surviving mutants from a mutation testing run and write targeted unit tests to kill them. Re-runs mutations to confirm kills.
crear-skill
Crear, probar y mejorar skills de forma iterativa. Usa cuando el usuario dice "crear skill", "crear habilidad", "build skill", "create a skill", "skill development", "desarrollar skill", "nueva habilidad". Usa el workflow: draft → test → review → improve → repeat con evaluación cuantitativa y qualitative review.
iniciar
Inicializar Don Cheli en un proyecto nuevo o existente.
adr
You are helping create a new ADR (Architecture Decision Record). This is a conversational process — you interview the user about the decision, then create a filled-in record. ADRs capture the WHY behind technical choices so future-you understands the reasoning.