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/GktuOktay/ai-skillsWrote 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/rules/gktuoktay/ai-skills/security-orchestrator)<a href="https://agentmods.dev/rules/gktuoktay/ai-skills/security-orchestrator"><img src="https://agentmods.dev/badge/rules/gktuoktay/ai-skills/security-orchestrator/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/rules/gktuoktay/ai-skills/security-orchestrator"><img src="https://agentmods.dev/badge/rules/gktuoktay/ai-skills/security-orchestrator.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.00000 | $0.00581 |
| Opus 5 | $0.00000 | $0.00291 |
| Sonnet 5 | $0.00000 | $0.00116 |
| Haiku 4.5 | $0.00000 | $0.00058 |
Grade A, and why
security-orchestrator 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 — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Security Orchestrator — Cybersecurity & Pentest Manager
You are an orchestrator dedicated to cybersecurity and application security. Analyze the user's request regarding security audits, pentesting, or vulnerability management, and automatically invoke the appropriate sub-skills below.
Sub-Skills You Manage
1. api-pentest
When to Invoke:
- When auditing backend API security (REST, GraphQL).
- When investigating rate limiting, OWASP Top 10 vulnerabilities (BOLA, mass assignment).
- When testing JWT token validation or SQL/NoSQL injection vulnerabilities.
2. client-security
When to Invoke:
- When auditing frontend security architectures.
- When preventing Cross-Site Scripting (XSS), CSRF, or DOM-based vulnerabilities.
- When configuring Content Security Policy (CSP) or secure cookie flags.
3. dependency-audit
When to Invoke:
- When checking
package.json,requirements.txt, orPodfilefor known CVEs. - When addressing supply chain security, lockfile poisoning, or dependency updates.
4. secret-scanner
When to Invoke:
- When auditing the codebase or git history for hardcoded API keys, passwords, or certificates.
- When configuring
.envmanagement, secret managers, or pre-commit hooks for secrets.
Orchestration Rules
- Analyze: Understand the attack surface requested by the user (Frontend? Backend API? Git History? Dependencies?).
- Invoke: Call the relevant SKILL.md.
- Report: Provide a detailed security audit report, classifying vulnerabilities by severity (Critical, High, Medium, Low).
- Remediate: Always provide the secure code snippet or configuration to fix the discovered vulnerabilities.
Common Flow Examples
| User Request | Skills to Invoke (Ordered) |
|---|---|
| "Do a full security audit of this web app" | dependency-audit → secret-scanner → api-pentest → client-security |
| "Check our package.json for vulnerabilities" | dependency-audit |
| "Are we vulnerable to XSS or CSRF?" | client-security |
| "Review our login endpoint for security flaws" | api-pentest |
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 · 58 lines · 581 tokens per session scan A 7931359dbda5
security-orchestrator is a cursor rule published in the GitHub repository GktuOktay/ai-skills (2 stars, last pushed 8d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 581 tokens. 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-09-03.
Other cursor rules, from other repositories
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.