owner-boundary-triage

owner-boundary-triage is a skill for Claude Code, Codex from Gesondian/ai-collab-governance-skills. It costs 35 tokens per session (524 once invoked), scanned A, original, MIT.

A method for deciding which part of an AI-delivered system owns a failure. It distinguishes feature, shared capability, data, environment, and verification responsibilities.

In plain words
What is it for?
It is for tracing where a failure appears, identifying its mechanism, checking affected users or features, and assigning an owner only when the evidence supports it.
Why use it?
It prevents failures from being assigned to the wrong team or component when the evidence does not show who controls the cause.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit It is for tracing where a failure appears, identifying its mechanism, checking affected users or features, and assigning an owner only when the evidence supports it.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/gesondian/ai-collab-governance-skills/owner-boundary-triage
Install

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.

Any agent
npx skills add Gesondian/ai-collab-governance-skills --skill owner-boundary-triage
Clone the repo
git clone --depth 1 https://github.com/Gesondian/ai-collab-governance-skills

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for owner-boundary-triage

README.md
[![agentmods](https://agentmods.dev/badge/skills/gesondian/ai-collab-governance-skills/owner-boundary-triage/github.svg)](https://agentmods.dev/skills/gesondian/ai-collab-governance-skills/owner-boundary-triage)
Your own site
<a href="https://agentmods.dev/skills/gesondian/ai-collab-governance-skills/owner-boundary-triage"><img src="https://agentmods.dev/badge/skills/gesondian/ai-collab-governance-skills/owner-boundary-triage/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.

agentmods 80×15 button for owner-boundary-triage

Your own site · 80×15
<a href="https://agentmods.dev/skills/gesondian/ai-collab-governance-skills/owner-boundary-triage"><img src="https://agentmods.dev/badge/skills/gesondian/ai-collab-governance-skills/owner-boundary-triage.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 35 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 524 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00035 $0.00524
Opus 5 $0.00017 $0.00262
Sonnet 5 $0.00007 $0.00105
Haiku 4.5 $0.00003 $0.00052

Measured 12d ago against content hash 4b1f1fc31974, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

owner-boundary-triage scanned grade A with 0 findings 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.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/owner-boundary-triage/SKILL.md · 76 lines

How it starts

The opening of the file, as written. The whole thing — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Owner Boundary Triage

Core Principle

Owner conclusions require both reproduction breadth and mechanism attribution. A shared-looking source file is not proof that every consumer belongs to the shared owner.

Required Signals

  • Where the failure reproduces.
  • Where it does not reproduce.
  • Which mechanism appears responsible.
  • Which owner controls that mechanism.
  • Which consumers are affected.
  • Which evidence is missing.

Triage Flow

  1. Define the failing behavior in one sentence.
  2. Map reproduction breadth:
    • single route or surface,
    • multiple consumers of one capability,
    • all consumers of a shared capability,
    • data-source-specific,
    • environment-specific.
  3. Attribute mechanism:
    • feature composition,
    • shared component,
    • data schema,
    • permissions,
    • environment or harness,
    • acceptance wording.
  4. Assign owner only when breadth and mechanism agree.
  5. If they do not agree, return owner_boundary_unclear with the smallest next check.

Verdict Vocabulary

Verdict Use When
feature_owner Failure is isolated to a feature composition or route-specific integration.
shared_capability_owner Failure reproduces across consumers and mechanism is in the shared capability.
data_owner Failure depends on data schema, lifecycle, or seed shape.
environment_owner Failure depends on setup, harness, browser, network, or fixture availability.
verifier_owner Failure is in the evidence, receipt wording, or acceptance procedure.
owner_boundary_unclear Reproduction breadth or mechanism attribution is insufficient.

Output Contract

verdict:
failure_summary:
reproduction_breadth:
mechanism_attribution:
excluded_owners:
missing_checks:
next_owner:
return_gate:
return_owner_on_fail:

Common Mistakes

  • Assigning a shared owner because code lives in a shared folder.
  • Assigning a feature owner because the bug was first seen on one page.
  • Ignoring negative reproduction evidence.
  • Treating verifier wording mistakes as runtime defects.
  • Asking one owner to fix another owner's missing evidence.

Read the full file on GitHub · 76 lines

Changes

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.

  1. 12d ago First seen · 76 lines · 35 tokens per session scan A 4b1f1fc31974

Subscribe to this mod's changes

owner-boundary-triage is a skill published in the GitHub repository Gesondian/ai-collab-governance-skills (1 stars, last pushed 2mo ago), licensed MIT. It adds 35 tokens to every session and 524 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

interactive-debugging

Use this skill when debugging runtime behavior requires live data from the running app, temporary instrumentation, or hypothesis verification through logs. Trigger for async timeouts, stale or incorrect state updates, race conditions, event ordering bugs, intermittent failures, browser/client behavior that static…

denysdovhan/agents · 97 tokens

rust-async-patterns

Master Rust async programming with Tokio, async traits, error handling, and concurrent patterns. Use when building async Rust applications, implementing concurrent systems, or debugging async code.

FilippoDeSilva/skills · 39 tokens

bug-report-writer

Converts rough notes, casual descriptions, console errors, or quick observations into professional, complete bug reports — exported as a formatted Excel (.xlsx) file ready for Excel, Google Sheets, Jira, or Azure DevOps. Use this skill whenever the user mentions: "write a bug report", "log a bug", "report this issue"…

ShreyasBh02/AI-Skills-Collection · 186 tokens

log-to-bug-report-converter

Parses error logs, stack traces, and test failures into production-ready bug reports.

ShreyasBh02/AI-Skills-Collection · 25 tokens

agenttrace-session-audit

Audit local AI coding-agent sessions with agenttrace for cost, tool failures, latency, anomalies, health, diffs, and CI gates.

sickn33/agentic-awesome-skills · 34 tokens

agent-qa-result-triage

Triage failed Agent QA runs with MCP evidence, artifacts, logs, fixed failure categories, confidence, and actionable next steps.

sickn33/agentic-awesome-skills · 33 tokens