---
title: "agent-operating-model"
description: "Agent capabilities for independently selectable repository standards, with optional adoption assets."
canonical: https://agentpluginsdirectory.com/plugins/agent-operating-model
last-updated: 2026-11-13
---

# agent-operating-model
Agent capabilities for independently selectable repository standards, with optional adoption assets.
## Package we checked
The manifest we fetched is dist/plugins/agent-operating-model/plugin.json in HarleyBartles/agent-asset-marketplace. The plugin root is the directory that holds that file. Its $schema is https://agent-plugins.org/schemas/1.0.0/plugin.schema.json. The manifest lists 17 skills and no MCP servers. Extension keys: com.openai.
- Slug: agent-operating-model
- Publisher: Harley Bartles
- Repository: https://github.com/HarleyBartles/agent-asset-marketplace
- Manifest: dist/plugins/agent-operating-model/plugin.json
- Version: 1.0.0
- License: MIT
- Category (editorial): other
- Skills: 17 (agent-doctrine-contracts, agents-routing, command-bus, completed-artifact-custody, contribution-entrypoint, gitflow, playbook-composition, python, repo-agent-assets, repo-composition, repo-standards, repository-validation, review-entrypoint, runbook-composition, semver, tracked-repo-hooks, unslop)
- MCP servers: 0
- Stars: 0
- Repository created: 2026-06-04
- Repository last pushed: 2026-10-08
- Publisher type: User
- Listing: https://agentpluginsdirectory.com/plugins/agent-operating-model
- Schema: https://agent-plugins.org/schemas/1.0.0/plugin.schema.json

## What agent-operating-model does, in the publisher's words

This plugin makes first-party repository operating capabilities available to agents and publishes selectable standard definitions.

- provenance and source mapping in SOURCE.md
- bundle inventory in references/bundle-manifest.json
- Plugin availability provides capabilities and a menu of standards. It does not adopt any standard for a consumer.
- Each consumer chooses the standards it wants, implements them in its own repository, and self-certifies against the requirements it pins.
- A standard skill carries its current definition, adoption and assessment guidance, and any optional starter assets. It may supply no deployable asset.
- Repositories may take, adapt, replace, or omit optional starters. Adopted files and tools become repository-owned; matching AOM starter bytes is not a compliance requirement.

Skills are installed from the Codex plugin roots under dist/plugins/agent-operating-model/skills/ /. The plugin makes authoring capabilities available. A repository adopting a standard records its immutable source commit and definition path separately from plugin refresh, maintains a readable certification, and routes agents to those records.

From the project README, punctuation lightly normalized. Full text: https://raw.githubusercontent.com/HarleyBartles/agent-asset-marketplace/HEAD/dist/plugins/agent-operating-model/README.md

## Skills

- agent-doctrine-contracts: Use when adopting or assessing agent-facing doctrine and contracts, their repository locations, quality, or routes.
- agents-routing: Use when creating, reviewing, or certifying repository AGENTS.md routers and their scoped guidance routes.
- command-bus: Use when creating, reviewing, or changing a repository command bus and its named targets.
- completed-artifact-custody: Use when a repository adopts completed-artifact-custody, or explicitly asks for its lifecycle, to assess plans, specifications, roadmaps, or checkpoints.
- contribution-entrypoint: Use when creating, assessing, or maintaining a repository's root CONTRIBUTING.md contributor guidance.
- gitflow
- playbook-composition: Use when adopting, authoring, routing, assessing, or updating repository concern-based playbooks.
- python: Use when writing, reviewing, or debugging Python code and the task calls for idiomatic language patterns, concurrency, testing, or type-safety guidance.
- repo-agent-assets: Use when changing repository plugin subscriptions or the custody boundary for repository-authored skills.
- repo-composition: Use when creating, changing, or assessing repository runbooks and playbooks under their explicitly adopted standards.
- repo-standards: Use when aligning repository operating-model standards, assessing adoption, or deciding which focused standard owns a requested change.
- repository-validation: Use when defining or diagnosing focused checks, complete repository gates, apply-check convergence, diagnostics, or validation evidence.
- review-entrypoint: Use when creating, assessing, or maintaining a repository's root REVIEW.md code review guidance.
- runbook-composition
- semver
- tracked-repo-hooks
- unslop

Descriptions come from the frontmatter of each SKILL.md, punctuation lightly normalized.
