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 Gesondian/ai-collab-governance-skills --skill owner-boundary-triagegit clone --depth 1 https://github.com/Gesondian/ai-collab-governance-skillsWrote 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/gesondian/ai-collab-governance-skills/owner-boundary-triage)<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.
<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>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.00035 | $0.00524 |
| Opus 5 | $0.00017 | $0.00262 |
| Sonnet 5 | $0.00007 | $0.00105 |
| Haiku 4.5 | $0.00003 | $0.00052 |
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.
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
- Define the failing behavior in one sentence.
- Map reproduction breadth:
- single route or surface,
- multiple consumers of one capability,
- all consumers of a shared capability,
- data-source-specific,
- environment-specific.
- Attribute mechanism:
- feature composition,
- shared component,
- data schema,
- permissions,
- environment or harness,
- acceptance wording.
- Assign owner only when breadth and mechanism agree.
- If they do not agree, return
owner_boundary_unclearwith 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.
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 · 76 lines · 35 tokens per session scan A 4b1f1fc31974
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.
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…
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.
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"…
log-to-bug-report-converter
Parses error logs, stack traces, and test failures into production-ready bug reports.
agenttrace-session-audit
Audit local AI coding-agent sessions with agenttrace for cost, tool failures, latency, anomalies, health, diffs, and CI gates.
agent-qa-result-triage
Triage failed Agent QA runs with MCP evidence, artifacts, logs, fixed failure categories, confidence, and actionable next steps.