coordinate-external-ag…
Coordinate independently operated external agents through durable handoffs. Use when work crosses hosts, sessions, accounts,…
@gaelic-ghostInstall SkillDevelopment
Skill
/operate-agentic-security-tools
Operate security tools through an AI agent with explicit authority boundaries. Use when an agent may invoke CLIs, GUI apps, browser automation, MCP servers, scanners, sandboxes, or containment actions with constrained approvals and logging.
Claude Code
$ npx -y skills add gaelic-ghost/socket --skill operate-agentic-security-tools --agent claude-code
Codex
$ npx skills add gaelic-ghost/socket --skill operate-agentic-security-tools -a codex -y
Cursor
$ npx skills add gaelic-ghost/socket --skill operate-agentic-security-tools -a cursor -y
Gemini CLI
$ npx skills add gaelic-ghost/socket --skill operate-agentic-security-tools -a gemini-cli -y
GitHub Copilot
$ npx skills add gaelic-ghost/socket --skill operate-agentic-security-tools -a github-copilot -y
OpenCode
$ npx skills add gaelic-ghost/socket --skill operate-agentic-security-tools -a opencode -y
Windsurf
$ npx skills add gaelic-ghost/socket --skill operate-agentic-security-tools -a windsurf -y
SKILL.md
operate-agentic-security-tools.SKILL.mdname: operate-agentic-security-tools
description: Operate security tools through an AI agent with explicit authority boundaries. Use when an agent may invoke CLIs, GUI apps, browser automation, MCP servers, scanners, sandboxes, or containment actions with constrained approvals and logging.
Operate Agentic Security Tools
Overview
Give the agent only the authority needed for the current security step and keep tool output reproducible. Separate discovery, active testing, exploit validation, containment, and remediation into visible decisions.
Read [references/agent-tool-controls.md](references/agent-tool-controls.md) for the preflight record and control checklist.
Workflow
1. Define the tool's job.
- State the security question, expected input/output, target, and why this tool is appropriate.
- Prefer read-only or offline operation when it can answer the question.
2. Discover capability before use.
- Record source, installed path or remote service, version, supported formats, privileges, network behavior, telemetry, and output location.
- Treat missing tools or unusable integrations as results; do not invent output.
3. Minimize authority.
- Limit readable/writable paths, target list, network destinations, credentials, environment variables, device access, and execution duration.
- Use temporary scoped credentials and disposable environments when credentials are unavoidable.
4. Gate consequential actions.
- Require an operator decision before active probing, exploit execution, persistence changes, credential access, security-control changes, destructive operations, production writes, or third-party uploads.
- Display the exact target and likely effect before approval.
5. Preserve evidence.
- Record commands or UI actions, configuration, timestamps, exit status, raw output, tool errors, and transformations.
- Validate high-impact findings with an independent observation or smallest safe reproduction.
6. Clean up and verify.
- Remove temporary mounts, ports, tokens, sessions, files, rules, and isolated environments.
- Report what remains installed, running, reachable, or retained.
Guardrails
- Do not grant broad host or cloud access merely to reduce approval prompts.
- Do not let an agent expand active-test scope from discovered targets.
- Do not treat an MCP server, GUI automation layer, or tool plugin as a trust boundary.
- Do not obscure failures behind a synthesized security conclusion.
Read more
name: operate-agentic-security-tools description: Operate security tools through an AI agent with explicit authority boundaries. Use when an agent may invoke CLIs, GUI apps, browser automation, MCP servers, scanners, sandboxes, or containment actions with constrained approvals and logging.
Operate Agentic Security Tools
Overview
Give the agent only the authority needed for the current security step and keep tool output reproducible. Separate discovery, active testing, exploit validation, containment, and remediation into visible decisions.
Read [references/agent-tool-controls.md](references/agent-tool-controls.md) for the preflight record and control checklist.
Workflow
1. Define the tool's job.
- State the security question, expected input/output, target, and why this tool is appropriate.
- Prefer read-only or offline operation when it can answer the question.
2. Discover capability before use.
- Record source, installed path or remote service, version, supported formats, privileges, network behavior, telemetry, and output location.
- Treat missing tools or unusable integrations as results; do not invent output.
3. Minimize authority.
- Limit readable/writable paths, target list, network destinations, credentials, environment variables, device access, and execution duration.
- Use temporary scoped credentials and disposable environments when credentials are unavoidable.
4. Gate consequential actions.
- Require an operator decision before active probing, exploit execution, persistence changes, credential access, security-control changes, destructive operations, production writes, or third-party uploads.
- Display the exact target and likely effect before approval.
5. Preserve evidence.
- Record commands or UI actions, configuration, timestamps, exit status, raw output, tool errors, and transformations.
- Validate high-impact findings with an independent observation or smallest safe reproduction.
6. Clean up and verify.
- Remove temporary mounts, ports, tokens, sessions, files, rules, and isolated environments.
- Report what remains installed, running, reachable, or retained.
Guardrails
- Do not grant broad host or cloud access merely to reduce approval prompts.
- Do not let an agent expand active-test scope from discovered targets.
- Do not treat an MCP server, GUI automation layer, or tool plugin as a trust boundary.
- Do not obscure failures behind a synthesized security conclusion.
10200 skills5 MCP
Stars on GitHub
Momentum
- stars in total
- 10
Other skills on socket.
@gaelic-ghostInstall Skillcoordinate-worktrees-a…
Assign worktree, branch, write, validation, integration, and cleanup ownership before parallel repository work. Use when a worker…
@gaelic-ghostInstall Skilldesign-agent-automatio…
Design framework-neutral agent and automation workflows before implementation. Use when choosing between Codex app automations,…
@gaelic-ghostInstall Skilldesign-agent-eval-work…
Design evaluation workflows for agent, skill, prompt, and automation behavior before implementation. Use when choosing eval…
@gaelic-ghostInstall Skilldesign-n8n-agent-workf…
Design safe n8n workflows with deterministic routing, credentials, idempotency, recovery, local-model checks, drafts, and exact…
@gaelic-ghostInstall Skillorchestrate-agent-work
Coordinate bounded worker tasks with a launch envelope, report-back, escalation, and synthesis contract. Use before spawning,…
@gaelic-ghostInstall SkillMore skills from other plugins.
Auto-invoked
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…
@obraInstall Skillask-matt
Ask which skill or flow fits your situation. A router over the skills in this repo.
@mattpocockInstall SkillAuto-invoked
Questions about operate-agentic-security-tools.
- Which coding agents can use operate-agentic-security-tools?
- operate-agentic-security-tools installs in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI, using each agent's flag shown on this page. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.