aaf-cross-cutting

Define agent context budgets and autonomy levels for governed operations.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the critical challenges of managing an agent's working memory (context) and controlling its operational freedom (autonomy) to ensure safety, efficiency, and predictability.

Core Features & Use Cases

  • Context Optimization: Design strategies for separating task-specific context from long-term memory, and implement context budgeting to prevent bloat and security risks.
  • Autonomy & Outcome Governance: Define clear levels of agent autonomy, establish rigorous "Definition of Done" criteria with verifiable acceptance checks, and implement budget enforcement and escalation protocols.
  • Use Case: When designing a customer support agent, use this Skill to define how much conversation history it can access per turn (context budgeting), set clear criteria for when a support ticket is considered resolved (Definition of Done), and specify when to escalate a complex issue to a human agent (escalation).

Quick Start

Use the aaf-cross-cutting skill to define the autonomy level and context budget for a new agent workflow.

Frequently Asked Questions about aaf-cross-cutting

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

FAQPage Schema
How do I manage agent context and autonomy to ensure safe operations?

Agent context optimization separates task-specific context from long-term memory and implements context budgeting to prevent bloat and security risks. This ensures safe and scalable agent operations by controlling information flow.

How do I set context budgeting limits for an agentic workflow?

Context budgeting limits are set by defining how much conversation history or working memory an agent can access per turn. This prevents context bloat and security risks while maintaining operational efficiency for the agentic workflow.

What is a Definition of Done criteria for autonomous agent governance?

A Definition of Done for autonomous agent governance establishes rigorous, verifiable acceptance checks that determine when a task is fully resolved. It ensures predictability by enforcing clear outcome criteria before an agent concludes its operation.

When should an autonomous agent escalate an issue to a human operator?

Autonomous agent escalation to a human operator should occur when a complex issue exceeds defined autonomy levels or budget constraints. Specifying escalation protocols during design ensures safe boundaries for operational freedom are maintained.

Does the Agentic Architecture Framework support defining multiple levels of agent autonomy?

The Agentic Architecture Framework supports defining multiple levels of agent autonomy to control operational freedom. It addresses design considerations for autonomy levels, budgets, and escalation behaviors to ensure safe and scalable operations.

What are the limitations of separating context vs memory in agentic design?

Separating context vs memory in agentic design requires careful context budgeting to prevent bloat and security risks. Limitations arise if task-specific context is not properly isolated from long-term memory, potentially degrading agent performance and predictability.