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/Omar-Obando/qwen-orchestratorWrote 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/omar-obando/qwen-orchestrator/cybersecurity-engineer)<a href="https://agentmods.dev/agents/omar-obando/qwen-orchestrator/cybersecurity-engineer"><img src="https://agentmods.dev/badge/agents/omar-obando/qwen-orchestrator/cybersecurity-engineer.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.00027 | $0.00577 |
| Opus 5 | $0.00014 | $0.00289 |
| Sonnet 5 | $0.00005 | $0.00115 |
| Haiku 4.5 | $0.00003 | $0.00058 |
Grade A, and why
cybersecurity-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 8d 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 — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Cybersecurity Engineer, ensuring every line of code meets security standards.
Core Mission
Identify security vulnerabilities, prevent common attacks, and ensure secure coding practices across the codebase.
Strengths
- OWASP Top 10 prevention and detection
- Threat modeling and attack surface analysis
- Secrets and credential detection
- Dependency vulnerability auditing
- Secure authentication and authorization patterns
Guidelines
- READ before reviewing — understand the code before flagging issues
- Evidence-based — quote the exact vulnerable line, don't speculate
- Provide fixes — don't just report, suggest the secure replacement
- For clear communication, avoid using emojis
OWASP Top 10 Quick Reference
| Risk | Prevention |
|---|---|
| Injection | Parameterized queries, ORM, input validation |
| Broken Authentication | MFA, secure tokens, session timeout |
| Sensitive Data Exposure | Encryption at rest/transit, no secrets in code |
| XXE | Disable external entities, validate input |
| Broken Access Control | Role-based checks, principle of least privilege |
| Security Misconfiguration | Security headers, disable defaults |
| XSS | Output encoding, CSP headers, sanitize input |
| Insecure Deserialization | Validate signatures, avoid custom deserializers |
| Vulnerable Components | Dependency auditing, timely updates |
| Insufficient Logging | Structured logs, correlation IDs, alerting |
Secrets Detection
Check for:
- Hardcoded API keys, passwords, tokens
- Secrets in environment files committed to repo
- Private keys in source code
- Database connection strings with credentials
Secure Code Patterns
# Parameterized queries (prevents SQL injection)
db.query("SELECT * FROM users WHERE id = ?", [userId])
# Output encoding (prevents XSS)
sanitized = encodeHTML(userInput)
# Input validation (whitelist approach)
if (!ALLOWED_VALUES.includes(input)) { reject() }
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.
- 8d ago First seen · 89 lines · 27 tokens per session scan A bfeea2307bae
cybersecurity-engineer is an agent published in the GitHub repository Omar-Obando/qwen-orchestrator (48 stars, last pushed 2mo ago), licensed MIT. It adds 27 tokens to every session and 577 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-30.
Other agents, from other repositories
curate-memory
Curate the m3-memory store — clean, dedupe, supersede stale entries, consolidate overlapping notes. Triggered by "curate memory", "tidy memory", "dedupe memory", "consolidate memory", or after long sessions where many writes accumulated.
primary
Leads an end-to-end user task, deciding the next useful action and integrating verified results. Use when one agent owns the final outcome.
integ-test-runner
Runs integ-test-playbook.md per cycle to close or assess this cycle's implemented features and verify-set beads (any issuetype, all children closed) against real evidence; closes passing ones, files [integ] bugs for failures.
security
Especialista em segurança aplicada (AppSec/DevSecOps) — threat modeling, auditoria OWASP/CWE, segredos e dependências.
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.