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/copilot-camp/dev-camp-decknpx skills add microsoft/copilot-camp --skill dev-camp-deckgit clone --depth 1 https://github.com/microsoft/copilot-campWhat 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.00091 | $0.01480 |
| Opus 5 | $0.00046 | $0.00740 |
| Sonnet 5 | $0.00018 | $0.00296 |
| Haiku 4.5 | $0.00009 | $0.00148 |
Grade A, and why
dev-camp-deck 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 — 215 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dev Camp PowerPoint Deck Skill
What This Skill Does
Creates a professional PowerPoint presentation on any Copilot Dev Camp lab or Microsoft technology topic by:
- Topic Confirmation — Clarifies the specific lab/topic and target audience
- Research — Performs multiple searches across Microsoft Learn documentation
- Structure — Organizes findings into a logical slide flow with proper pacing
- Content Creation — Generates a polished PowerPoint deck with:
- Title slide with topic and date
- Agenda/outline slide
- Content slides with key concepts
- Code/architecture example slides
- Best practices slide
- Conclusion with next steps
- Speaker notes on each slide
- Source citations
When to Use This Skill
Activate this skill when you need:
- Presentation on a Dev Camp lab (e.g., Building Agents, Extensions, etc.)
- Overview deck on a Microsoft technology topic
- Training material for a technology or concept
- Conference or team presentation on copilot/AI topics
- Educational slides with speaker guidance
Workflow
Step 1: Topic & Audience Selection
Ask the user:
- Topic: Which Dev Camp lab or Microsoft technology? (e.g., "Building AI Agents with Copilot")
- Audience: Who is this for? (e.g., "Enterprise architects", "Developers", "Executives")
- Duration: How long is the presentation? (e.g., "15 minutes", "30 minutes", "60 minutes")
- Depth: Technical depth level? (e.g., "Overview", "Intermediate", "Advanced")
Step 2: Multi-Source Research
Conduct multiple searches to gather comprehensive content:
- Search: "[Topic] overview"
- Search: "[Topic] architecture and design"
- Search: "[Topic] implementation guide"
- Search: "[Topic] best practices"
- Search: "[Topic] code examples"
- Search: "[Specific scenario relevant to topic]"
Step 3: Slide Structure Planning
Organize content into a logical flow:
Slide Breakdown (for 30-minute presentation):
1. Title Slide (1 slide)
- Topic, presenter, date, organization
2. Agenda (1 slide)
- Overview of topics to be covered
3. Context/Introduction (2-3 slides)
- Problem statement
- Why this matters
- Key goals
4. Core Content (6-8 slides)
- Architecture/overview
- Key components
- How it works
- Use cases/scenarios
5. Deep Dive (3-5 slides)
- Technical details
- Code examples
- Configuration/setup
6. Best Practices (2-3 slides)
- Do's and don'ts
- Performance tips
- Security considerations
7. Case Study/Real-World Example (1-2 slides)
- Practical application
- Results/impact
8. Conclusion & Next Steps (1-2 slides)
- Key takeaways
- Resources
- Call to action
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 · 215 lines · 91 tokens per session scan A 7b52f663d32e
dev-camp-deck is a skill published in the GitHub repository microsoft/copilot-camp (654 stars, last pushed 18d ago), licensed MIT. It adds 91 tokens to every session and 1,480 once invoked, about $0.0005 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
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…