agentic-sdlc-controls — Claude Code skill: what it does and setup
Audits development pipelines where AI agents commit, run tests, or deploy code. It maps credentials and defines hard boundaries for irreversible actions.
npx skills add securityskills/skills --skill agentic-sdlc-controls -a claude-codeWhat agentic-sdlc-controls does
An autonomous coding agent executes work at machine speed using the credentials given to it. This skill focuses on hard system boundaries rather than model alignment. The process starts by cataloging agent reach: service account identity, repository permissions, reachable staging or production environments, runtime secrets, and outbound network traffic.
Actions split strictly by reversibility. Modifying source files or running test suites can proceed autonomously. Schema migrations, publishing packages, and branch merges require mandatory human approvals. Operations like data deletion or credential rotation stay completely out of reach. Prompts alone cannot stop bad behavior. Runtime hooks and immutable guardrails must enforce every boundary.
The review also checks how the pipeline handles untrusted data. External issue text, pull request summaries, or documentation can carry hidden instructions. Teams needing audit-ready evidence can combine this review with the ai-change-evidence skill.
What it helps with
- Catalog all credentials, environments, and network paths reachable by an agent
- Separate safe reversible tasks from operations requiring human sign-off
- Block autonomous agents from executing destructive or irreversible commands
- Identify prompt injection paths across issue descriptions and external docs
Example prompts for the agent
- Audit our CI/CD pipeline permissions using agentic-sdlc-controls
- Check which actions our coding agent can run without human approval
- Map all runtime secrets exposed to the agent and recommend tighter scopes
How to install agentic-sdlc-controls
1Skills CLI (Vercel)
npx skills add securityskills/skills --skill agentic-sdlc-controls -a claude-code2Manually: put the files in place
~/.claude/skills/agentic-sdlc-controls/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/agentic-sdlc-controls/
1Skills CLI (Vercel)
npx skills add securityskills/skills --skill agentic-sdlc-controls -a codex2Manually: put the files in place
.agents/skills/agentic-sdlc-controls/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add securityskills/skills --skill agentic-sdlc-controls -a cursor2Manually: put the files in place
.cursor/skills/agentic-sdlc-controls/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install securityskills/skills agentic-sdlc-controls2Manually: put the files in place
.github/skills/agentic-sdlc-controls/SKILL.md1Skills CLI (Vercel)
npx skills add securityskills/skills --skill agentic-sdlc-controls -a gemini-cli2Platform CLI
gemini skills install https://github.com/securityskills/skills --path agentic-security/pipeline/agentic-sdlc-controlsManually: put the files in place
.devin/skills/agentic-sdlc-controls/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add securityskills/skills --skill agentic-sdlc-controls -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about agentic-sdlc-controls
How to install agentic-sdlc-controls in Claude Code?
Run npx skills add securityskills/skills --skill agentic-sdlc-controls -a claude-code. The skill definition will be stored at ~/.claude/skills/agentic-sdlc-controls/SKILL.md.
What does agentic-sdlc-controls do?
It provides a structured security audit for pipelines where AI agents write and deploy code. The review covers permission boundaries, credential exposure, and approval gates for irreversible actions.
Why does the skill insist on runtime enforcement over prompt instructions?
Prompts act as preferences that a confused or manipulated model can ignore. Runtime mechanisms like pre-action hooks and platform permission lists enforce hard boundaries that the agent cannot modify or bypass.