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 build-sharepoint-business-solutiongit 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/build-sharepoint-business-solution)<a href="https://agentmods.dev/skills/pnp/sharepoint-skills/build-sharepoint-business-solution"><img src="https://agentmods.dev/badge/skills/pnp/sharepoint-skills/build-sharepoint-business-solution/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/build-sharepoint-business-solution"><img src="https://agentmods.dev/badge/skills/pnp/sharepoint-skills/build-sharepoint-business-solution.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.00126 | $0.02844 |
| Opus 5 | $0.00063 | $0.01422 |
| Sonnet 5 | $0.00025 | $0.00569 |
| Haiku 4.5 | $0.00013 | $0.00284 |
Grade A, and why
build-sharepoint-business-solution 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 4d 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 — 271 lines — stays where its author put it; the contents beside it link to each section on GitHub.
When to use
Use this skill to design, create, demonstrate, audit, rebuild, or extend a SharePoint business solution. It applies to any domain, including procurement, HR, finance, legal, IT, projects, operations, compliance, sales, service management, facilities, and administration.
Use it when the solution may include one or more of:
- SharePoint lists or document libraries.
- Main transaction records and related detail records.
- Reference data and configurable business rules.
- Native SharePoint approvals.
- Event-driven or scheduled workflows.
- Notifications through Teams or Outlook.
- Demo or seed data.
- Live HTML dashboards backed by SharePoint lists.
- An app-like user experience or architecture recommendation.
Don't use standalone HTML as a security boundary or claim it can securely create and update data while hiding the underlying lists. SharePoint permissions still apply. For a true application-only experience, recommend Power Apps, SPFx, or a secured API/middleware layer with app-only permissions.
Inputs
Extract from the conversation first, then discover missing technical context:
- Business purpose, users, roles, lifecycle, decisions, and reporting needs.
- Target SharePoint site URL.
- Existing lists, libraries, forms, approvals, workflows, rules, and dashboards.
- Main records, child/detail records, reference data, configuration, audit history, and integration logs.
- Fields, types, required values, defaults, uniqueness, choices, validation, attachments, and retention needs.
- Approval routing, triggers, conditions, recipients, messages, schedules, and escalation rules.
- People used in User fields.
- External systems and approved integration method.
- Demo-data requirements.
- Dashboard audience, KPIs, filters, breakdowns, tables, destination library, and file name.
- Whether the output is reporting-only or must support secure create/update actions.
Ask at most one question when a required value can't be discovered. Don't ask for IDs or internal names that tools can resolve.
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.
- 4d ago First seen · 271 lines · 126 tokens per session scan A de331de94a29
build-sharepoint-business-solution is a skill published in the GitHub repository pnp/sharepoint-skills (118 stars, last pushed 3d ago), licensed MIT. It adds 126 tokens to every session and 2,844 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-09-07.
Other skills, from other repositories
issue-creation
Trigger: issue creation, bug reports, feature requests, or issue approval. Create and triage GitHub issues from repository evidence.
sdd-tasks
Break an SDD change into implementation tasks. Trigger: orchestrator launches task planning for a change.
flow-parallel
Decompose and execute large changes, migrations, or multi-issue fixes in parallel with quality gates.
skill-task-management
Manage tasks with Claude Code native tools — use to track TODOs, delegate work, and monitor progress.
skill-issues
Track project blockers, bugs, and gaps across sessions — use when issues pile up or need triage.
systemic-issue-triage
Trigger: new issue, bug report, triage, backlog, issue flood, community report, root cause, dead-end, blocked user. Attack issues by root class, never one-by-one; fixes must shrink the system, not grow it.