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/dinnovos/dinnovos-marketplaceWrote 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/dinnovos/dinnovos-marketplace/bro-this-is-slow)<a href="https://agentmods.dev/commands/dinnovos/dinnovos-marketplace/bro-this-is-slow"><img src="https://agentmods.dev/badge/commands/dinnovos/dinnovos-marketplace/bro-this-is-slow/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/dinnovos/dinnovos-marketplace/bro-this-is-slow"><img src="https://agentmods.dev/badge/commands/dinnovos/dinnovos-marketplace/bro-this-is-slow.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.00033 | $0.03437 |
| Opus 5 | $0.00016 | $0.01718 |
| Sonnet 5 | $0.00007 | $0.00687 |
| Haiku 4.5 | $0.00003 | $0.00344 |
Grade A, and why
bro-this-is-slow 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 12d 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 — 592 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Performance Audit
Analyze code for performance issues and optimization opportunities. Read-only, doesn't modify anything. Multi-language support.
User Input
The user can specify what to audit in various ways:
Exact path:
/bro-this-is-slow src//bro-this-is-slow src/services/dataService.ts/bro-this-is-slow app/handlers/
Natural language (illustrative examples):
/bro-this-is-slow analyze performance of <module>/bro-this-is-slow find memory leaks in <area>/bro-this-is-slow review queries in <service>/bro-this-is-slow optimizations for <component>/bro-this-is-slow why is <feature> slow
No arguments:
/bro-this-is-slow→ audits the entire project
Note: Terms like "API", "dashboard", "reports" are just examples. Interpret what the user requests and search for the corresponding files in the project.
Step 1: Interpret the Request
If it's an exact path:
Use directly.
If it's natural language:
Search for files matching the description:
# Explore project structure
find . -type f \( -name "*.ts" -o -name "*.tsx" -o -name "*.js" -o -name "*.jsx" -o -name "*.py" -o -name "*.go" -o -name "*.rs" -o -name "*.java" \) \
! -path "*/node_modules/*" ! -path "*/.git/*" ! -path "*/dist/*" ! -path "*/build/*" ! -path "*/target/*"
# Search by related name
find . -type f -iname "*<term>*" | grep -v node_modules
find . -type d -iname "*<term>*" | grep -v node_modules
# Search related content
grep -ril "<term>" --include="*.ts" --include="*.tsx" --include="*.js" --include="*.py" --include="*.go" | grep -v node_modules | head -30
Confirm with the user if you find multiple matches.
Limit: Maximum 100 files. If there are more, ask to narrow down or prioritize by risk.
Step 2: Project Context
# Standards and guides
cat CLAUDE.md 2>/dev/null
cat AGENTS.md 2>/dev/null
# Detect stack
cat package.json pyproject.toml go.mod Cargo.toml composer.json 2>/dev/null
# Build and bundle configuration
cat webpack.config.js 2>/dev/null
cat vite.config.ts 2>/dev/null
cat next.config.js 2>/dev/null
cat tsconfig.json 2>/dev/null
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.
- 12d ago First seen · 592 lines · 33 tokens per session scan A b29bed5bc7f1
bro-this-is-slow is a command published in the GitHub repository dinnovos/dinnovos-marketplace (2 stars, last pushed 7mo ago), licensed MIT. It adds 33 tokens to every session and 3,437 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
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…
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…
fix
Universal debugging and fix application with semantic code analysis.
doctor
Badi configuration validation. Checks all Badi components and produces a diagnostic report.
http-service
Build, review or debug a Bun HTTP service. Loads the http-service skill, then works the task through its workflow.
gh-issue-use-cypress
Like /gh-issue-use-browser, but pinned to the Cypress MCP — use when your project runs the Cypress MCP for browser automation. Example — /gh-issue-use-cypress "Composer > Save" saving toasts failure but the record persists.