edit-triggers

edit-triggers is a skill for Claude Code from microsoft/skills-for-copilot-studio. It costs 33 tokens per session (1,063 once invoked), scanned A, original, MIT.

A tool for changing the phrases and descriptions that determine when a Copilot Studio topic starts. A topic is a conversation flow within an agent.

In plain words
What is it for?
Use it to add, remove, or edit trigger phrases and to change a topic's model description.
Why use it?
It helps you control how the agent routes user messages to the right conversation flow. It also accounts for whether the agent uses generative orchestration, where an AI system chooses the topic from its description.

Skill for Claude Code ✓ vendor

Written for Claude Code: allowed-tools in frontmatter. Also seen: agent in frontmatter.

Part of the copilot-studio plugin — 31 skills, 4 agents, 1 hook shipped together

Good fit Use it to add, remove, or edit trigger phrases and to change a topic's model description.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/microsoft/skills-for-copilot-studio/edit-triggers
About the project

Skills for Copilot Studio is a plugin for authoring, testing, and troubleshooting standard Microsoft Copilot Studio agents as YAML files from a terminal or editor. It is intended for users of Claude Code, GitHub Copilot CLI, and VS Code who work with Copilot Studio agents. The catalogue add-ons are the plugin's skills, agents, hook, and plugin definition.

microsoft/skills-for-copilot-studio · 432 stars · on GitHub

Install

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.

Any agent
npx skills add microsoft/skills-for-copilot-studio --skill edit-triggers
Clone the repo
git clone --depth 1 https://github.com/microsoft/skills-for-copilot-studio

Made for: Claude Code.

Or install copilot-studio, the plugin that ships this one along with the rest of its 31 skills, 4 agents, 1 hook.

Wrote 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.

agentmods badge for edit-triggers

README.md
[![agentmods](https://agentmods.dev/badge/skills/microsoft/skills-for-copilot-studio/edit-triggers.svg)](https://agentmods.dev/skills/microsoft/skills-for-copilot-studio/edit-triggers)
Your own site
<a href="https://agentmods.dev/skills/microsoft/skills-for-copilot-studio/edit-triggers"><img src="https://agentmods.dev/badge/skills/microsoft/skills-for-copilot-studio/edit-triggers.svg" alt="Measured on agentmods" height="20"></a>
Per session 33 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,063 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00033 $0.01063
Opus 5 $0.00016 $0.00531
Sonnet 5 $0.00007 $0.00213
Haiku 4.5 $0.00003 $0.00106

Measured 8d ago against content hash c8c028a5b1ba, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

edit-triggers 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 8d 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.

skills/edit-triggers/SKILL.md · 118 lines

How it starts

The opening of the file, as written. The whole thing — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Edit Topic Triggers

Modify how a topic gets triggered: trigger phrases (triggerQueries) and model description (modelDescription).

Instructions

  1. Auto-discover the agent directory:

    Glob: **/agent.mcs.yml
    

    NEVER hardcode an agent name.

  2. Find the target topic:

    Glob: <agent-dir>/topics/*.topic.mcs.yml
    

    If $ARGUMENTS specifies a topic name, match it. Otherwise, list all topics and ask which one.

  3. Read the topic file and identify what to change.

  4. Check the agent's settings.mcs.yml for GenerativeActionsEnabled. This determines which trigger mechanism matters most.

  5. Make the requested changes using the Edit tool.

Model Description (modelDescription)

The modelDescription is a natural language description at the root of an AdaptiveDialog that tells the generative orchestrator when to route to this topic. When GenerativeActionsEnabled: true, this is the primary way the agent decides which topic to trigger — even more important than trigger phrases.

kind: AdaptiveDialog
modelDescription: This topic helps users order a pizza by collecting their preferred size, toppings, and delivery address.
beginDialog:
  kind: OnRecognizedIntent
  id: main
  ...

Best Practices for Model Description

  • Write a clear, specific sentence describing what the topic does and when it should be used
  • Focus on the user's intent: "Use this topic when the user asks for information about our perfumes" rather than "This topic sends a message"
  • Include key scenarios the topic covers: "This topic handles billing inquiries, refund requests, and payment issues"
  • Keep it concise but complete — the orchestrator reads this to decide routing
  • Avoid vague descriptions like "This topic handles requests" — be specific about which requests

Examples from Real Topics

# Good — specific about what the topic does and when to use it
modelDescription: Use this topic when the user asks for help or needs assistance with something. Search the SharePoint knowledge base to find relevant information.

# Good — describes the full flow
modelDescription: This topic takes the user's favorite color, generates a word by concatenating the color with four random digits, and returns the generated word. If the color is white, it also provides information about the wavelength.

# Good — describes the computation
modelDescription: This sample topic performs the sum between the two numbers in input

Read the full file on GitHub · 118 lines

Changes

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.

  1. 8d ago First seen · 118 lines · 33 tokens per session scan A c8c028a5b1ba

Subscribe to this mod's changes

edit-triggers is a skill published in the GitHub repository microsoft/skills-for-copilot-studio (432 stars, last pushed 5d ago), licensed MIT. It adds 33 tokens to every session and 1,063 once invoked, about $0.0002 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.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

microsoft/ai-agents-for-beginners · 200 tokens

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…

vercel/next.js · 95 tokens

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…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens

chronicle

Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…

microsoft/vscode · 72 tokens