Skip to content
Back to skills

Agents

ASecurity

Every Claude Code and Codex agent in one list, and share each host's own agents with the other — list, sync now, stop or resume sharing one agent, reset an edited copy

  • 2 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added September 25, 2026
ai-agentsshell

Works with

  • claude code
  • cli
  • mcp

Security analysis

A100/100

Scanned October 6, 2026

npx -y skills add zzoretich/AgenticOS-Workbench --skill agents --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Agents?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Agents
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/zzoretich-agents/badge)](https://www.skillsdirectory.com/skills/zzoretich-agents)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: agents
description: Every Claude Code and Codex agent in one list, and share each host's own agents with the other — list, sync now, stop or resume sharing one agent, reset an edited copy
---
<!-- generated by tools/build-codex-plugin.js from plugin/; edit the source there, not this file -->

> Host: Codex CLI, through the `agenticos` plugin. Invoke as `$agenticos:agents`. `<plugin root>` is the plugin's folder, two levels above the folder that holds this SKILL.md; the `aos` launcher is `<plugin root>/bin/aos`. The tools of the `agenticos` MCP server are named `mcp__agenticos__<tool>`.

Run `aos agents the text the user wrote after `$agenticos:agents`` in the shell (fallback: `sh "<plugin root>/bin/aos" agents the text the user wrote after `$agenticos:agents``); with no arguments run `aos agents list`. Relay the output; every verb is a passthrough.

How sharing works: each host keeps its own agents, in its own format. Claude Code reads `~/.claude/agents/<name>.md` (frontmatter, and the body is the prompt); Codex reads `~/.codex/agents/<name>.toml` (`name`, `description`, `developer_instructions`). With both hosts enabled, AgenticOS writes a translated copy of each one into the other host's folder at the end of every session, so an agent made in one host is in the other by its next session. The name, the description and the prompt carry over; an agent whose tools cannot write runs read-only on the other host; the model does not carry over (each host uses its own default). Plugin agents and roles declared in Codex's `config.toml` are listed but never copied.

- `list [--all]`: the first line is the summary; relay it, then the table. Columns: the agent (marked read-only when it is), how to reach it in Claude Code (`@agent-<name>`) and in Codex (its name), where it comes from, and its status. `--all` adds plugin agents and `config.toml` roles.
- `sync [--dry-run]`: share now instead of waiting for the session to end. `--dry-run` prints what it would write or remove and changes nothing.
- `exclude <name>` / `include <name>`: stop or resume sharing one agent (kept in `brain/config.json` under `agents.exclude`). Suggest it when Codex carries agents the user never uses there: every Codex agent's description is sent on every Codex turn.
- `reset <name>`: a copy that was edited by hand is never overwritten. This deletes that copy, and the edit with it, so the next sync writes it fresh. Say that plainly and ask before running it.

Statuses worth one line each: `universal` = on both hosts; `pending` = sharing is off or only one host is enabled (the summary says which); `differs` = a different agent of the same name exists on each host and both are left alone; `edited` = a copy was edited by hand (edit the source instead, or `reset`); `excluded` = not shared on purpose; `invalid` = cannot be shared as written (the reason follows the table: a missing name, description or prompt, or a name the other host already uses for a built-in agent such as `explorer` or `general-purpose`); `listed` = a plugin agent or a `config.toml` role.

Using an agent: in Claude Code, ask for it by name, mention `@agent-<name>`, or start a session as it with `claude --agent <name>`. In Codex, ask for it by name ("have reviewer check this diff") and Codex spawns it. The Agents tab in the Workbench shows the same list, with buttons that start a Claude Code or Codex session with the agent.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.