design-paradigms
claudeModern OOP, functional, structural, SQL, API, Docker, cloud, and React design paradigms with code examples.
12 skills
Backend, frontend, network, system, database, and dependency/supply-chain security scanning checklists.
Plugin security-scanning from marketplace engineering-standards-marketplace in shah-arnav3/eng_standards-marketplace-claudecode. Commands read from the repo's manifest — 6 days ago.
backend-securityBackend and application-layer security vulnerability scanning — injection flaws, broken authentication/authorization, insecure deserialization, SSRF, business logic flaws, and secrets management, aligned to OWASP Top 10 / ASVS. Use whenever reviewing backend/API code for security issues, designing a
database-securityDatabase-layer security vulnerability scanning — access control and least privilege, encryption at rest, backup security, audit logging, and data minimization/PII handling. Use whenever reviewing database configuration, access grants, encryption settings, or the user mentions database security, data
dependency-auditDependency and supply-chain security auditing — vulnerability scanning of third-party packages, lockfile integrity, transitive dependency risk, license compliance, and supply-chain attack patterns (typosquatting, compromised maintainers). Use whenever reviewing project dependencies, package.json/req
frontend-securityFrontend and client-side security vulnerability scanning — XSS, CSRF, clickjacking, insecure storage of tokens, content security policy, and third-party script risk. Use whenever reviewing frontend/client-side code for security issues, working with cookies/localStorage/tokens in the browser, or the
network-securityNetwork-layer security vulnerability scanning — TLS configuration, firewall and segmentation rules, exposed ports/services, DNS security, and API gateway/rate-limiting posture. Use whenever reviewing network architecture, firewall/security group rules, TLS configuration, or the user mentions network
system-securitySystem and host/OS-level security vulnerability scanning — least-privilege OS accounts, container hardening, patch management, filesystem permissions, and secure defaults for compute infrastructure. Use whenever reviewing server/container/OS hardening, Dockerfiles, deployment configuration, or the u
Modern OOP, functional, structural, SQL, API, Docker, cloud, and React design paradigms with code examples.
12 skills
Concurrency, testing, git workflows, code quality, debugging, scoped changes, documentation, performance, observability, and debloating.
10 skills
Seven-agent delivery pipeline with a /ship orchestrator and a human-approval gate on deploys and rollbacks.
1 skill · 7 agents · hooks
Token-efficient habits, per-task model and effort selection, session memory, docs-first discipline, autonomous execution, and structured work reports for Claude Code.
6 skills
Harness-native ECC operator layer - 71 agents, 314 skills, 98 legacy command shims, reusable hooks, rules, selective install profiles, and production-ready workflows for Claude Code, Codex, OpenCode, Cursor, and related agent harnesses
200 skills · 98 commands · 71 agents · 1 MCP server · hooks
Security review for Claude-generated code. Pattern-based warnings on edits, LLM-powered diff review on Stop, and an agentic commit reviewer that catches injection, XSS, SSRF, hardcoded secrets, and 25+ other vulnerability classes.
hooks
Cross-installation agent federation with zero-trust security, PII-gated data flow, and compliance-grade audit trails
3 skills · 1 command · 1 agent
Install the "AAS Security Engineer" workflow plugin from Agentic Awesome Skills.
12 skills
Duende development skills and agents for Claude Code — covering OAuth/OIDC protocols, IdentityServer, token management, ASP.NET Core authentication/authorization, BFF patterns, and secure identity architecture
24 skills · 2 agents
SAST analysis, dependency vulnerability scanning, OWASP Top 10 compliance, container security scanning, and automated security hardening
5 skills · 3 commands · 2 agents
This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.