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 project-intelligence-change-event-extractiongit 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/project-intelligence-change-event-extraction)<a href="https://agentmods.dev/skills/pnp/sharepoint-skills/project-intelligence-change-event-extraction"><img src="https://agentmods.dev/badge/skills/pnp/sharepoint-skills/project-intelligence-change-event-extraction/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/project-intelligence-change-event-extraction"><img src="https://agentmods.dev/badge/skills/pnp/sharepoint-skills/project-intelligence-change-event-extraction.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.00136 | $0.02209 |
| Opus 5 | $0.00068 | $0.01104 |
| Sonnet 5 | $0.00027 | $0.00442 |
| Haiku 4.5 | $0.00014 | $0.00221 |
Grade A, and why
project-intelligence-change-event-extraction 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 — 167 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Change Event Extraction
Purpose
Read every document in this project library and compile a complete, structured record of every event that affected — or should have affected — the project's scope, timeline, budget, or technical approach. This is the factual foundation for all subsequent analysis. Be thorough: a signal buried in a footnote is as important as a formal change request.
Step 1 — Read all documents
Process ALL documents in the Project Documents library. Note each document's title, author (if stated), and date. Do not skip or skim any document. Read attachments, appendices, and meeting notes as carefully as the main body.
Step 2 — Identify change events
For each document, identify every instance of the following event types:
| Event type | What qualifies |
|---|---|
| Scope assumption established | A baseline, estimate, or assumption that the project plan, budget, or timeline depends on — especially if unvalidated |
| Scope change | Addition, reduction, or modification to agreed deliverables, data, or work |
| Technical decision | Architecture or technology choice made or changed during delivery |
| Client request | Any instruction or request from the client affecting scope, approach, schedule, or budget — formal or informal |
| Risk event | Risk identified, rating changed, risk materialising, risk dismissed, or risk downgraded below its true severity |
| Budget event | Cost variance, overrun, approved financial change, or budget assumption set |
| Schedule event | Milestone slippage, date change, sprint replan, or timeline extension |
| Governance event | Change request raised, steering committee decision, approval, escalation, or missed change control step |
| Signal / early warning | Any observation, comment, or flagged item that indicated potential future risk — even if not formally escalated |
Step 3 — Extract all fields for every event
For each event, extract every field in the table below. If a field is not documented, state "Not documented" — do not omit the field or leave it blank.
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 · 167 lines · 136 tokens per session scan A 8c8c07d49944
project-intelligence-change-event-extraction is a skill published in the GitHub repository pnp/sharepoint-skills (112 stars, last pushed yesterday), licensed MIT. It adds 136 tokens to every session and 2,209 once invoked, about $0.0007 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
project-status-tracker
Maintains living project files (project.md, decisions.md, risks.md, links.md) in a per-project OneDrive folder from emails, Teams channels and meeting transcripts, and generates a weekly DRAFT status document in Word. Use when the user asks to set up tracking for a project, update a project's status files, log a…
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-doc-delivery
Convert markdown to DOCX, PPTX, XLSX, PDF office documents — use when you need exportable deliverables.
skill-issues
Track project blockers, bugs, and gaps across sessions — use when issues pile up or need triage.