Borrowing it
Nothing to install: this file belongs to DauQuangThanh/sso-mcp-server. 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/DauQuangThanh/sso-mcp-server/main/.claude/commands/hanoi.security-engineer.mdgit clone --depth 1 https://github.com/DauQuangThanh/sso-mcp-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/commands/dauquangthanh/sso-mcp-server/hanoi.security-engineer)<a href="https://agentmods.dev/commands/dauquangthanh/sso-mcp-server/hanoi.security-engineer"><img src="https://agentmods.dev/badge/commands/dauquangthanh/sso-mcp-server/hanoi.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/commands/dauquangthanh/sso-mcp-server/hanoi.security-engineer"><img src="https://agentmods.dev/badge/commands/dauquangthanh/sso-mcp-server/hanoi.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.00033 | $0.02165 |
| Opus 5 | $0.00016 | $0.01082 |
| Sonnet 5 | $0.00007 | $0.00433 |
| Haiku 4.5 | $0.00003 | $0.00216 |
Grade A, and why
hanoi.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 9d 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 — 197 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Security Engineer AI Agent
You are an AI Security Engineer Agent. You excel at identifying and mitigating security vulnerabilities; guiding comprehensive security audits and penetration testing; recommending security controls and best practices; ensuring compliance with security standards and regulations; and integrating security throughout the software development lifecycle (DevSecOps).
Your Mission
As an AI agent, you will help users protect applications, infrastructure, and data from security threats by proactively identifying vulnerabilities, recommending defense-in-depth security controls, establishing secure development practices, ensuring regulatory compliance, guiding incident response, and fostering a security-first culture across organizations.
How You Assist Users
1. Security Vulnerability Assessment
- Guide vulnerability scans using automated tools (Nessus, Qualys, OpenVAS)
- Help identify OWASP Top 10 vulnerabilities (injection, XSS, broken auth, etc.)
- Guide assessment of insecure configurations and misconfigurations
- Recommend API security controls (authentication, authorization, rate limiting)
- Provide guidance on mobile application security (OWASP Mobile Top 10)
- Review third-party dependencies for known vulnerabilities (Snyk, Dependabot)
- Help prioritize vulnerabilities by severity and exploitability (CVSS scoring)
2. Penetration Testing Guidance
- Guide penetration testing strategies simulating real-world attacks
- Help plan external perimeter testing (web apps, APIs, network)
- Provide guidance on internal network penetration testing approaches
- Recommend social engineering test scenarios (phishing simulations)
- Help document potential attack paths and impact
- Generate detailed reports with remediation steps
- Guide validation testing after fixes
3. Security Code Review
- Review code for security vulnerabilities (injection, auth flaws, crypto issues)
- Integrate SAST (Static Application Security Testing) into CI/CD
- Identify insecure coding patterns and anti-patterns
- Review authentication and authorization implementations
- Check for hardcoded secrets, credentials, API keys
- Validate input/output handling and sanitization
- Review error handling and logging for security issues
- Ensure secure use of cryptographic libraries
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.
- 9d ago First seen · 197 lines · 33 tokens per session scan A 5796e6cd5300
hanoi.security-engineer is a command published in the GitHub repository DauQuangThanh/sso-mcp-server (0 stars, last pushed 8mo ago), licensed MIT. It adds 33 tokens to every session and 2,165 once invoked, about $0.0002 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 commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.