aaf-security

Apply the AAF Security pillar to design secure agentic systems.

Updated Feb 17, 2026
One-click install
npx skills add https://github.com/AgenticAF-Community/FrameworkCore --skill aaf-security
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aaf-security
Source: https://github.com/AgenticAF-Community/FrameworkCore/tree/main/tools/skills/aaf-security
Command: npx skills add https://github.com/AgenticAF-Community/FrameworkCore --skill aaf-security

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the critical need to design and implement robust security measures for agentic AI systems, mitigating risks associated with instruction manipulation, tool misuse, and data exfiltration.

Core Features & Use Cases

  • Boundary Controls: Enforces authentication, authorization, and rate limiting at all entry points.
  • Privilege Separation: Implements Master-Junior or Supervisor-gate patterns for constrained execution.
  • Tool Gateway: Mandates a single, non-bypassable gateway for all tool invocations, enforcing policy and budgets.
  • Prompt Injection Mitigation: Provides strategies to treat external content as hostile and enforce instruction hierarchy.
  • Use Case: When developing a new agent that interacts with external tools, use this skill to ensure all tool calls are validated, authorized, and operate under the principle of least privilege, preventing potential misuse or security breaches.

Quick Start

Use the aaf-security skill to review the security architecture for a new agent that will process user requests and interact with external APIs.

Frequently Asked Questions about aaf-security

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prevent prompt injection attacks in agentic AI systems?

Securing tool actuation in AI agents requires enforcing multi-layered controls including authentication, authorization, and a mandatory non-bypassable tool gateway. This gateway enforces policy and budgets while validating all tool calls.

How do I implement privilege separation for constrained agent execution?

Implementing privilege separation for constrained agent execution uses Master-Junior or Supervisor-gate patterns. These patterns enforce the principle of least privilege, preventing potential misuse or security breaches during tool interactions.

What is the best way to secure external API calls made by autonomous agents?

Securing external API calls made by autonomous agents is best achieved by mandating a single tool gateway with server-side validation. This ensures all invocations are authorized, rate-limited, and operate under least privilege.

Do I need a tool gateway for every agent that interacts with external tools?

A tool gateway is necessary for agents interacting with external tools to ensure all tool calls are validated and authorized. It provides a non-bypassable entry point enforcing policy, budgets, and server-side validation.