agent-ops-governance

Govern AI agent fleets through ownership, maintenance loops, cost measurement, and lifecycle classification.

Updated Jul 16, 2026
One-click install
npx skills add https://github.com/Cloud-Byte-Consulting/plugins --skill agent-ops-governance-cloud-byte-consulting
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agent-ops-governance
Source: https://github.com/Cloud-Byte-Consulting/plugins/tree/main/ai-operations/skills/agent-ops-governance
Command: npx skills add https://github.com/Cloud-Byte-Consulting/plugins --skill agent-ops-governance-cloud-byte-consulting

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Organizations running AI agents face unclear ownership, climbing token costs, prototype sprawl, and vendor renewals negotiated without leverage. This Skill provides an operating model for managing agents like managed labor rather than shelfware. ## Core Features & Use Cases - Ownership and maintenance: Assign one accountable owner per consequential agent and run a seven-surface maintenance loop (job, diet, memory, tools, reach, proof, value) ending in an explicit keep/change/pause/retire decision. - Cost and licensing discipline: Measure token usage in three fidelity lanes, read budget burn as signal, score vendor licenses against nine fairness traits, and compute cost per completed unit of work. - Prototype lifecycle management: Classify tools on a four-state ladder (personal, team beta, supported, customer-facing) with promotion and demotion triggers plus a scheduled demotion audit. - Use Case: Before a major AI vendor renewal, inventory all agents, assign ownership cards, run maintenance passes with replay packs, and renegotiate the contract using cost-per-resolved-case data. ## Quick Start Inventory every agent touching real data in my organization, assign an owner to each, and run the first maintenance pass on the highest-cost agent.

Frequently Asked Questions about agent-ops-governance

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

FAQPage Schema
How do I assign ownership for AI agents in my organization?

Assign one accountable person per consequential agent using a minimal ownership card: owner name, one-sentence purpose, blast radius, and review cadence. A committee or team alias does not count as an owner, and unclaimed agents are retirement candidates.

How do I measure AI agent token costs accurately?

Log usage in three separate fidelity lanes: exact token counts, measured activity counts, and labeled estimate bands. Never sum across lanes, and evaluate spend against completed units of work rather than raw token volume.

What is the seven-surface agent maintenance loop?

It walks seven harness surfaces: job, diet, memory, tools, reach, proof, and value. Each pass inspects the last ten runs, replays 5-20 known cases, deletes before adding rules, and ends with an explicit keep, change, pause, or retire decision.

When should I retire or demote an internal AI prototype?

Demote a beta to personal when usage falls to one person or the backup owner disappears, and demote supported tools that lose their owner or stop justifying support cost. Run a scheduled demotion audit, since this pass is the one most teams skip.

What should I ask vendors before an AI license renewal?

Ask what current seats already cover, how the usage meter works including failed versus completed work, and whether seats can be reduced when agents absorb volume. Compute cost per completed unit of work and negotiate before the workflow becomes mission-critical.