agent-harness-design

Design agent harnesses with risk taxonomies, permission decision objects, and structured event models.

140|23|Updated Mar 28, 2026
One-click install
npx skills add https://github.com/AnastasiyaW/codex-claude-code-config --skill agent-harness-design-anastasiyaw
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agent-harness-design
Source: https://github.com/AnastasiyaW/codex-claude-code-config/tree/main/skills/agent-harness-design
Command: npx skills add https://github.com/AnastasiyaW/codex-claude-code-config --skill agent-harness-design-anastasiyaw

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Building robust agent harnesses is complex and prone to failure; this skill provides the architectural patterns and operational checklists needed to ensure agent systems are observable, secure, and predictable.

Core Features & Use Cases

  • Risk & Permission Taxonomy: Standardizes how tools are classified and how permissions are decided at runtime.
  • Operational Reference Sheets: Provides 11 specialized guides covering budgets, evals, event models, and approval records.
  • Use Case: Use this when architecting a new Agent SDK application, custom orchestrator, or MCP server to ensure you have the necessary guardrails and observability traces in place before deployment.

Quick Start

Load the agent-tool-design reference to review the risk taxonomy and permission decision object for your new agent project.

Frequently Asked Questions about agent-harness-design

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

FAQPage Schema
How do I design an observable and safe agent harness?

Agent harnesses need risk taxonomies, permission decision objects, and structured event models to establish security boundaries and budget enforcement. This framework provides architectural patterns and 11 operational reference guides to ensure predictable, observable agent systems.

What is a permission decision object in agent architecture?

A permission decision object in agent architecture standardizes how tools are classified and how runtime permissions are decided. It serves as a core component of the risk taxonomy, ensuring safe guardrails are in place before agent deployment.

How do I implement budget enforcement for custom agent orchestrators?

Budget enforcement for custom agent orchestrators is implemented using structured event models and operational reference sheets. This framework satisfies requirements for tracking resource consumption and applying standardized evaluation categories to agentic systems.

Can I use this agent harness framework for an MCP server?

Yes, this framework applies directly to developing MCP servers requiring rigorous observability and security boundaries. It provides the necessary architectural patterns to implement approval record schemas and budget enforcement before deployment.

What's the best way to structure evaluation categories for agentic systems?

The best way to structure evaluation categories for agentic systems is to use standardized operational reference sheets. This framework provides 11 specialized guides covering evals, event models, and approval records to ensure comprehensive system assessment.

When do I need structured event models for agent SDK applications?

Structured event models are needed for agent SDK applications when you require rigorous observability traces and security guardrails. They enable budget enforcement, approval record schemas, and standardized evaluation before deploying custom orchestrators.