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/bkuriach/copilot-agents-tutorial/summarize-notesnpx skills add bkuriach/copilot-agents-tutorial --skill summarize-notesgit clone --depth 1 https://github.com/bkuriach/copilot-agents-tutorialWhat 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.00061 | $0.00383 |
| Opus 5 | $0.00030 | $0.00192 |
| Sonnet 5 | $0.00012 | $0.00077 |
| Haiku 4.5 | $0.00006 | $0.00038 |
Grade A, and why
summarize-notes 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.
What it actually says
Summarize Notes
Turn raw notes into a short, skimmable, faithful summary.
When to use
Use this skill when the user wants a summary, recap, condensed version, or "the gist" of one or more notes files (meeting notes, research notes, project briefs, and similar).
Steps
- Read each notes file the user provided. Do not pull in files they did not mention.
- Identify the overview, the most important points, any explicit decisions, and any action items (with owner and due date when stated).
- Produce the output using the format below.
- Do not invent owners, dates, decisions, or facts that are not in the source. If something is unclear, note it briefly instead of guessing.
Output format
## Overview
<1 to 2 sentences>
## Key points
- <point 1>
- <point 2>
- <point 3>
## Decisions (omit this section if there are none)
- <decision>
## Action items (omit this section if there are none)
- <Owner> - <task> (due <date> if present)
Rules
- Stay faithful to the source; summarize, do not editorialize.
- Keep it concise: aim for 3 to 6 key points.
- Never rewrite or modify the original notes files.
- If multiple files are given, summarize them together and note which file a decision or action item came from when it is not obvious.
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 · 45 lines · 61 tokens per session scan A 96b339fcb0b8
summarize-notes is a skill published in the GitHub repository bkuriach/copilot-agents-tutorial (6 stars, last pushed 3mo ago), licensed MIT. It adds 61 tokens to every session and 383 once invoked, about $0.0003 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-31.
Other skills, from other repositories
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…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…