Borrowing it
Nothing to install: this file belongs to niels-emmer/myace. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/niels-emmer/myace/main/.opencode/skills/governance/SKILL.mdgit clone --depth 1 https://github.com/niels-emmer/myaceWrote 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/niels-emmer/myace/governance)<a href="https://agentmods.dev/skills/niels-emmer/myace/governance"><img src="https://agentmods.dev/badge/skills/niels-emmer/myace/governance/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/niels-emmer/myace/governance"><img src="https://agentmods.dev/badge/skills/niels-emmer/myace/governance.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.00038 | $0.00878 |
| Opus 5 | $0.00019 | $0.00439 |
| Sonnet 5 | $0.00008 | $0.00176 |
| Haiku 4.5 | $0.00004 | $0.00088 |
Grade A, and why
governance 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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MyACE-specific governance
This skill extends the global governance rules with MyACE project-specific conventions.
Data classification
Same classification table as the global governance skill (PUBLIC / INTERNAL / CONFIDENTIAL / REGULATED). When in doubt, treat as CONFIDENTIAL.
ADR process (Architecture Decision Records)
MyACE uses ADRs to capture non-obvious, expensive-to-reverse decisions. See docs/adr/README.md for the full guide.
When to write an ADR:
- Picking an auth strategy, data model shape, deployment topology
- Anything where a reasonable engineer could have gone a different direction
- A decision that's expensive to reverse
When NOT to write an ADR:
- Routine features, bug fixes, or anything where the code itself is the whole explanation
Format:
- Copy
docs/adr/template.md - Number sequentially (next is
0006) - Keep it short — one screen
- Never renumber or delete a past ADR
- If superseded, mark old status as
Superseded by ADR-00XX
ADR structure:
# ADR-00XX: Title
**Status:** Proposed | Accepted | Superseded by ADR-00XX
## Context
What problem forced this decision? What constraints were in play?
## Decision
What did we decide to do, stated as a clear, single sentence.
## Alternatives considered
What else was on the table, and why it was rejected.
## Consequences
What this makes easier, what it makes harder, and what it gives up.
Documentation maintenance
MyACE maintains documentation for two audiences, both updated in the same PR as the code:
| Document | Audience | Purpose |
|---|---|---|
README.md |
Humans, first visit | What MyACE is, how to run it |
AGENTS.md / CLAUDE.md |
AI coding agents | Terse, enforceable rules and gotchas |
docs/ |
Humans and agents, deep dives | Architecture, data model, invariants, ADRs, debugging, extending |
Before considering a change done:
- New route, model field, or config setting → update
README.mdanddocs/data-model.md/docs/invariants.md - New non-obvious pattern, gotcha, or convention → add a numbered rule to
AGENTS.mdand an entry indocs/debugging.md - Expensive-to-reverse decision → write an ADR in
docs/adr/ - Stale doc → fix it in the same PR, don't leave it for later
- Removing a feature or file → grep across
README.md,AGENTS.md,CLAUDE.md, anddocs/for dangling references
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 · 95 lines · 38 tokens per session scan A afff49ea57f6
governance is a skill published in the GitHub repository niels-emmer/myace (1 stars, last pushed 5d ago), licensed MIT. It adds 38 tokens to every session and 878 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
idea
Use when capturing ONE new idea the user voices and wants recorded — "save this idea", "I have an idea", "log this idea", "/idea", "idea: ...". Creates a provenance-tracked folder (one folder per idea) in your ideas repo, dedups against an index, optionally mirrors to a GitHub Project view filtered by label:idea. NOT…
pm-feedback
A feedback-analysis aid that turns spreadsheet data, CSV files, pasted text, or review screenshots into organized product insights. It groups themes, identifies sentiment, examines trends and sources, calculates NPS, and extracts user types.
weekly-planning
A planning workflow that turns a completed weekly review and existing backlog into prioritized outcomes for one ISO calendar week.
gh-issues
Use when creating, searching, updating, or managing GitHub issues via CLI. Triggers: "issue", "create issue", "gh issue", "task tracking", "context", "handoff", "resume task", "session context", "save progress", "active tasks", "in-progress", "my tasks", "open issues". Covers: gh commands, bulk operations, JSON/jq…
pm-brainstorm
A structured brainstorming session for exploring a specific product problem or opportunity and narrowing the results to ideas worth pursuing.
ceo-council
Use when needing strategic project analysis from multiple independent expert perspectives. Triggers on business decisions, growth strategy, product direction, competitive analysis, or any situation where diverse C-level opinions reduce blind spots.