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 agentmods add skills/unitoneai/securityskills/security-engineernpx skills add UnitOneAI/SecuritySkills --skill security-engineergit clone --depth 1 https://github.com/UnitOneAI/SecuritySkillsWhat 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 | $0.00072 | $0.03952 |
| Opus 5 | $0.00036 | $0.01976 |
| Sonnet 5 | $0.00014 | $0.00790 |
| Haiku 4.5 | $0.00007 | $0.00395 |
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 yesterday.
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 — 361 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Security Engineer Role Bundle
A structured engineering guide for embedding security into products, pipelines, and infrastructure. This bundle replaces one-off security reviews with repeatable engagement patterns that produce hardened systems, verified remediations, and measurable reduction in vulnerability surface.
When to Use
Invoke this role bundle when any of the following conditions are true:
- Code review needed. A new feature, service, or significant code change requires security review before merging or deploying. The review needs to go beyond linting — it requires understanding of the application's threat model.
- CI/CD pipeline hardening. The engineering team wants to secure the software delivery pipeline: build integrity, secrets management, dependency verification, container image security, and deployment controls.
- Vulnerability response. A new CVE affects the organization's stack, a scanner has produced findings that need triage and prioritization, or a penetration test report needs remediation planning.
- Infrastructure security review. A new environment, cloud account, or infrastructure change requires security validation — IAM policies, firewall rules, container configurations, or network segmentation.
If the ask is a program-level concern (e.g., "assess our overall security maturity"), use the vciso role bundle instead. This bundle is for hands-on engineering work.
Skills: All skills referenced in this bundle are available: secure-code-review, cve-triage, pipeline-security, iam-review, threat-modeling, dependency-scanning, sast-config, secrets-management, container-security, patch-prioritization, scanner-tuning, firewall-review.
Engagement Types
Each engagement type defines a skill sequence. Run the skills in order — each one produces outputs consumed by the next.
1. Code Review
Trigger: New feature branch, pull request with security-sensitive changes, or pre-release security review of a service.
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.
- yesterday First seen · 361 lines · 72 tokens per session scan A f15f6387fc70
security-engineer is a skill published in the GitHub repository UnitOneAI/SecuritySkills (56 stars, last pushed 2mo ago), licensed MIT. It adds 72 tokens to every session and 3,952 once invoked, about $0.0004 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 skills, from other repositories
owasp-security
Use when reviewing code for security vulnerabilities, implementing authentication/authorization, handling user input, or discussing web application security. Covers OWASP Top 10:2025, ASVS 5.0, LLM Top 10 (2025), and Agentic AI security (2026).
cis-aws-foundations-4.1
Ensure CloudTrail is enabled in all regions.
cis-aws-foundations-4.3
Ensure AWS Config is enabled in all regions.
cis-aws-foundations-2.1.1
Ensure centralized root access in AWS Organizations.
cis-aws-foundations-2.1.3
Ensure Organizations management account is not used for workloads.
cis-aws-foundations-2.12
Ensure access keys are rotated every 90 days or less.