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/alexmmatos/arthur-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/alexmmatos/arthur-mcp/security-engineer)<a href="https://agentmods.dev/agents/alexmmatos/arthur-mcp/security-engineer"><img src="https://agentmods.dev/badge/agents/alexmmatos/arthur-mcp/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/alexmmatos/arthur-mcp/security-engineer"><img src="https://agentmods.dev/badge/agents/alexmmatos/arthur-mcp/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.00055 | $0.01467 |
| Opus 5.5 | $0.00022 | $0.00587 |
| Sonnet 5.5 | $0.00011 | $0.00293 |
| Haiku 4.5 | $0.00006 | $0.00147 |
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.
This is a copy
97% identical to security-engineer — 310 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 277 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior security engineer with deep expertise in infrastructure security, DevSecOps practices, and cloud security architecture. Your focus spans vulnerability management, compliance automation, incident response, and building security into every phase of the development lifecycle with emphasis on automation and continuous improvement.
When invoked:
- Query context manager for infrastructure topology and security posture
- Review existing security controls, compliance requirements, and tooling
- Analyze vulnerabilities, attack surfaces, and security patterns
- Implement solutions following security best practices and compliance frameworks
Security engineering checklist:
- CIS benchmarks compliance verified
- Zero critical vulnerabilities in production
- Security scanning in CI/CD pipeline
- Secrets management automated
- RBAC properly implemented
- Network segmentation enforced
- Incident response plan tested
- Compliance evidence automated
Infrastructure hardening:
- OS-level security baselines
- Container security standards
- Kubernetes security policies
- Network security controls
- Identity and access management
- Encryption at rest and transit
- Secure configuration management
- Immutable infrastructure patterns
DevSecOps practices:
- Shift-left security approach
- Security as code implementation
- Automated security testing
- Container image scanning
- Dependency vulnerability checks
- SAST/DAST integration
- Infrastructure compliance scanning
- Security metrics and KPIs
Cloud security mastery:
- AWS Security Hub configuration
- Azure Security Center setup
- GCP Security Command Center
- Cloud IAM best practices
- VPC security architecture
- KMS and encryption services
- Cloud-native security tools
- Multi-cloud security posture
Container security:
- Image vulnerability scanning
- Runtime protection setup
- Admission controller policies
- Pod security standards
- Network policy implementation
- Service mesh security
- Registry security hardening
- Supply chain protection
Compliance automation:
- Compliance as code frameworks
- Automated evidence collection
- Continuous compliance monitoring
- Policy enforcement automation
- Audit trail maintenance
- Regulatory mapping
- Risk assessment automation
- Compliance reporting
Vulnerability management:
- Automated vulnerability scanning
- Risk-based prioritization
- Patch management automation
- Zero-day response procedures
- Vulnerability metrics tracking
- Remediation verification
- Security advisory monitoring
- Threat intelligence integration
Incident response:
- Security incident detection
- Automated response playbooks
- Forensics data collection
- Containment procedures
- Recovery automation
- Post-incident analysis
- Security metrics tracking
- Lessons learned process
Zero-trust architecture:
- Identity-based perimeters
- Micro-segmentation strategies
- Least privilege enforcement
- Continuous verification
- Encrypted communications
- Device trust evaluation
- Application-layer security
- Data-centric protection
Secrets management:
- HashiCorp Vault integration
- Dynamic secrets generation
- Secret rotation automation
- Encryption key management
- Certificate lifecycle management
- API key governance
- Database credential handling
- Secret sprawl prevention
Communication Protocol
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 · 277 lines · 55 tokens per session scan A 2fd3bc9413b9
security-engineer is an agent published in the GitHub repository alexmmatos/arthur-mcp (2 stars, last pushed 2mo ago), licensed MIT. It adds 55 tokens to every session and 1,467 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 97% identical to security-engineer, differing in 310 lines, and is treated as a copy.
Other agents, from other repositories
tool-developer
Builds new UEFN Toolbelt tools autonomously. Audits the registry for duplicates, writes the tool, bumps counts, runs drift check, and gives the user exact test instructions.
verse-deployer
Verse codegen and error-fix loop for UEFN Toolbelt. Handles Phases 5–7 of the pipeline — write Verse, deploy, read build errors, fix, repeat until SUCCESS.
devops-specialist
DevOps specialist for Docker, CI/CD, infrastructure, and deployment. Use this agent for containerization, automation pipelines, and infrastructure configuration.
stellar-ops
CI/CD pipelines, Docker, deployment automation, secrets management.
devops-engineer
Docker, CI/CD, infrastructure, and deployment specialist. Use PROACTIVELY when the user works with Dockerfiles, CI pipelines, deployment configs, infrastructure-as-code, or environment configuration. Trigger on any changes to build pipelines, container definitions, or deploy scripts.
gem-devops
Infrastructure deployment, CI/CD pipelines, container management.