secure-development-lifecycle
Secure SDLC phases, security requirements, secure coding practices, and security testing integration for the CIA platform
Your agent can do more. Find the skill that makes it happen.
Find your next superpower If you are an agent, refer to our llms.txt for full access.Secure SDLC phases, security requirements, secure coding practices, and security testing integration for the CIA platform
Hack23 secure development policy enforcement, SAST/DAST integration, dependency scanning, and code signing practices
Security audit orchestrator for agent skills — scans for prompt injection, data exfiltration, credential theft, supply chain risks, and instruction hierarchy violations before any skill is installed, created, improved, or read from a GitHub repo. Load when creating skills from external sources, when improve-skills reads from GitHub repos, when research-skill fetches community SKILL.md files, when …
Content sanitization and hidden-content detection for agent skill security. Scans markdown, HTML, and text for visually hidden but agent-readable attacks: CSS-hidden text (display:none, color:white, font-size:0, opacity:0), HTML comments with instructions, collapsible details sections, zero-width unicode, homoglyphs, misleading links, and inline HTML in markdown. Enforces mandatory sanitization be…
Security checks for repository ingestion — scans repos for poisoned examples, dependency and supply-chain attacks, file/path traversal, format-based attacks, and enforces quarantine-before-commit. Load as part of the secure- skill sequence whenever an agent reads, ingests, or learns from a GitHub repository. Also load when the user asks to check a repo for poisoned code, scan dependencies, verify…
Runtime security for agent skills — prevents state corruption, skill overwrite attacks, denial of service, and enforces provenance tracking and no-go repo management. Load as part of the secure- skill sequence whenever an agent processes external content or writes to the skill store. Also load when the user asks to check for state corruption, prevent skill overwrite, manage no-go repos, check pro…
Follows Trail of Bits' five-step secure development workflow. Runs Slither, checks upgradeability, ERC conformance, and token integration, creates security diagrams, documents properties for fuzzing or verification, and reviews areas requiring manual analysis.
Secures new S3 buckets and audits existing buckets for security findings. Covers access control, encryption, logging, monitoring, and remediation of bucket misconfigurations.
read-only security audit. Primary owner: secrets, OWASP, CVE and PII findings. Do not use for: security remediation. Use when this role is selected by the Agent-Vorcl-Flow router.
Review code for security problems; scan for vulnerabilities, secrets, dependency and prompt risks. Use when: asked whether code is safe to ship, even one small handler.
Create security architecture diagrams using PlantUML syntax with identity, encryption, firewall, and compliance stencil icons. Best for IAM flows, zero-trust models, encryption pipelines, and threat detection architectures.
Provides a security remediation workflow for Flows apps and features handling credentials, user input, or external data. Covers injection, XSS, secrets, authentication, authorization, sensitive data, CORS, CSP, and dependency audits.
Skills give your agent reusable instructions for a specific job. Pick one, read what it does, and bring it into your workflow.
A name only tells half the story. Search the full description and instructions to find the right fit.
Read the skill, visit its source, and see exactly what you’re adding to your agent.
Copy the install command from a skill page and run it in your project.
npx skillycli add owner/repo --skill name