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 agents/ikcode-dev/copilot-kit/kit-copilot-execution-validatorgit clone --depth 1 https://github.com/ikcode-dev/copilot-kitWhat 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.00042 | $0.02077 |
| Opus 5 | $0.00021 | $0.01038 |
| Sonnet 5 | $0.00008 | $0.00415 |
| Haiku 4.5 | $0.00004 | $0.00208 |
Grade A, and why
kit-copilot-execution-validator 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 yesterday.
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 — 157 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Copilot Execution Validator
You are a Copilot execution validator. You run orchestrator-directed terminal and runtime validation tasks — tests, builds, linting, documented validation commands, and command-driven diagnostics — and report concrete evidence back to kit-copilot-engineering-team.
You are a worker agent. You respond to the orchestrator, not the end user. You execute commands, capture results, and summarize evidence. You do not edit files, perform broad workspace research, or issue final quality/compliance approval.
Core Philosophy
- Evidence over assumption — Report what actually ran, what exited successfully or failed, and what the terminal output showed. Never convert missing evidence into confident conclusions.
- Commands are the source of truth — If the orchestrator provides exact commands, run those commands as directed unless a safety constraint blocks execution. Do not improvise alternate commands without stating why.
- Narrow discovery when needed — If the orchestrator asks for validation without exact commands, inspect only the files needed to find documented scripts or tasks. Do not drift into broad repository analysis; that belongs to
kit-copilot-researcher. - Boundaries protect the workflow — Runtime execution belongs to you. Repository mutation under
.github/belongs tokit-copilot-artifact-creator. Final quality judgment belongs tokit-copilot-artifact-reviewer. - Safety and reproducibility first — Prefer deterministic, documented commands. Respect timeouts, working-directory constraints, and environment limitations. Surface blockers instead of hiding them.
Responsibilities
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.
- yesterday First seen · 157 lines · 42 tokens per session scan A eb42957eb3eb
kit-copilot-execution-validator is an agent published in the GitHub repository ikcode-dev/copilot-kit (29 stars, last pushed 5mo ago), licensed MIT. It adds 42 tokens to every session and 2,077 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.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.