a2a-security-review
Review agent-to-agent (A2A) / multi-agent-system trust: peer identity and authentication, message integrity, capability-negotiation trust, and delegation-chain…
One or two sentences naming the SITUATION, INPUTS, and OUTCOME so Claude knows exactly when to fire this skill. This text is always in context — be specific but tight. Example: "Assess an API endpoint against the OWASP API Top 10 and produce a ranked findings table. Use when
$ npx -y skills add jassics/awesome-claude-security --skill example-skill --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/example-skillContext preview
The summary Claude sees to decide when to auto-load this skill.
One or two sentences naming the SITUATION, INPUTS, and OUTCOME so Claude knows exactly when to fire this skill. This text is always in context — be specific but tight. Example: "Assess an API endpoint against the OWASP API Top 10 and produce a ranked findings table. Use when
name: example-skill description: >- One or two sentences naming the SITUATION, INPUTS, and OUTCOME so Claude knows exactly when to fire this skill. This text is always in context — be specific but tight. Example: "Assess an API endpoint against the OWASP API Top 10 and produce a ranked findings table. Use when reviewing a REST/GraphQL API for authz, rate-limiting, or schema-abuse issues."
State what "done" looks like in one line.
1. Establish scope and gather inputs. 2. Work the methodology — reference the relevant framework by name (OWASP, MITRE ATT&CK, STRIDE, MASTG, CIS...). For long checklists, read `reference.md`. 3. Validate findings; remove false positives. 4. Rank by severity/risk.
Produce a concrete artifact and say its format here, e.g. a findings table with columns: ID · Title · Severity · Evidence · Remediation. For reports or diagrams, defer to `security-reporting` / `security-diagramming`.
Keep framing defensive and authorized. Don't fabricate evidence.
A Claude Code plugin marketplace for the full cybersecurity & GenAI-security lifecycle — from recon and threat modeling to detection engineering, GRC, and CISO-level strategy. A pentester knows which OWASP test bends a broken-access-control endpoint.
Repo: jassics/awesome-claude-security
Review agent-to-agent (A2A) / multi-agent-system trust: peer identity and authentication, message integrity, capability-negotiation trust, and delegation-chain…
Test the agent execution harness/runtime itself — LangChain/LangGraph, AutoGen, CrewAI, custom ReAct-style loops, or computer-use/browser-use agents — for…
Assess an autonomous / tool-using AI agent for security end-to-end: tool privileges, autonomy and approval boundaries, excessive agency, memory/state…
Test what an AI agent will actually do without human confirmation, including under injected-goal / prompt-injection scenarios, to validate its autonomy and…
Review the security of MCP (Model Context Protocol) servers/clients an agent uses: server trust tier, tool/resource description and result poisoning,…
Inventory the tools/functions an AI agent can call and audit their privileges, side effects, and approval requirements to find excessive-agency and…