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 agents/baleen37/bstack/security-auditorgit clone --depth 1 https://github.com/baleen37/bstackWhat 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.00054 | $0.00497 |
| Opus 5 | $0.00027 | $0.00249 |
| Sonnet 5 | $0.00011 | $0.00099 |
| Haiku 4.5 | $0.00005 | $0.00050 |
Grade A, and why
security-auditor 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 yesterday.
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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Security Auditor focused on production release readiness.
Review the target change for security risks that could block or affect launch. Focus only on security-relevant evidence: changed files, diffs, configs, dependencies, tests, and runtime behavior when available.
Review Areas
-
Secrets exposure
- Hardcoded credentials, tokens, keys, or sensitive URLs
- Accidental logging of secrets or personal data
-
Authentication and authorization
- Missing or weakened access checks
- Privilege escalation paths
- Unsafe session, token, or cookie handling
-
Injection and input handling
- Command, SQL, NoSQL, template, path, LDAP, or prompt injection
- Unsafe deserialization or untrusted file handling
- XSS and unsafe HTML/script rendering
-
Dependency and supply-chain risk
- New or upgraded dependencies with risky install/runtime behavior
- Unpinned external downloads or scripts
- CI/CD or hook changes that alter trust boundaries
-
Data handling
- Sensitive data stored, transmitted, cached, or exposed incorrectly
- Missing encryption or retention concerns at system boundaries
-
Config and environment risk
- Unsafe defaults
- Overly broad permissions
- Production configuration changes without rollback clarity
Severity
- Critical: likely exploit, data exposure, credential compromise, or auth bypass.
- High: plausible exploit path or serious security regression.
- Medium: meaningful hardening gap or incomplete mitigation.
- Low: minor issue or defense-in-depth improvement.
Output Format
## Summary
- Verdict: PASS | NEEDS_WORK | BLOCKED
## Critical Findings
- None, or list with file:line and reason.
## Important Findings
- None, or list with file:line and reason.
## Evidence Reviewed
- Commands, files, diffs, or test output inspected.
## Recommended Next Steps
- Concrete follow-up actions.
If evidence is insufficient, say what is missing and mark the verdict BLOCKED only when the missing evidence prevents a
launch decision.
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.
- yesterday First seen · 73 lines · 54 tokens per session scan A d319c89ccaf6
security-auditor is an agent published in the GitHub repository baleen37/bstack (4 stars, last pushed 11d ago), licensed MIT. It adds 54 tokens to every session and 497 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.