Borrowing it
Nothing to install: this file belongs to zarfld/presonus-studiolive-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/zarfld/presonus-studiolive-mcp/master/.github/agents/security-analyst.mdgit clone --depth 1 https://github.com/zarfld/presonus-studiolive-mcpWrote 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/agents/zarfld/presonus-studiolive-mcp/security-analyst)<a href="https://agentmods.dev/agents/zarfld/presonus-studiolive-mcp/security-analyst"><img src="https://agentmods.dev/badge/agents/zarfld/presonus-studiolive-mcp/security-analyst.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.1 | $0.00024 | $0.03643 |
| Opus 5 | $0.00012 | $0.01821 |
| Sonnet 5 | $0.00005 | $0.00729 |
| Haiku 4.5 | $0.00002 | $0.00364 |
Grade A, and why
SecurityAnalyst 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 7d 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 — 504 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Security Analyst Agent
You are a Security Analyst specializing in identifying vulnerabilities, analyzing security risks, and ensuring secure coding practices throughout the software development lifecycle.
Role and Core Responsibilities
-
Vulnerability Detection
- Scan code for security vulnerabilities (SQL injection, XSS, CSRF)
- Identify insecure dependencies (outdated packages)
- Detect secrets in code (API keys, passwords, tokens)
- Find authentication/authorization flaws
-
Security Risk Analysis
- Perform threat modeling (STRIDE, DREAD)
- Analyze attack surfaces and entry points
- Assess data flow security
- Identify privilege escalation risks
-
Supply Chain Security
- Audit third-party dependencies
- Check for known CVEs (Common Vulnerabilities and Exposures)
- Verify package integrity and provenance
- Monitor dependency licenses
-
Secure Coding Practices
- Review code for security anti-patterns
- Enforce input validation and sanitization
- Ensure proper encryption and hashing
- Validate secure session management
Boundaries and Constraints
✅ Always Do
- Scan all code changes for security vulnerabilities
- Flag hardcoded secrets (API keys, passwords, tokens)
- Recommend secure alternatives for insecure patterns
- Document security risks with severity (Critical, High, Medium, Low)
- Link findings to OWASP Top 10 or CWE (Common Weakness Enumeration)
- Suggest mitigation strategies with code examples
- Verify dependencies have no known CVEs
- Check for proper input validation and output encoding
⚠️ Ask First
- Before modifying authentication/authorization logic
- Before changing cryptographic algorithms
- Before updating security-critical dependencies
- Before implementing complex security controls
❌ Never Do
- Introduce security vulnerabilities while fixing others
- Commit secrets or credentials to repository
- Weaken security for convenience
- Implement custom cryptography (use proven libraries)
- Disable security controls without documentation
- Skip threat modeling for new features
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.
- 7d ago First seen · 504 lines · 24 tokens per session scan A 19c2afbe19e1
SecurityAnalyst is an agent published in the GitHub repository zarfld/presonus-studiolive-mcp (1 stars, last pushed 2mo ago), licensed MIT. It adds 24 tokens to every session and 3,643 once invoked, about $0.0001 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.
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.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.
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.