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 broken-link-auditorgit 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/broken-link-auditor)<a href="https://agentmods.dev/skills/pnp/sharepoint-skills/broken-link-auditor"><img src="https://agentmods.dev/badge/skills/pnp/sharepoint-skills/broken-link-auditor/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/broken-link-auditor"><img src="https://agentmods.dev/badge/skills/pnp/sharepoint-skills/broken-link-auditor.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.00112 | $0.02290 |
| Opus 5 | $0.00056 | $0.01145 |
| Sonnet 5 | $0.00022 | $0.00458 |
| Haiku 4.5 | $0.00011 | $0.00229 |
Grade A, and why
broken-link-auditor 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 10d 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 — 224 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Broken Link Auditor
Purpose
Broken or stale links make SharePoint sites feel unreliable, especially after migrations, re-orgs, and content cleanups. This skill audits link health across SharePoint pages, news posts, libraries, lists, or selected items and saves a self-contained HTML report that teams can act on. It is strictly read-only for content: it never edits pages, files, metadata, or links. The only thing it writes is the final HTML report file.
Trigger Phrases
Activate this skill when the user says any of the following (or close variations):
- "broken link audit" / "dead link audit"
- "find broken links" / "check broken links"
- "check dead links on this site"
- "audit links in this library"
- "scan pages for broken links"
- "which SharePoint links are broken"
Inputs & Scope
Determine the reporting scope from the user's request and the current context, in this order:
- Selected items — if the user has pages, files, or folders selected or says "these/this", audit those items first.
- Named library, list, or Site Pages — if the user names one, resolve it on the current site.
- Current library or current Site Pages context — if the user is already in one, use it.
- Whole current site — if no narrower scope is clear, scan accessible Site Pages plus hyperlink-bearing items in accessible user-created lists and libraries.
- If no scope can be resolved, ask the user which library, page set, or site scope to audit. Do not guess.
Only inspect content the current user can already read. Never invent pages, items, targets, or HTTP outcomes.
What counts as a link
Audit the following when present:
- Links embedded in SharePoint page and news post content
- Hyperlink / URL columns on list items or library items
- Obvious SharePoint links stored in plain text fields when the user explicitly asks for a broader scan
Ignore the following unless the user explicitly asks:
- Mailto links
- Telephone links
- JavaScript pseudo-links
- Anchors that only jump within the same page and do not reference another resource
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.
- 10d ago First seen · 224 lines · 112 tokens per session scan A b20957528cc3
broken-link-auditor is a skill published in the GitHub repository pnp/sharepoint-skills (112 stars, last pushed yesterday), licensed MIT. It adds 112 tokens to every session and 2,290 once invoked, about $0.0006 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
chrome-devtools-mcp
Use Chrome DevTools MCP from .NET agents and .NET-focused repos to inspect, debug, and automate Chrome through an MCP client. USE FOR: the repo needs browser-level debugging for ASP.NET Core, Blazor, WebAssembly, or any .NET app with a web UI; the user wants an MCP server that can inspect console. DO NOT USE FOR: pure…
chrome-devtools
Browser debugging, performance profiling, and automation via Chrome DevTools MCP. Use when user says "debug this page", "take a screenshot", "check network requests", "profile performance", "inspect console errors", or "analyze page load". Do NOT use for full E2E test suites (use playwright-skill) or non-browser…
react-sentinel-debug
Use React-Sentinel when a task needs live browser or React runtime inspection rather than static code reading alone.
chrome-devtools
Expert-level browser automation, debugging, and performance analysis using Chrome DevTools MCP. Use for interacting with web pages, capturing screenshots, analyzing network traffic, and profiling performance.
chrome-devtools-cli
Use this skill to write shell scripts or run shell commands to automate tasks in the browser or otherwise use Chrome DevTools via CLI.
a11y-debugging
Uses Chrome DevTools MCP for accessibility (a11y) debugging and auditing based on web.dev guidelines. Use when testing semantic HTML, ARIA labels, focus states, keyboard navigation, tap targets, and color contrast.