Agent Native Agent Skill
Make an out-of-session agent AgentOps-native via skills + ao CLI + CI, not hooks.
Install
one command, takes just this skill from the repositorynpx skills add https://github.com/majiayu000/claude-skill-registry --skill agent-nativeWhat comes with it
751 bytes besides the instructionWhat it tells the agent to use
found in the instruction textThe instruction itself
3 sections, as written by the author$agent-native — Make Out-of-Session Agents AgentOps-Native (Codex Native)
> Quick Ref: Run a Claude/Codex loop *outside* an interactive session (Managed Agent, Agent SDK, or self-hosted sandbox) under the same AgentOps guardrails — hooklessly. Guardrails = skills + the ao CLI + CI, never ported hooks. Bundle skills into the agent definition, expose ao as a callable tool so the loop self-bootstraps + self-validates, and gate the output through the SAME CI as interactive work.
Codex/NTM path
Codex (gpt-5.3-codex) has NO Managed Agents API, NO Workflow tool, NO Task subagent. It orchestrates via NTM (tmux pane swarms + agent-mail) + skills + the ao CLI + ssh to bushido. So an out-of-session Codex loop becomes AgentOps-native the same way: load the AgentOps skills, call ao session bootstrap / ao inject / ao validate directly (no MCP needed — Codex shells out), and gate outputs through CI (agent-output-validate.yml). ao does not wrap gc; a whole loop needing a mayor/refinery still routes through gc.
Instructions
Load and follow the skill instructions from the sibling SKILL.md — OR read skills/agent-native/SKILL.md in the host repo for the canonical specification. Honor the Critical Constraints: this is a reframe of "port hooks", NOT a hook revival; no skill fork (load the same skills/ files); Managed Agents are NOT ZDR (no holdout/PII in the agent definition); CI is the enforcement boundary, not the optional in-loop adapter.
Other skills for the same job
different authors, same section of the catalogue
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
Replace with description of the skill and when Claude should use it.
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
This skill should be used when the user wants to "create a skill", "add a skill to plugin", "write a new skill", "improve skill description", "organize skill content", or needs guidance on skill structure, progressive disclosure, or skill development best practices for Claude Code plugins.
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
Use when creating new skills, editing existing skills, or verifying skills work before deployment
How to use it
Take majiayu000/agent-native from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.