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 skills/pr3m/claude-code-bash-smart-approve/statusnpx skills add pr3m/claude-code-bash-smart-approve --skill statusgit clone --depth 1 https://github.com/pr3m/claude-code-bash-smart-approveWrote 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/skills/pr3m/claude-code-bash-smart-approve/status)<a href="https://agentmods.dev/skills/pr3m/claude-code-bash-smart-approve/status"><img src="https://agentmods.dev/badge/skills/pr3m/claude-code-bash-smart-approve/status.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 | $0.00065 | $0.00518 |
| Opus 5 | $0.00032 | $0.00259 |
| Sonnet 5 | $0.00013 | $0.00104 |
| Haiku 4.5 | $0.00006 | $0.00052 |
Grade B, and why
bash-smart-approve:status scanned grade B 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 4d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
Read `~/.claude/settings.json` and check `hooks.PreToolUse`. What it actually says
Status / Health Check
Step 1 — Dependencies
shfmt --version→ report version or ❌ missingnode --version→ report version
Step 2 — Hook wired
Read ~/.claude/settings.json and check hooks.PreToolUse.
Find any entry whose command references bash-smart-approve or approve.js.
Report:
- ✅ Hook wired at
<path>with timeout<N>s - ❌ Hook not found in settings → suggest
/bash-smart-approve:install
Also check .claude/settings.json and .claude/settings.local.json in cwd for project-level hook overrides.
Step 3 — Enabled state
- Config
enabledflag: read user + project config. Report effective value. BASH_SMART_APPROVE_DISABLEenv var: checkprocess.envvia a bash probe (echo "${BASH_SMART_APPROVE_DISABLE:-unset}").- If either disables the plugin, flag it prominently.
Step 4 — Scope
If scopeDirectories is set, report whether the current cwd is in scope.
Step 5 — Recent activity
If the log file exists, report:
- Entries in the last 24h
- Split: allowed vs asked vs denied
- Most recent entry timestamp
Use: tail -n 200 <logFile> and parse JSON lines.
Step 6 — Output
Single compact status block:
bash-smart-approve — status
Dependencies: shfmt 3.13.1 ✅ · node v20.11.0 ✅
Hook wired: ✅ ~/.claude/settings.json (timeout 5s)
Plugin enabled: ✅ (config + env)
Scope: everywhere (cwd is in scope)
Config: ~/.claude/bash-smart-approve.json
42 binaries · 3 domains · 1 rm path
Recent (24h): 17 allowed · 3 asked · 0 denied
Last activity: 2 min ago
OK → plugin is operational.
If any ❌, lead with remediation steps.
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.
- 4d ago First seen · 63 lines · 65 tokens per session scan B 7677b83225b1
bash-smart-approve:status is a skill published in the GitHub repository pr3m/claude-code-bash-smart-approve (1 stars, last pushed 4mo ago), licensed MIT. It adds 65 tokens to every session and 518 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
workflow-address-feedback
Use when a PR owner wants to address review feedback — fetches outstanding threads and general comments, presents a per-item triage (ADDRESSED / CLARIFIED / DEFERRED), applies fixes via the Edit tool, commits via workflow-commit-and-pr, resolves review threads via GraphQL resolveReviewThread (those without a thread…
workflow-branch-sync
Sync the current branch with the default branch via rimba or git, then resolve conflicts file by file with a per-hunk rationale and a keep-mine / keep-main / manual recommendation before staging. Push only happens after explicit confirmation — never automatic.
workflow-commit-and-pr
Use when the user wants to commit staged changes or create a PR — enforces trigger-phrase discipline (preview vs commit vs ship), the [type] commit format, branch-naming check, draft-vs-ready PR prompt, and PR template detection. Pre-merge counterpart to workflow-cleanup-merged.
workflow-pr-review
Use when reviewing a remote GitHub PR — a first-pass peer review, or a followup re-check after the owner has addressed feedback. Fetches into an ephemeral worktree, runs the reviewer agent against the updated diff with a Review Decision footer instruction, deduplicates findings against existing review threads (±5-line…
workflow-audit-emit-issues
After a codebase audit, groups audit findings by subsystem (path prefix) and emits them as context-rich GitHub issues with template discovery, label selection, and a batch preview-confirm gate before filing. Keywords — audit findings grouped github issues subsystem emit.
workflow-bug-triage
Use when investigating a bug to root-cause and FILE a GitHub issue rather than fixing immediately — counterpart to /swe-workbench:debug (which patches). Enforces the Iron Law (no patches without root cause), and produces a structured issue with code-path table and impact assessment.