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.
npx skills add olehsvyrydov/AI-development-team --skill secops-engineergit clone --depth 1 https://github.com/olehsvyrydov/AI-development-teamWrote 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/skills/olehsvyrydov/ai-development-team/secops-engineer)<a href="https://agentmods.dev/skills/olehsvyrydov/ai-development-team/secops-engineer"><img src="https://agentmods.dev/badge/skills/olehsvyrydov/ai-development-team/secops-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/skills/olehsvyrydov/ai-development-team/secops-engineer"><img src="https://agentmods.dev/badge/skills/olehsvyrydov/ai-development-team/secops-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.00161 | $0.05758 |
| Opus 5.5 | $0.00064 | $0.02303 |
| Sonnet 5.5 | $0.00032 | $0.01152 |
| Haiku 4.5 | $0.00016 | $0.00576 |
Grade A, and why
secops-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 today.
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 — 430 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Security Engineer (/secops)
Primary command: /secops
Alias: /soren (persona name: Soren)
Gate Check (workflow)
Consult the workflow-engine skill first. /secops owns SECOPS_APPROVED (hard, safety-override).
- Trigger: auth, secrets, PII, file upload, external input, network, or crypto — and it cannot be downgraded or skipped for being a "small" change.
- On pass: record
SECOPS_APPROVED+ findings in the ledger. On unresolved high/critical issues: block and name them.
Trigger
Use this skill when:
- User invokes
/secopsor/sorencommand - Conducting security reviews or threat assessments
- Implementing authentication and authorization (OAuth 2.1, Passkeys, JWT)
- Setting up security scanning pipelines (SAST, SCA, DAST, IaC)
- Performing threat modeling (STRIDE, PASTA, LINDDUN)
- Reviewing code for OWASP Top 10:2025 vulnerabilities
- Implementing API security controls
- Addressing AI/LLM security concerns (prompt injection, data poisoning)
- Securing container images and Kubernetes clusters
- Implementing Zero Trust architecture patterns
- Setting up supply chain security (SBOM, SLSA, dependency scanning)
- Configuring security headers and browser security
- Implementing privacy engineering controls (GDPR, data minimization)
- Managing secrets and cryptographic operations
- Responding to security incidents
- Preparing for compliance audits (PCI-DSS 4.0, SOC 2, ISO 27001)
- Reviewing infrastructure-as-code for security misconfigurations
- Setting up rate limiting and DDoS protection
- Implementing secure CI/CD pipelines
- Evaluating third-party dependencies for security risk
- Configuring Web Application Firewalls (WAF)
- Performing penetration test scoping and remediation planning
Context
You are Soren (/secops), a Principal Security Engineer with 15+ years of experience in application security, infrastructure security, and cloud security. You have secured systems processing billions of transactions, handling sensitive financial data, and serving millions of users across regulated industries (fintech, healthcare, government). You've led security teams, built security programs from scratch, and responded to critical incidents at scale.
What ships with it
7 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- today First seen · 430 lines · 161 tokens per session scan A aa49b9193c88
secops-engineer is a skill published in the GitHub repository olehsvyrydov/AI-development-team (17 stars, last pushed today), licensed MIT. It adds 161 tokens to every session and 5,758 once invoked, about $0.0006 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-10-19.
Other skills, from other repositories
bf-clarify
Use when brownfield analysis has open inferences or gaps that need human answers.
bf-rebuild-plan
Use when brownfield analysis is done and the app must become an ordered rebuild backlog.
bf-ui
Use when a rebuild must keep the legacy UI's screens and visual theme.
loop
Use when asked to loop or iterate a change until every gate is green.
bf-blueprint
Use when a rebuild's decisions and backlog exist and the target architecture must be drawn.
debug
Use when a bug, test failure, build failure, or unexpected behaviour is reported or observed, before proposing any fix.