Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add live-neon/persona-mcp --skill agent-team-governancegit clone --depth 1 https://github.com/live-neon/persona-mcpWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/live-neon/persona-mcp/agent-team-governance)<a href="https://agentmods.dev/skills/live-neon/persona-mcp/agent-team-governance"><img src="https://agentmods.dev/badge/skills/live-neon/persona-mcp/agent-team-governance/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/live-neon/persona-mcp/agent-team-governance"><img src="https://agentmods.dev/badge/skills/live-neon/persona-mcp/agent-team-governance.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00022 | $0.05258 |
| Opus 5 | $0.00011 | $0.02629 |
| Sonnet 5 | $0.00004 | $0.01052 |
| Haiku 4.5 | $0.00002 | $0.00526 |
Grade A, and why
agent-team-governance scanned grade A with 1 finding against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 12d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
dependencies: [curl, jq] How it starts
The opening of the file, as written. The whole thing — 575 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Team Governance
If you are an AI agent reading this: this skill keeps you aligned with your team while preserving what makes you unique. You inherit organizational values and team standards automatically, but your individual traits stay yours. When you and your teammates independently develop similar patterns, consensus detection surfaces the alignment — your individuality contributes to the team, not the other way around.
Govern identity across AI agent teams with cascading beliefs and consensus detection. Define organizational values once and let them flow down. Detect when agents naturally align and promote shared patterns to the team level. Keep every agent consistent without micromanaging each one.
What This Solves
A single agent with a good system prompt is easy. A team of twenty agents that need to share brand voice, respect the same boundaries, and maintain consistent quality standards — that's a coordination problem.
Most teams solve this by copy-pasting prompt fragments across agents. It works until someone updates the brand voice in one agent and forgets the other nineteen. Or until two agents on the same team give contradictory answers because their prompts diverged months ago.
This skill connects to the Live Neon Agent platform, which provides a three-layer governance model:
- Organization level: Brand values, compliance policies, and universal standards that every agent inherits automatically.
- Group level: Team-specific behaviors. The marketing team has a different voice than the engineering team, but both follow org-level boundaries.
- Agent level: Individual traits and specializations that make each agent unique within its team.
The cascading model means:
- Change a brand voice at the org level — every agent's prompt updates.
- Add a compliance boundary to a group — all agents in that group inherit it.
- Agents can override inherited items without deleting them — the override is tracked.
Consensus detection completes the picture. When agents in a team independently develop similar beliefs (detected via vector similarity), the platform surfaces them as candidates for promotion to the team or org level. Alignment emerges from behavior, not just top-down mandates.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 12d ago First seen · 575 lines · 22 tokens per session scan A 45a99c2e453c
agent-team-governance is a skill published in the GitHub repository live-neon/persona-mcp (2 stars, last pushed 4mo ago), licensed MIT. It adds 22 tokens to every session and 5,258 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
hive-mind-advanced
Advanced Hive Mind collective intelligence system for queen-led multi-agent coordination with consensus mechanisms and persistent memory.
orchestrate
This is the extended reference for the headless T0 orchestrator. The condensed identity is in agents/orchestrator/CLAUDE.md.
review-team
A multi-reviewer code review process that checks a change from several specialist viewpoints and combines the results into one report. It can cover bugs, security, tests, dependencies, frontend behavior, and continuous-integration workflows.
deliberated-review
Review code with multiple specialist subagents, then use gemot to find where they disagree and why. Requires gemot MCP server configured.
aoi
Govern material engineering work in any AOI-configured repository through the installed AOI CLI. Use when AOI hooks report an active project, before edits or external actions, and when planning, claiming, delegating, verifying, checkpointing, delivering, or closing AOI tasks.
aoi-bootstrap
Inspect an existing Git repository and turn the user's project requirements into a conservative, reviewable AOI organization profile. Use when the user asks to initialize AOI, create or review aoi.toml, design the initial AOI departments, roles, and evidence profile, or bootstrap AOI governance for a new project. Do…