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 the-open-agent/oss-skills --skill governance-and-sustainabilitygit clone --depth 1 https://github.com/the-open-agent/oss-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/the-open-agent/oss-skills/governance-and-sustainability)<a href="https://agentmods.dev/skills/the-open-agent/oss-skills/governance-and-sustainability"><img src="https://agentmods.dev/badge/skills/the-open-agent/oss-skills/governance-and-sustainability/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/the-open-agent/oss-skills/governance-and-sustainability"><img src="https://agentmods.dev/badge/skills/the-open-agent/oss-skills/governance-and-sustainability.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.00095 | $0.02489 |
| Opus 5 | $0.00048 | $0.01244 |
| Sonnet 5 | $0.00019 | $0.00498 |
| Haiku 4.5 | $0.00010 | $0.00249 |
Grade A, and why
governance-and-sustainability 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 — 220 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Governance and Sustainability
Most open-source projects do not die from technical debt. They die because the person maintaining them stopped wanting to, and there was no structure for anyone else to take over.
Add process only when the pain is real
Governance documents for a one-person project are cosplay. Match structure to size:
| Size | Governance |
|---|---|
| 1 maintainer | None. A Scope section in the README is enough. |
| 2–3 maintainers | A written norm: who merges, how you break ties. A paragraph. |
| 4–10 | GOVERNANCE.md: roles, how maintainers are added/removed, decision process. |
| 10+, or corporate stakeholders | Formal: steering committee, voting, possibly a foundation. |
Grow into each level when the previous one visibly fails — typically at the first disagreement nobody knows how to resolve.
Decision-making models
- BDFL — one person decides. Fast, clear, and the default. Fails on bus factor and when the BDFL burns out or becomes unresponsive. Honest, and fine for years.
- Consensus-seeking — discuss until nobody blocks. Works well for 3–8 people who trust each other. Requires someone empowered to call the question, or threads run forever.
- Voting — for formal projects with real stakes. Slow, and adversarial by design; reserve it for the decisions that need legitimacy more than speed.
- RFC process — for user-visible changes in projects with many stakeholders. A written proposal, a public comment period, an explicit decision recorded in the repo. Adopt this when design arguments start recurring in issue threads. It is heavier than it looks; do not add it before you need it.
Whatever the model, record decisions where people can find them. An ADR
(docs/decisions/0007-drop-node-18.md) with context → decision → consequences takes
ten minutes and prevents the same argument in a year, with a different person.
GOVERNANCE.md, minimal version
# Governance
## Roles
- **Contributor** — anyone who opens a PR or issue.
- **Committer** — merge rights. Added by maintainer consensus after sustained
contribution. Listed in MAINTAINERS.md.
- **Maintainer** — committer + release rights + CoC enforcement.
## Decisions
Day-to-day changes: one committer approval merges.
Breaking changes, new dependencies, scope changes: an issue with the `needs-decision`
label, open at least 72 hours, resolved by maintainer consensus. Any maintainer may
block with a stated technical reason.
## Adding maintainers
Nominated by an existing maintainer, approved by consensus. Criteria: sustained
contribution, good review judgment, helps other contributors.
## Removing maintainers
12 months of inactivity moves a maintainer to emeritus (no access, credit retained).
Reinstatement on request. Removal for cause requires consensus of the others.
## Scope
<What this project does and, specifically, what it does not.>
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 · 220 lines · 95 tokens per session scan A adf2b9308b7f
governance-and-sustainability is a skill published in the GitHub repository the-open-agent/oss-skills (5 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 95 tokens to every session and 2,489 once invoked, about $0.0005 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
babysit
Use when the user says "babysit", "monitor", "keep checking", "keep an eye on", "loop on this PR", "let me know when", or wants polling that outlives a wait+poll window. Same-session monitoring loop for PRs, CI runs, tickets, and deployments using the monitorstart / monitorupdate / autonudgestop MCP tools. The loop…
jira-server-pat-cli
A command-line workflow for managing self-hosted Jira Server or Jira Data Center through Jira's REST API. Jira is a system for tracking issues, projects, work, and software tasks.
issue-comment
Handle a non-build maintainer comment on an issue or PR — close, reopen, label, dedupe, answer a brief question, or triage. Action-only; redirect anything that needs code changes to /build.
github-issues
GitHub issue'larını gh veya REST ile oluştur, sırala, etiketle, ata.
phase-closeout
A Chinese-language stage closer that summarizes completed work, records decisions, updates project status, and prepares the next conversation.
handoff
Use when leaving a project, joining a project, or performing any project/module handover. Detects .handoff/ directory presence but always confirms intent before acting.