Skill Detail

Design and Audit Agent Harnesses with Agents Best Practices

Use Agents Best Practices when an agent should produce concrete harness designs, permission models, memory plans, eval gates, or production-readiness audits.

Templates & WorkflowsMulti-Framework
Templates & Workflows Multi-Framework Security Reviewed
⭐ 2.2k GitHub stars
COPY SKILL INSTRUCTIONS (OPTIONAL)
npx skills add agentskillexchange/skills --skill design-and-audit-agent-harnesses-with-agents-best-practices Copy
Uses the third-party skills CLI, not an ASE-owned installer. Check your agent’s compatibility. This copies instructions; complete the upstream tool setup below separately.
At a glance
Tools required
A compatible agent skill runtime such as Codex skills, Claude Code skills, or the skills CLI; local access to the installed SKILL.md and references directory.
Install & setup
Install as a portable Agent Skill. With the skills CLI, run npx skills add DenisSergeevitch/agents-best-practices -g. For Codex, clone the repo into CODEX_HOME/skills/agents-best-practices or $HOME/.codex/skills/agents-best-practices. For Claude Code, clone it into $HOME/.claude/skills/agents-best-practices or a project .claude/skills/agents-best-practices directory.
Author
DenisSergeevitch
Publisher
Open Source
Last updated
Aug 10, 2026
Quick brief

Use Agents Best Practices when an agent/operator needs a portable skill for designing or reviewing agentic harnesses. The operator installs the skill into a supported agent skill directory, then invokes it to generate MVP blueprints, audit existing harnesses, design tool permissions and connectors, plan context and memory behavior, define workflow orchestration, and set eval or launch gates.

How it works

What this skill actually does

Invoke this instead of browsing generic best-practice articles when the output needs to become a concrete implementation or review plan for an agent runtime. It is useful when the user asks for a safe agent architecture, a permission model, a harness audit, a production-readiness checklist, or a provider-neutral view of agent loop design.

The scope boundary is provider-neutral agent harness design and audit guidance packaged as an Agent Skill. This is not an SDK, product, generic documentation card, or broad framework listing; it is a repeatable workflow for turning agent architecture concerns into operational plans and checks.