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 tomimor/skills --skill governance-messagegit clone --depth 1 https://github.com/tomimor/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/tomimor/skills/governance-message)<a href="https://agentmods.dev/skills/tomimor/skills/governance-message"><img src="https://agentmods.dev/badge/skills/tomimor/skills/governance-message/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/tomimor/skills/governance-message"><img src="https://agentmods.dev/badge/skills/tomimor/skills/governance-message.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.00101 | $0.02389 |
| Opus 5 | $0.00051 | $0.01195 |
| Sonnet 5 | $0.00020 | $0.00478 |
| Haiku 4.5 | $0.00010 | $0.00239 |
Grade A, and why
governance-message 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 9d 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 — 229 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Governance Message
Turn a governance proposal URL into a concise, Slack-ready summary using the fixed template below.
Critical rules
- Input is a single URL. The skill argument is the proposal link. If the user did not provide one, ask for it before doing anything else.
- Fetch before drafting. Always pull the page via
WebFetchfirst. Never draft from prior knowledge of the proposal -- proposals get amended. - Clarification gate. If voting stance, risk level, or rationale are not
derivable from the page, STOP and ask the user via
AskUserQuestion. Never guess a stance. - Confirmation gate. Show the full draft to the user and wait for explicit approval before posting, copying, or sending anywhere.
- Template is fixed. Do not invent sections. Do not reorder. Do not drop bullets. The structure below is the contract.
- Concision. Each section is 1-2 sentences or 1-3 bullets. Aim for a message a reader can scan in under 30 seconds.
- Always English. The drafted message is always written in English, regardless of the language the user is speaking. If the source proposal is in another language, translate it. Conversation around the draft can be in any language, but the deliverable is English.
- Slack mrkdwn only. The output uses Slack's
mrkdwnflavor, not GitHub/CommonMark. That means*bold*(single asterisks),_italic_,<url|label>for links, no#headers, no**bold**, no[label](url), no horizontal rules. See Slack mrkdwn cheatsheet. - Plain message, not a document. The deliverable is a single chat message
ready to paste into Slack. Never write it to a
.mdfile. Never wrap it in a fenced code block. Never add a title, preamble, or trailing explanation. Emit the message as the bare chat reply with the Slack mrkdwn characters (*,<url|label>,•,:emoji:) as literal text so the user copies it straight from the chat into Slack.
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.
- 9d ago First seen · 229 lines · 101 tokens per session scan A e7f9eff8121d
governance-message is a skill published in the GitHub repository tomimor/skills (2 stars, last pushed 4d ago), licensed MIT. It adds 101 tokens to every session and 2,389 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
workers-best-practices
Cloudflare Workers best practices for production applications. Use when writing, reviewing, or configuring Workers.
find-journalists
Build, refine, dedupe, and enrich small fit-checked journalist lists for newsjack campaigns. Uses the newsjack CLI (preferred) or the medialyst MCP for news search and journalist enrichment, and falls back to a best-effort local mode with no verified contacts; the agent owns how returned data is organized.
story-origin-check
Recover the first public timestamp and canonical major coverage for a newsjacking signal, then decide whether newer coverage is the same story, a different story, or a materially new development.
relevance-coarse-filter
Cheap, high-recall first-pass filter that removes obvious junk from a detector candidate pool before expensive story-origin research and PR judgment. Decides keep, monitoronly, or reject — never ranks, writes angles, verifies dates, or decides whether to pitch.
annotating-task-lineage
Annotate Airflow tasks with data lineage using inlets and outlets. Use when the user wants to add lineage metadata to tasks, specify input/output datasets, or enable lineage tracking for operators without built-in OpenLineage extraction.
checking-freshness
Quick data freshness check. Use when the user asks if data is up to date, when a table was last updated, if data is stale, or needs to verify data currency before using it.