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 agentmods add skills/microsoft/apm/docs-impact-localizernpx skills add microsoft/apm --skill docs-impact-localizergit clone --depth 1 https://github.com/microsoft/apmWhat 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 | $0.00078 | $0.01041 |
| Opus 5 | $0.00039 | $0.00521 |
| Sonnet 5 | $0.00016 | $0.00208 |
| Haiku 4.5 | $0.00008 | $0.00104 |
Grade A, and why
docs-impact-localizer 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 2d 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 — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.
docs-impact-localizer
Single responsibility: given a list of candidate pages from the classifier, produce a per-page task brief the docs-sync panel can fan out against.
You are NOT the verdict-maker (classifier owns that). You are NOT the writer (doc-writer owns that). You are the work planner.
When to invoke
The docs-sync orchestrator invokes you ONLY when the classifier
returned verdict: in_place. For no_change you don't run.
For structural the architect runs first; you may run after, scoped
to existing pages that need amendment.
Inputs
scope_pages[]from the classifier- The PR diff (
gh pr diff $PR) .apm/docs-index.yml(per-page metadata)- Optional: the structural architect's TOC delta (if you run after the architect on a structural verdict)
Step 1: load page contents
For each path in scope_pages[], read the file. Pages are typically
3-10 KB; total budget for this step is bounded by the candidate
count (the classifier should have kept it to <= 6).
Step 2: narrow scope inside each page
For each page, identify the SPECIFIC section(s) that need to change:
- Read the page's H2/H3 structure
- For each diff symbol from the classifier output, find the section most directly documenting it
- Capture line ranges:
lines 120-145notthe whole page
The output is a sections_to_edit[] per page, where each entry is:
page: docs/src/content/docs/consumer/install.md
sections_to_edit:
- section: "## From Git"
line_range: [120, 145]
diff_symbol: "--no-cache flag"
edit_kind: add | modify | remove
rationale: "the new --no-cache flag is documented nowhere; section already lists other flags so this is the natural home"
Step 3: detect cross-page conflicts
If two pages document the same symbol and the diff changes the symbol's behaviour, BOTH pages need an edit AND they must stay consistent. Flag this in the brief so the CDO synthesizer knows to cross-check coherence between the two redrafts:
cross_page_constraint:
pages: [path1, path2]
shared_symbol: "apm install --target"
consistency_required: "both pages must reflect the same default value"
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.
- 2d ago First seen · 125 lines · 78 tokens per session scan A 1a46fb1da757
docs-impact-localizer is a skill published in the GitHub repository microsoft/apm (3,687 stars, last pushed today), licensed MIT. It adds 78 tokens to every session and 1,041 once invoked, about $0.0004 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
review
Review a proposed change before applying it.
chinese-content-writing-guideline
Writing guidelines for producing high-quality Traditional Chinese (zh-TW) content. Use when writing any kind of content. Including blog posts, notes, technical articles, technical writing, chitchat, social media posts, etc., even when you are just sending a text message. Also use when reviewing or editing existing…
copilot-studio-agent-documenter
Generate comprehensive documentation for Microsoft Copilot Studio agents from exported Dataverse solutions using the Power Platform CLI. Use when asked, to analyse the solution with the agents file and create documentation from the contents.
code-review-csharp
Perform structured code reviews of C# source code covering naming conventions, performance, security, readability, and .NET best practices. Trigger phrases include "review this C# code", "check my C# for best practices", "analyze this C# class", "find issues in my C# code".
prompt-of-the-week
Generates a weekly PowerPoint slide from a PnP copilot-prompts GitHub sample URL (for example, samples/agent-instructions/creator-agent), derives the correct weekly title from the sample folder, and produces a styled .pptx file that matches the Prompt-K template layout.
api-docs-generator
Generate structured API reference documentation from source code, OpenAPI specs, or route definitions. Trigger phrases include "generate API docs", "document this API", "create API reference", "write endpoint docs", "scaffold API docs".