aaf-acc-implementation

Implement Agent Control Contracts with a YAML template for workflow governance.

Updated Feb 17, 2026

Search Tags:#workflow #security #governance #policy #agentic #acc

Ready to run

npx skills add https://github.com/AgenticAF-Community/FrameworkCore --skill aaf-acc-implementation

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: aaf-acc-implementation
Source: https://github.com/AgenticAF-Community/FrameworkCore/tree/main/tools/skills/aaf-acc-implementation
Command: npx skills add https://github.com/AgenticAF-Community/FrameworkCore --skill aaf-acc-implementation

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides clear guidance and a template for implementing Agent Control Contracts (ACCs), ensuring workflows operate within defined governance, security, and budget constraints.

Core Features & Use Cases

ACC Definition: Offers a comprehensive template for defining ACCs, covering autonomy, tool usage, budgets, and definition of done.
Architectural Placement: Explains where ACCs fit within the Agentic Architecture Framework, emphasizing their role in the governance layer.
ACC vs AGENTS.md: Differentiates ACCs from agent operating instructions, clarifying their distinct purposes and authorities.
Use Case: When designing a new agentic workflow, use this skill to create a robust ACC that specifies exactly what tools the agent can use, its budget, and the verifiable conditions for task completion.

Quick Start

Use the aaf-acc-implementation skill to generate a comprehensive ACC template for a new workflow.

Frequently Asked Questions about aaf-acc-implementation

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

FAQPage Schema

How do I enforce security and budget constraints for agentic workflows?▼

An Agent Control Contract (ACC) governs agentic workflows by defining their autonomy, tool scope, budgets, and definition of done. It operates within the governance layer to enforce security and policy constraints.

What is the difference between an Agent Control Contract and AGENTS.md?▼

An Agent Control Contract (ACC) defines governance constraints like budgets and tool scope, whereas AGENTS.md provides operational instructions for agent behavior. The ACC holds architectural authority over workflow limits.

How do I create a governance policy template for an autonomous agent?▼

You create a governance policy template by defining a YAML Agent Control Contract (ACC) that specifies workflow autonomy, tool permissions, budgets, and evidence requirements for task completion.

Where does workflow governance fit within the agentic architecture framework?▼

Workflow governance fits within the governance layer of the Agentic Architecture Framework. Agent Control Contracts (ACCs) operate here to specify allowed tools and verifiable completion conditions.

Can I define verifiable completion conditions for agentic workflows?▼

Yes, you define verifiable completion conditions by specifying a definition of done and evidence requirements within the Agent Control Contract (ACC) YAML template, ensuring tasks meet governance criteria.