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/profile)<a href="https://agentmods.dev/commands/juanmhidalgo/claude-plugins/profile"><img src="https://agentmods.dev/badge/commands/juanmhidalgo/claude-plugins/profile/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/profile"><img src="https://agentmods.dev/badge/commands/juanmhidalgo/claude-plugins/profile.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.00040 | $0.00516 |
| Opus 5.5 | $0.00016 | $0.00206 |
| Sonnet 5.5 | $0.00008 | $0.00103 |
| Haiku 4.5 | $0.00004 | $0.00052 |
Grade A, and why
profile 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 1mo 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
Focused Profiling
Target: $ARGUMENTS
Step 1: Understand the Code
Read the target function/endpoint. Understand what it does, what it calls, and what data flows through it.
Step 2: Identify Measurement Approach
Based on the language and context:
Python:
python -m cProfile -s cumulative script.py
python -m timeit -s "setup" "expression"
Node.js:
console.time('operation');
// ... code ...
console.timeEnd('operation');
Database queries:
- Enable query logging to see actual SQL and timing
- Check for N+1 patterns in the query log
- Look for missing indexes on WHERE/JOIN columns
Step 3: Profile
Run the profiling tool and collect baseline numbers. Record:
- Total execution time
- Hot spots (functions consuming the most time)
- Call counts (functions called most frequently)
- Memory allocation (if relevant)
Step 4: Analyze & Recommend
For each hot spot:
- Is it doing unnecessary work? (redundant computation, fetching unused data)
- Is it doing work at the wrong time? (could be cached, deferred, or parallelized)
- Is it using an inefficient algorithm? (O(n²) when O(n) is possible)
Provide specific fix recommendations with expected improvement.
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.
- 1mo ago First seen · 85 lines · 40 tokens per session scan A 69a918f7e097
profile is a command published in the GitHub repository juanmhidalgo/claude-plugins (8 stars, last pushed 5d ago), licensed MIT. It adds 40 tokens to every session and 516 once invoked, about $0.0002 per session on Opus 5.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
qa-changes
This skill should be used when the user asks to "QA a pull request", "test PR changes", "verify a PR works", "functionally test changes", or when an automated workflow triggers QA validation of code changes. Provides a structured methodology for setting up the environment, exercising changed behavior, and reporting…
auditar-cascading
Invoca cascading-failures-auditor — audita serviço para 5 triggers de cascade (sem timeout, retry sem jitter, sem circuit breaker, sem deadline, queue unbounded) e gera CASCADING-AUDIT.md.
doctor
Diagnosticar y reparar problemas del framework Don Cheli, git y entorno. Usa cuando el usuario dice "doctor", "problemas del framework", "don cheli no funciona", "repair Don Cheli", "debug setup", "setup broken", "framework broken", "reparar entorno". Detecta y repara issues de configuración, git y dependencias…
http-service
Build, review or debug a Bun HTTP service. Loads the http-service skill, then works the task through its workflow.
doctor
Badi configuration validation. Checks all Badi components and produces a diagnostic report.
fix
Universal debugging and fix application with semantic code analysis.