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/testzugang/pi-plugins/bash-approval-managernpx skills add testzugang/pi-plugins --skill bash-approval-managergit clone --depth 1 https://github.com/testzugang/pi-pluginsWhat 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.00063 | $0.00604 |
| Opus 5 | $0.00032 | $0.00302 |
| Sonnet 5 | $0.00013 | $0.00121 |
| Haiku 4.5 | $0.00006 | $0.00060 |
Grade A, and why
bash-approval-manager 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 2d 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 — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bash Approval Manager
Specialized assistant skill to audit, clean, and simulate whitelist patterns for the pi-bash-approval extension. Helps developers manage prompt fatigue, keep rules minimal, and prevent security vulnerabilities (such as command injection).
Capabilities
- Security & Quality Audit: Scan
~/.pi/agent/.bash-approvalfor:- Syntactically invalid regular expressions.
- Security risks (e.g. unanchored rules, greedy
.*wildcards). - Use of obsolete, vulnerable path pattern formulas (recommends the new injection-proof
PATH_PATTERN). - Duplicate or redundant rule definitions.
- Automatic Cleanup: Removes exact duplicates and redundant literal rules (literals already covered by broader regex or glob rules) with automatic backup creation.
- Command Simulation: Explains step-by-step why a specific shell command is allowed or blocked, showing exactly which whitelist line matched which segment.
Usage
All features are provided by the bundled cross-platform Node utility script scripts/manager.mjs.
1. Run Security and Quality Audit
Scan your current whitelist for security risks, syntactical errors, duplicates, and redundant entries:
node skills/bash-approval-manager/scripts/manager.mjs audit
2. Auto-Clean Duplicates and Redundancies
Clean up your .bash-approval file automatically. This removes exact duplicates and redundant literal rules (and creates a safety backup of your original file!):
node skills/bash-approval-manager/scripts/manager.mjs clean
3. Simulate Matching and Splitting
Simulate how the bash-approval interceptor evaluates a given command. This shows segment-by-segment matches or blocks:
node skills/bash-approval-manager/scripts/manager.mjs simulate "git -C siblings/ai-agents-playground status"
Agent Workflows
When the user asks you to inspect, verify, debug, or clean their bash-approval rules, use the following steps:
- Identify the Goal: Determine if they want to find out why a command was blocked (use
simulate), clean up rules (useclean), or check for security vulnerabilities (useaudit). - Run the Utility: Execute the corresponding subcommand via the
bashtool. - Synthesize Results: Present findings to the user. On auditing, explain what each warning means and give direct suggestions on how to improve the regex.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2d ago First seen · 49 lines · 63 tokens per session scan A 19c7dd15b811
bash-approval-manager is a skill published in the GitHub repository testzugang/pi-plugins (2 stars, last pushed 1mo ago), licensed MIT. It adds 63 tokens to every session and 604 once invoked, about $0.0003 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…