Borrowing it
Nothing to install: this file belongs to Rikuto-des/slide-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Rikuto-des/slide-mcp/main/.github/copilot-instructions.mdgit clone --depth 1 https://github.com/Rikuto-des/slide-mcpWrote 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/instructions/rikuto-des/slide-mcp/copilot-instructions)<a href="https://agentmods.dev/instructions/rikuto-des/slide-mcp/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/rikuto-des/slide-mcp/copilot-instructions.svg" alt="Measured on agentmods" 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.00745 | $0.00745 |
| Opus 5 | $0.00373 | $0.00373 |
| Sonnet 5 | $0.00149 | $0.00149 |
| Haiku 4.5 | $0.00075 | $0.00075 |
Grade A, and why
slide-mcp copilot-instructions.md 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 — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
slide-mcp — Copilot instructions
This repo is slide-mcp: a Figma Slides plugin + local MCP/WebSocket bridge that
lets you generate designed Figma slides from chat. When the user asks to make,
build, or generate slides / a deck / a presentation, use the create_deck MCP
tool exposed by the slide-mcp server.
Generating a deck
Call create_deck with { replace?, theme?, slides: [...] }:
replace: truerecreates the deck from scratch (clears existing slides); omit to append.- The slide-mcp plugin must be running in Figma Slides (its panel shows "Connected"). If the tool errors, tell the user to run it (Plugins → Development → slide-mcp).
Design well:
- Vary layouts across the deck (use ≥ 5 different ones). Don't make every slide a bullet list.
- One idea per slide. Short bullets (≤ ~12 words, ≤ 5 per slide). Short titles.
- Pick the layout that fits the content (see below). Numbers → stats/charts; A vs B → compare; process → steps/timeline; etc.
- Arc: cover → agenda → sections/content → closing (or a statement).
Layouts (slide.layout)
cover, section, content, two-col, checklist, agenda, split (term/desc), statement, callout, stats, big-number, bars, progress, donut, line, funnel, pyramid, steps, timeline, compare, cards, table, split-mix, team, testimonial, image-right, image-left, hero, gallery, code.
Data per layout:
- text:
title,bullets[]; split/compare/cards/stats/steps/timeline/charts useitems[]({ title, value, label, desc, bullets[], image }). - charts (bars/progress/donut/line/funnel/pyramid):
items[].label+items[].value(value contains a number). - table:
slide.table.headers[]+slide.table.rows[][]. - images (image-right/left/hero):
slide.image(URL). gallery/team:items[].image. - code:
slide.bodyis the code (newlines preserved). - Omit
layoutto auto-detect.
Design systems (theme.preset)
Light: light (default), sky, ocean, emerald, forest, warm, sunset, rose, plum,
indigo, mono, paper. Dark: dark, midnight, graphite, carbon, royal.
Set deck-wide via theme.preset, or per slide via slide.theme.preset. If you
omit it, the system selected in the plugin panel is used. Override colors with
theme.accent / background / titleColor / etc.
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 · 55 lines · 745 tokens per session scan A db03034685a7
slide-mcp copilot-instructions.md is an instructions file published in the GitHub repository Rikuto-des/slide-mcp (0 stars, last pushed 2mo ago), licensed MIT. It adds 745 tokens to every session, about $0.0037 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 instructions, from other repositories
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.