repository-governance-lifecycle

repository-governance-lifecycle is a skill for Claude Code from Arenukvern/skill_steward. It costs 88 tokens per session (1,351 once invoked), scanned A, a copy of repository-governance-lifecycle, MIT.

A governance guide for managing the lifecycle of an agent-operated repository. It covers architectural decisions, repository policies, living documentation, and cleanup of outdated plans.

In plain words
What is it for?
Use it when changing architecture, long-term policies, ownership, or the structure of repository documentation.
Why use it?
It helps keep important repository decisions documented and prevents stale plans or rules from misleading future work.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the skill-steward plugin — 15 skills shipped together

Good fit Use it when changing architecture, long-term policies, ownership, or the structure of repository documentation.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/arenukvern/skill_steward/repository-governance-lifecycle
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 Arenukvern/skill_steward --skill repository-governance-lifecycle
Clone the repo
git clone --depth 1 https://github.com/Arenukvern/skill_steward

Made for: Claude Code.

Or install skill-steward, the plugin that ships this one along with the rest of its 15 skills.

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 repository-governance-lifecycle

README.md
[![agentmods](https://agentmods.dev/badge/skills/arenukvern/skill_steward/repository-governance-lifecycle/github.svg)](https://agentmods.dev/skills/arenukvern/skill_steward/repository-governance-lifecycle)
Your own site
<a href="https://agentmods.dev/skills/arenukvern/skill_steward/repository-governance-lifecycle"><img src="https://agentmods.dev/badge/skills/arenukvern/skill_steward/repository-governance-lifecycle/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 repository-governance-lifecycle

Your own site · 80×15
<a href="https://agentmods.dev/skills/arenukvern/skill_steward/repository-governance-lifecycle"><img src="https://agentmods.dev/badge/skills/arenukvern/skill_steward/repository-governance-lifecycle.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 88 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,351 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 100% copy Near-identical to another mod 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.00088 $0.01351
Opus 5 $0.00044 $0.00675
Sonnet 5 $0.00018 $0.00270
Haiku 4.5 $0.00009 $0.00135

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

Security

Grade A, and why

repository-governance-lifecycle 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 11d 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.

Origin

This is a copy

100% identical to repository-governance-lifecycle — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

skills/repository-governance-lifecycle/SKILL.md · 74 lines

How it starts

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

Repository Governance Lifecycle

This is the central nervous system for governing an agent-operated repository. It applies to apps, libraries, tools, plugins, harnesses, and meta repos; Skill Steward itself remains a structural stewardship repo, not a domain tutorial catalog. It unifies ethics, branding, architectural decision logs (ADRs), and living documentation (FAQs) into a single, cohesive loop: Decide → Document → Cleanup.

Whenever an agent proposes or executes a structural shift, claim change, durable policy change, or docs-lattice change, they must walk this loop. Routine repo repairs should keep the original goal and native gate first; use this governance loop only when the repair changes durable ownership, policy, evidence, ADR/FAQ truth, or plan hygiene.

The Governance Loop

1. Check Ethics & Boundaries (NORTH_STAR)

Before making any decision, check the repository's foundational charter and ethical baseline.

  • Read Charter and Ethics to ensure your proposed changes do not violate the repository's moral boundaries (e.g. no hype; no domain tutorials inside Skill Steward; domain docs belong in the governed product repo when they are that repo's product).
  • Read North Star Rules to understand the extension model.
  • Classify north_star_impact for durable structural changes: none, applies, clarifies, sub_star, amends, or conflicts. Use the protocol only when ownership, policy, evidence truth, ADR/FAQ truth, or the repo's center may change.
  • Ask the gate questions before editing durable governance surfaces: what pain triggered this; which North Star value path it serves; whether it is a mechanism or a new center; whether it changes what the repo owns or refuses; where the ADR is if it does; and what check prevents the mechanism becoming the mission if it does not.
  • Route none and applies through the native workflow, clarifies through FAQ/skill/map/check updates, sub_star through an explicit parent/child boundary, and amends or conflicts through an ADR plus a North Star diff before implementation.

Read the full file on GitHub · 74 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. 11d ago First seen · 74 lines · 88 tokens per session scan A badab520f13b

Subscribe to this mod's changes

repository-governance-lifecycle is a skill published in the GitHub repository Arenukvern/skill_steward (11 stars, last pushed 26d ago), licensed MIT. It adds 88 tokens to every session and 1,351 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to repository-governance-lifecycle, differing in 0 lines, and is treated as a copy.