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 Arenukvern/mcp_flutter --skill repository-governance-lifecyclegit clone --depth 1 https://github.com/Arenukvern/mcp_flutterWrote 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/arenukvern/mcp_flutter/repository-governance-lifecycle)<a href="https://agentmods.dev/skills/arenukvern/mcp_flutter/repository-governance-lifecycle"><img src="https://agentmods.dev/badge/skills/arenukvern/mcp_flutter/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.
<a href="https://agentmods.dev/skills/arenukvern/mcp_flutter/repository-governance-lifecycle"><img src="https://agentmods.dev/badge/skills/arenukvern/mcp_flutter/repository-governance-lifecycle.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium MCP Rug Pull · line 68 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00088 | $0.01351 |
| Opus 5 | $0.00044 | $0.00675 |
| Sonnet 5 | $0.00018 | $0.00270 |
| Haiku 4.5 | $0.00009 | $0.00135 |
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.
Copies of this mod
1 near-identical copy found in the catalogue:
- repository-governance-lifecycle — 100% identical, 0 lines differ
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_impactfor durable structural changes:none,applies,clarifies,sub_star,amends, orconflicts. 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
noneandappliesthrough the native workflow,clarifiesthrough FAQ/skill/map/check updates,sub_starthrough an explicit parent/child boundary, andamendsorconflictsthrough an ADR plus a North Star diff before implementation.
What ships with it
12 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- evals/cases/evidence-routing-trigger.yaml 610 B
- evals/cases/governance-adr-trigger.yaml 458 B
- evals/cases/logo-work-dormant.yaml 415 B
- evals/cases/north-star-impact-trigger.yaml 787 B
- evals/cases/routine-repair-dormant.yaml 677 B
- references/adr-format.md 6.8 KB
- references/brand-guidelines.md 5.3 KB
- references/charter-and-ethics.md 8.2 KB
- references/evals.md 1.8 KB
- references/faq-format.md 6.9 KB
- references/north-star-rules.md 6.8 KB
- references/sources.md 222 B
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.
- 11d ago First seen · 74 lines · 88 tokens per session scan A badab520f13b
repository-governance-lifecycle is a skill published in the GitHub repository Arenukvern/mcp_flutter (375 stars, last pushed 2d 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. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
at_client_skills-sdk
Use this skill when a developer is building a Dart or Flutter app that depends on atclient or atclientflutter from pub.dev, stores or shares data via the Atsign Protocol, needs onboarding (CRAM new-atsign, atKeys file, keychain, APKAM) or APKAM enrollment, or asks about AtCollection , CItem , Query , sub-collections…
signals-dart
Advanced reactive state primitives, collections, mixins, and utilities of signalscore.
signals-flutter
Highly optimized Flutter UI bindings and GPU rendering for reactive signals.
signals-migration-6-to-7
Detailed guidelines, patterns, and rules for migrating codebases from signals.dart version 6.x to version 7.x.
signals-preact-dart
Core reactive programming best practices and primitive definitions for preactsignals in Dart.
flutter-pre-caching
Use when preloading fonts, asset/network images, Lottie/Rive animations, local JSON/config, warming initial API data, or optimizing Flutter Web startup.