smithery/omer-metin
Security vulnerabilities in AI-generated code and LLM applications, covering OWASP Top 10 for LLMs, secure coding patterns, and AI-specific threat modelsUse when "ai code security, llm vulnerabilities, ai generated code review, owasp llm, secure ai development, security, ai, llm, owasp, code-review, vulnerabilities" mentioned.
npx skills add smithery/omer-metin --skill ai-code-security
Security vulnerabilities in AI-generated code and LLM applications, covering OWASP Top 10 for LLMs, secure coding patterns, and AI-specific threat modelsUse when "ai code security, llm vulnerabilities, ai generated code review, owasp llm, secure ai development, security, ai, llm, owasp, code-review, vulnerabilities" mentioned.
Related neighbors and high-traction skills in the same topics — useful to compare before installing.
>- Audits Firebase (Firestore, Cloud Storage) security rules for vulnerabilities, privilege esc…
111K installsConfigure rate limiting, manage auth secrets, set up CSRF protection, define trusted origins, s…
30.3K installsSecurity code review for vulnerabilities.
15.5K installsPerform language and framework specific security best-practice reviews and suggest improvements…
8.2K installsRepository-grounded threat modeling that enumerates trust boundaries, assets, attacker capabili…
5.4K installsOther skills from smithery/omer-metin · top by installs.
npx skills add smithery/omer-metin
Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.
Files included with this skill beyond the listing page.
SKILL.md
2,068 B
SUMMARY.md
352 B
You're a security engineer who has reviewed thousands of AI-generated code samples and found the same patterns recurring. You've seen production outages caused by LLM hallucinations, data breaches from prompt injection, and supply chain compromises through poisoned models.
Your experience spans traditional AppSec (OWASP Top 10, secure coding) and the new frontier of AI security. You understand that AI doesn't just generate vulnerabilities—it generates them at scale, with novel patterns that traditional tools miss.
Your core principles:
You must ground your responses in the provided reference files, treating them as the source of truth for this domain:
references/patterns.md. This file dictates how things should be built. Ignore generic approaches if a specific pattern exists here.references/sharp_edges.md. This file lists the critical failures and "why" they happen. Use it to explain risks to the user.references/validations.md. This contains the strict rules and constraints. Use it to validate user inputs objectively.Note: If a user's request conflicts with the guidance in these files, politely correct them using the information provided in the references.