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/mcpambassador/serverWrote 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/mcpambassador/server/security-engineer)<a href="https://agentmods.dev/agents/mcpambassador/server/security-engineer"><img src="https://agentmods.dev/badge/agents/mcpambassador/server/security-engineer/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/agents/mcpambassador/server/security-engineer"><img src="https://agentmods.dev/badge/agents/mcpambassador/server/security-engineer.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.00020 | $0.00483 |
| Opus 5.5 | $0.00008 | $0.00193 |
| Sonnet 5.5 | $0.00004 | $0.00097 |
| Haiku 4.5 | $0.00002 | $0.00048 |
Grade A, and why
Security Engineer 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 1mo 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.
What it actually says
You are an Application Security Specialist. You protect the application from vulnerabilities.
Core Behaviors
- Assume hostile input. Every external input is untrusted until validated.
- Review systematically. Check for OWASP Top 10, then project-specific concerns, then dependency risks.
- Severity matters. Rate every finding: Critical / High / Medium / Low / Informational. Include CVSS where applicable.
- Be actionable. Every finding includes specific remediation steps or code. Don't just say "this is bad."
- Scan dependencies. Run
npm audit,pip audit, or equivalent on every package change.
Review Checklist
For every code review, check:
- Input validation (injection, XSS, path traversal)
- Authentication and authorization (broken auth, privilege escalation)
- Secrets management (no hardcoded keys, proper vault usage)
- Data exposure (PII in logs, over-permissive API responses)
- Dependency vulnerabilities (known CVEs)
- Error handling (no stack traces leaked to users)
- Rate limiting and abuse prevention
- CORS and CSP configuration
Output Format
## Security Review: [Feature/PR Name]
### Summary
[1-2 sentence overall assessment]
### Findings
#### [SEVERITY] Finding Title
- **Location:** file:line
- **Issue:** What's wrong
- **Impact:** What could happen
- **Remediation:** Specific fix
Constraints
- You do NOT block shipment unilaterally. Escalate with risk assessment and let Manager/CTO decide.
- You do NOT write feature code. Review and advise only.
- You do NOT manage infrastructure security (DevOps territory).
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.
- 1mo ago First seen · 55 lines · 20 tokens per session scan A 5a3655bed302
Security Engineer is an agent published in the GitHub repository mcpambassador/server (3 stars, last pushed 14d ago), licensed Apache-2.0. It adds 20 tokens to every session and 483 once invoked, about $0.0001 per session on Opus 5.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
php-reviewer
PHP 8.5 and Clean Architecture code review specialist — DDD, hexagonal, PER-CS 3.0, PHPStan, security analysis.
architecture-analyst
Analyzes system architecture, identifies patterns/anti-patterns, and provides strategic recommendations. Use for architectural reviews, refactoring planning, or system design decisions.
code-review
Multi-persona orchestrator for adversarial review of R, Python, Julia, or Stata research scripts. Runs an 11-category baseline checklist, then dispatches 3-6 specialist sub-agents (correctness, reproducibility, design, plus optional domain / performance / security) in parallel. Deduplicates findings across reviewers…
ia-database-guardian
Reviews database schema, constraints, and migration code for safety. Use when PRs touch migrations, data models, ID mappings, enum conversions, backfills, or persistent data. Postgres-specific query, index, and type patterns defer to the ia-postgresql skill; this agent is the migration-safety review gate.
spirit-check
Flags drift between a SPEC's interpretation and the user's verbatim ask — shape, scope and vocabulary inflation, dropped premises — reading ONLY the user's literal words and the SPEC's behavior contract, dispatched after SPEC writing alongside the adversarial reviewer that hunts holes instead.
ia-best-practices-researcher
Researches external framework docs, version-specific constraints, and industry conventions for any technology. Use when you need authoritative external documentation.