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 yha9806/academic-writing-toolkit --skill release-governancegit clone --depth 1 https://github.com/yha9806/academic-writing-toolkitWrote 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/yha9806/academic-writing-toolkit/release-governance)<a href="https://agentmods.dev/skills/yha9806/academic-writing-toolkit/release-governance"><img src="https://agentmods.dev/badge/skills/yha9806/academic-writing-toolkit/release-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/yha9806/academic-writing-toolkit/release-governance"><img src="https://agentmods.dev/badge/skills/yha9806/academic-writing-toolkit/release-governance.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00064 | $0.01114 |
| Opus 5 | $0.00032 | $0.00557 |
| Sonnet 5 | $0.00013 | $0.00223 |
| Haiku 4.5 | $0.00006 | $0.00111 |
Grade A, and why
release-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 7d 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 — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/release-governance - Release Evidence Governance
Purpose
Prepare release-facing academic artifacts with explicit evidence control. The core rule is:
release truth = ref + artifact + gate
Do not infer release truth from memory, a branch name, a pull request title, a local file cache, or an agent draft.
Trigger Words
This skill activates on: release governance, release evidence, camera-ready, rebuttal packet, artifact packet, claim ledger, human evidence gate, release packet, /release-governance.
Core Rules
- Name the exact ref, artifact, and gate behind every release-facing claim.
- Keep draft advisory evidence, verified artifacts, and final human evidence separate.
- Do not promote agent or Gemini review output into final evidence.
- Do not treat ignored, untracked, cached, or local-only assets as submitted artifacts.
- Do not treat a repository check as venue, submission-system, or scientific compliance.
- If two refs diverge, name both and scope which one is canonical for each artifact.
- If a worktree is dirty, list the dirty paths and mark the packet as draft until changes are committed or explicitly scoped.
- Freeze evidence and argument separately. An evidence ref or result snapshot does not authorise an unapproved narrative, and an approved manuscript spine does not validate changed numbers.
Evidence States
Use references/evidence_state_schema.md for the shared states:
draft_advisoryverified_artifacthuman_final
human_final requires an explicit human confirmation gate when the project schema provides one. Agent drafts, reviewer suggestions, generated summaries, simulations, and prefilled labels stay draft_advisory.
Workflow
1. Declare Scope
Create release/release_scope.md with scope date, artifact name, intended use,
included refs, excluded refs, the evidence baseline, the argument baseline, and
the highest-risk open question. For a manuscript, the evidence baseline names
the frozen results, data/configuration, and artifact refs; the argument baseline
names the author-approved intent and manuscript version.
What ships with it
4 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.
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.
- 7d ago Changed · +11 lines · +18 tokens per session f28611713113
- 11d ago First seen · 100 lines · 46 tokens per session scan A 2193f07eb4f6
release-governance is a skill published in the GitHub repository yha9806/academic-writing-toolkit (38 stars, last pushed 3d ago), licensed MIT. It adds 64 tokens to every session and 1,114 once invoked, about $0.0003 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
docs-generator
WHAT — Generate or update documentation from code: README.md from repo structure, CHANGELOG.md from git history, API reference from OpenAPI/GraphQL schemas, and AGENTS.md starters for new projects.
tikz-figure-review
Review and fix alignment, label collision, clipping, legend-over-data, overlap, and layout issues in TikZ and pgfplots figures inside LaTeX documents. Use when the user wants to review figures in a paper, tutorial, lecture notes, or thesis before submission; when a reviewer flags figure problems; when a rendered…
PDF → spreadsheet — extract data into Excel (Local MCP)
Use when the user wants to pull data out of one or more PDFs (invoices, bank/credit-card statements, receipts, reports, tables) and put it into a spreadsheet. pdfread is one of the most-used tools; this codifies the read-PDF → structure → write-Excel workflow. Powered by Local MCP, on-device.
latex-writer
Write, structure, and compile LaTeX documents for academic purposes. Use this skill whenever the user needs to write a LaTeX document, choose the right document class or packages, format equations, manage bibliographies, create figures and tables in LaTeX, troubleshoot errors, or prepare a journal-ready manuscript.…
data-management-plan
Write and review data management plans (DMPs) for research grants and projects. Use this skill whenever the user needs to write a DMP for NIH, NSF, UKRI, EU Horizon, or another funder; understand FAIR data principles; choose a data repository; describe data formats and metadata standards; handle sensitive or…
Use this skill whenever the user wants to do anything with PDF files. This includes reading or extracting text/tables from PDFs, combining or merging multiple PDFs into one, splitting PDFs apart, rotating pages, adding watermarks, creating new PDFs, filling PDF forms, encrypting/decrypting PDFs, extracting images, and…