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-is-this-safe)<a href="https://agentmods.dev/commands/dinnovos/dinnovos-marketplace/bro-is-this-safe"><img src="https://agentmods.dev/badge/commands/dinnovos/dinnovos-marketplace/bro-is-this-safe/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-is-this-safe"><img src="https://agentmods.dev/badge/commands/dinnovos/dinnovos-marketplace/bro-is-this-safe.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.00026 | $0.02815 |
| Opus 5 | $0.00013 | $0.01407 |
| Sonnet 5 | $0.00005 | $0.00563 |
| Haiku 4.5 | $0.00003 | $0.00281 |
Grade A, and why
bro-is-this-safe scanned grade A with 1 finding 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.
Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
| Python | `os.system(f"ping {h}")` | `subprocess.run(['ping', h])` | How it starts
The opening of the file, as written. The whole thing — 464 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Security Scan
Analyze code for security vulnerabilities. Read-only, doesn't modify anything. Multi-language support.
User Input
The user can specify what to scan in various ways:
Exact path:
/bro-is-this-safe src/api//bro-is-this-safe src/auth/authService.ts/bro-is-this-safe app/auth/
Natural language (illustrative examples):
/bro-is-this-safe scan the <area> module/bro-is-this-safe check security in <feature>/bro-is-this-safe analyze vulnerabilities in <topic> services/bro-is-this-safe look for secrets in <module>
No arguments:
/bro-is-this-safe→ scans the entire project
Note: Terms like "authentication", "payments", "API" 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 (includes config files)
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 "*.php" -o -name "*.rb" -o -name "*.java" -o -name "*.env*" -o -name "*.yml" -o -name "*.yaml" -o -name "Dockerfile*" \) \
! -path "*/node_modules/*" ! -path "*/vendor/*" ! -path "*/target/*" ! -path "*/.git/*" ! -path "*/dist/*"
# 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 (auth, api, config first).
Step 2: Project Context
Search and read configuration and standards files:
# Project standards and guides
cat CLAUDE.md 2>/dev/null
cat AGENTS.md 2>/dev/null
cat .cursor/rules.md 2>/dev/null
# Security configuration
cat .env.example 2>/dev/null
cat .gitignore 2>/dev/null
# Detect stack
cat package.json pyproject.toml go.mod Cargo.toml composer.json 2>/dev/null
cat docker-compose.yml 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 · 464 lines · 26 tokens per session scan A 115ace161ccd
bro-is-this-safe is a command published in the GitHub repository dinnovos/dinnovos-marketplace (2 stars, last pushed 7mo ago), licensed MIT. It adds 26 tokens to every session and 2,815 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
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.
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.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.