Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add yonatangross/orchestkit/plugin install orkWrote 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/yonatangross/orchestkit/security-patterns)<a href="https://agentmods.dev/skills/yonatangross/orchestkit/security-patterns"><img src="https://agentmods.dev/badge/skills/yonatangross/orchestkit/security-patterns.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.00056 | $0.05620 |
| Opus 5 | $0.00028 | $0.02810 |
| Sonnet 5 | $0.00011 | $0.01124 |
| Haiku 4.5 | $0.00006 | $0.00562 |
Grade B, and why
security-patterns scanned grade B with 2 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.
Reaches for credential filesmediumPrivilege escalation
SSH keys, cloud credentials, git-credentials, .npmrc, /etc/shadow: reading these is how a config file becomes a credential leak.
"files": [{ "path": "~/.aws/credentials", "mode": "deny" }], Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
Reads agent configuration directorieslowAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
| 3. User (`~/.claude/settings.json`) | Personal preferences | Final authority | Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
How it starts
The opening of the file, as written. The whole thing — 413 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Security Patterns
Comprehensive security patterns for building hardened applications. Each category has individual rule files in rules/ loaded on-demand.
Quick Reference
| Category | Rules | Impact | When to Use |
|---|---|---|---|
| Authentication | upstream | CRITICAL | JWT tokens, OAuth 2.1/PKCE, RBAC/permissions |
| Defense-in-Depth | 1 | CRITICAL | Multi-layer security, zero-trust architecture |
| Input Validation | 2 | HIGH | Schema validation (Zod/Pydantic), output encoding, file uploads |
| OWASP Top 10 | 1 | CRITICAL | Injection prevention, broken authentication fixes |
| LLM Safety | refs | HIGH | Prompt injection defense, output guardrails, content filtering |
| PII Masking | refs | HIGH | PII detection/redaction with Presidio, Langfuse, LLM Guard |
| Scanning | upstream | HIGH | Dependency audit, SAST (Semgrep/Bandit), secret detection |
| Advanced Guardrails | 2 | CRITICAL | NeMo/Guardrails AI validators, red-teaming, OWASP LLM |
Total: 6 rule files across 4 categories. Topics marked "upstream" or "refs" keep only
the ork delta here: floors and key decisions in this file, scars and house decisions in
references/ork-delta.md, and first-party sources in
Upstream coverage.
Quick Start
# Argon2id password hashing
from argon2 import PasswordHasher
ph = PasswordHasher()
password_hash = ph.hash(password)
ph.verify(password_hash, password)
# JWT access token (15-min expiry)
import jwt
from datetime import datetime, timedelta, timezone
payload = {
'sub': user_id, 'type': 'access',
'exp': datetime.now(timezone.utc) + timedelta(minutes=15),
}
token = jwt.encode(payload, SECRET_KEY, algorithm='HS256')
// Zod v4 schema validation
import { z } from 'zod';
const UserSchema = z.object({
email: z.email(),
name: z.string().min(2).max(100),
role: z.enum(['user', 'admin']).default('user'),
});
const result = UserSchema.safeParse(req.body);
What ships with it
31 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.
- checklists/auth-checklist.md 3.0 KB
- checklists/pre-deployment-security.md 2.5 KB
- checklists/pre-llm-call.md 2.5 KB
- checklists/safety-checklist.md 656 B
- checklists/validation-checklist.md 3.3 KB
- metadata.json 619 B
- references/audit-logging.md 6.0 KB
- references/cc-permission-model.md 5.3 KB
- references/context-separation.md 9.5 KB
- references/langfuse-mask-callback.md 2.2 KB
- references/ork-delta.md 2.5 KB
- references/output-guardrails.md 13 KB
- references/post-llm-attribution.md 11 KB
- references/pre-llm-filtering.md 9.5 KB
- references/presidio-integration.md 1.9 KB
- references/prompt-audit.md 13 KB
- references/request-context-pattern.md 4.3 KB
- rules/_sections.md 1.4 KB
- rules/_template.md 339 B
- rules/defense-layers.md 4.8 KB
- rules/guardrails-llm-validation.md 3.2 KB
- rules/guardrails-nemo.md 3.0 KB
- rules/supply-chain.md 3.7 KB
- rules/validation-input.md 3.7 KB
- rules/validation-output.md 3.4 KB
- scripts/auth-middleware-template.py 7.0 KB runs code
- scripts/prompt_builder.py 8.3 KB runs code
- scripts/safe_llm_call.py 9.0 KB runs code
- scripts/scan-vulnerabilities.sh 8.4 KB runs code
- scripts/validation-schemas.ts 6.9 KB runs code
- test-cases.json 8.7 KB
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 · 413 lines · 56 tokens per session scan B 78d032799c79
security-patterns is a skill published in the GitHub repository yonatangross/orchestkit (228 stars, last pushed yesterday), licensed MIT. It adds 56 tokens to every session and 5,620 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it B with 2 findings (reaches for credential files, reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-05.
Other skills, from other repositories
auth0-docs
Auth0 — identity platform: auth flows, Universal Login, SSO, identity providers, MFA, RBAC, Actions, tokens.
auth-patterns
Use when implementing authentication (JWT, sessions, OAuth), authorization (RBAC, ABAC), password hashing, MFA, or security best practices for backend services.
security-review
Security Code Review: Reviews code for security vulnerabilities including authentication (OAuth2, JWT), authorization (RBAC, roles), API security, data protection, payment security, and common attack vectors. Use whenever the user wants a security review, penetration test analysis, threat model, or mentions OAuth2…
testing-api-authentication-weaknesses
Tests API authentication mechanisms for weaknesses including broken token validation, missing authentication on endpoints, weak password policies, credential stuffing susceptibility, token leakage in URLs or logs, and session management flaws. The tester evaluates JWT implementation, API key handling, OAuth flows, and…
security-hardening
Use when writing code that handles user input, auth, sessions, or external data. Covers OWASP prevention patterns. Do NOT use for general code quality or performance — see dedicated skills.
JWT Security Testing
Comprehensive JWT token security testing including signature verification, expiration checks, algorithm confusion attacks, and claim validation.