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 calsora/power-platform-github-copilot-kit --skill docs-syncgit clone --depth 1 https://github.com/calsora/power-platform-github-copilot-kitWrote 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/calsora/power-platform-github-copilot-kit/docs-sync)<a href="https://agentmods.dev/skills/calsora/power-platform-github-copilot-kit/docs-sync"><img src="https://agentmods.dev/badge/skills/calsora/power-platform-github-copilot-kit/docs-sync/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/calsora/power-platform-github-copilot-kit/docs-sync"><img src="https://agentmods.dev/badge/skills/calsora/power-platform-github-copilot-kit/docs-sync.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.00033 | $0.00576 |
| Opus 5.5 | $0.00013 | $0.00230 |
| Sonnet 5.5 | $0.00007 | $0.00115 |
| Haiku 4.5 | $0.00003 | $0.00058 |
Grade A, and why
docs-sync 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 6d 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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Documentation Sync Skill
Context
This skill keeps the repository's top-level documentation aligned with recent changes. It is designed for small, focused updates where a skill, agent, workflow, or repo guidance file changes and the README or another key doc should accurately reflect the current state.
The goal is to avoid drift between the repo and its documentation while keeping updates brief, factual, and easy to maintain.
Example Trigger Phrases
- "Update the README to reflect the new retro skill."
- "Sync the docs after changing the repo skill set."
- "Refresh the project overview after adding a new agent or skill."
- "Keep the README consistent with the latest repo guidance."
What This Skill Should Do
Review the changed files and update the relevant documentation sections only when needed. Focus on:
- new skills or agent guidance
- changed repo responsibilities or workflows
- updated setup, usage, or structure information
- additions or removals of top-level guidance files
Scope Rules
- Update the README or docs index only when the change affects repo usage or discoverability.
- Keep edits factual and based on the current repository state.
- Do not invent capabilities, agents, or tooling that are not present.
- Prefer small, targeted updates over broad rewrites.
- Do not add marketing language or speculative content.
What to Update
- README summary or overview sections
- repository structure notes
- agent or skill references
- getting started or quick reference sections
- any small top-level docs that are clearly intended to summarize repo capabilities
What Not to Update
- detailed implementation guidance that belongs in a dedicated doc
- long technical design content unrelated to the repo summary
- unrelated content in existing docs just because a change happened elsewhere
- generated documentation that should be maintained separately
Simple Decision Rules
- If the change adds or modifies a reusable skill, update the relevant README or repo summary.
- If the change is internal-only and not discoverable to repo users, do not change README.
- Prefer concise summary bullets over long explanatory blocks.
- Keep naming and paths consistent with the repository.
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.
- 6d ago First seen · 65 lines · 33 tokens per session scan A 62e6cf28f9ee
docs-sync is a skill published in the GitHub repository calsora/power-platform-github-copilot-kit (6 stars, last pushed 7d ago), licensed MIT. It adds 33 tokens to every session and 576 once invoked, about $0.0001 per session on Opus 5.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-10-11.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…