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 pnp/sharepoint-skills --skill news-governance-reviewgit clone --depth 1 https://github.com/pnp/sharepoint-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/pnp/sharepoint-skills/news-governance-review)<a href="https://agentmods.dev/skills/pnp/sharepoint-skills/news-governance-review"><img src="https://agentmods.dev/badge/skills/pnp/sharepoint-skills/news-governance-review/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/pnp/sharepoint-skills/news-governance-review"><img src="https://agentmods.dev/badge/skills/pnp/sharepoint-skills/news-governance-review.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.00211 | $0.04487 |
| Opus 5 | $0.00105 | $0.02243 |
| Sonnet 5 | $0.00042 | $0.00897 |
| Haiku 4.5 | $0.00021 | $0.00449 |
Grade A, and why
news-governance-review 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 13d 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 — 266 lines — stays where its author put it; the contents beside it link to each section on GitHub.
News Governance Review
Purpose
Intranet news flows fill up over time with posts that are outdated, half-finished, mistargeted, or ownerless, and important news gets pushed down and missed. This skill gives site owners, editors, and communications teams a structured governance review of the news on a site.
It evaluates each news post against freshness, publication-quality, governance, findability, relevance, and link quality, assigns a recommended outcome with reasons, and produces a color-coded HTML dashboard that works directly as a cleanup backlog. It relies only on the default Site Pages fields available on every modern SharePoint site; no custom columns are required.
It is strictly advisory and read-only: it reads pages and metadata, but never deletes, unpublishes, archives, edits, or reclassifies anything. Every decision to keep, update, archive, unpublish, or delete stays with a human content owner.
Trigger Phrases
Activate this skill when the user says any of the following (or close variations):
- "review news" / "review our news posts" / "news review report"
- "news governance" / "audit news posts"
- "check news quality" / "find outdated news"
- "clean up intranet news" / "news cleanup backlog"
- "which news posts are obsolete"
Inputs & Scope
Determine the review scope from the user's request and the current context, in this order:
- Selected pages: if the user has news posts/pages selected or says "these/this", review exactly the selection.
- Named site or library: if the user names a site or a pages library (e.g., "review the news on the HR site"), resolve it and review its news posts.
- Current site's news: if no other scope is given, review the news posts in the current site's Site Pages library.
- If no scope can be resolved, ask the user which site, library, or pages to review. Do not guess.
What counts as a news post: pages in the Site Pages library whose PromotedState is 2 (promoted as news). If the user explicitly asks to include all site pages, widen the scope and say so in the report. If PromotedState is unavailable, fall back to reviewing all pages in the resolved library and record that in the report's limitations section.
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.
- 13d ago First seen · 266 lines · 211 tokens per session scan A 16c7e7b2dd1f
news-governance-review is a skill published in the GitHub repository pnp/sharepoint-skills (118 stars, last pushed 4d ago), licensed MIT. It adds 211 tokens to every session and 4,487 once invoked, about $0.0011 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
html-ppt-hermes-cyber-terminal
OpenDesign + BYOK: choosing and wiring your own model, hands-on — cost, quality, and the routing decision. Built as a decision-grade AI literacy deck for engineers, IT, applied-AI teams.
skill-doc-delivery
Convert markdown to DOCX, PPTX, XLSX, PDF office documents — use when you need exportable deliverables.
skill-writing-plans
Create zero-context implementation plans with bite-sized tasks — use for multi-step feature planning.
skill-copilot-provider
GitHub Copilot CLI as optional zero-cost provider via copilot -p programmatic mode.
bf-to-agents-sdk-dotnet-migration
Use when migrating a Bot Framework .NET SDK bot to Microsoft 365 Agents SDK. Triggered by projects that depend on packages: Microsoft.Bot.Builder or Microsoft.Bot.Builder.Integration.AspNet.Core that want to migrate to Agents SDK.
go-testing
Trigger: Go tests, go test coverage, Bubbletea teatest, golden files. Apply focused Go testing patterns.