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/omnigent-ai/omnigent/copilot-sdk-e2e-devnpx skills add omnigent-ai/omnigent --skill copilot-sdk-e2e-devgit clone --depth 1 https://github.com/omnigent-ai/omnigentWhat 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.00095 | $0.03028 |
| Opus 5 | $0.00048 | $0.01514 |
| Sonnet 5 | $0.00019 | $0.00606 |
| Haiku 4.5 | $0.00010 | $0.00303 |
Grade C, and why
copilot-sdk-e2e-dev scanned grade C with 2 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 3d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf /tmp/copilot-dev # remove scratch bundles Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s http://127.0.0.1:7788/health # {"status":"ok"} 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.
Copilot SDK harness: end-to-end dev & testing
The copilot harness drives the GitHub Copilot SDK (github-copilot-sdk,
imported as copilot) — a persistent CopilotClient + CopilotSession per
Omnigent conversation — and bridges Omnigent's sys_* tools into Copilot as SDK
Tools. The Python SDK bundles the Copilot CLI binary it drives as a backing
server, so there is no separate @github/copilot install. This skill is the
proven recipe for running it for real against a live local server — not just
the unit tests.
The harness runs as a local runner from your current checkout, so
omni run <bundle> --server <url>exercises exactly the code you're on.
Prerequisites (check these first)
- You're on the branch you want to test. The copilot harness is an
optional extra — install it (without disturbing other extras) with
uv sync --frozen --group test --extra copilot. NB: a bareuv run --frozen --group testre-syncs the venv and prunes the copilot SDK; for live testing call.venv/bin/omni/.venv/bin/pythondirectly and avoiduv runmid-session. - The SDK is installed:
.venv/bin/python -c "import copilot; print(copilot.__file__)". - A GitHub token with Copilot access is configured. Copilot needs a
fine-grained PAT with the "Copilot Requests" permission, or an OAuth token
from the GitHub CLI / Copilot CLI app (classic
ghp_PATs are rejected). Verify (booleans only — never print the token):
If both are.venv/bin/python -c "from omnigent.onboarding.copilot_auth import copilot_github_token_configured; import os; print('config:', copilot_github_token_configured(), 'env:', bool(os.environ.get('GH_TOKEN') or os.environ.get('COPILOT_GITHUB_TOKEN')))"False, runomni setupand register a Copilot token, orexport GH_TOKEN=$(gh auth token)(whenghis logged into an account with Copilot). Check the account's entitlement withgh api /copilot_internal/user(look forchat_enabled/cli_enabled). - Network egress to GitHub's Copilot backend. A turn that hangs or fails to connect on a locked-down host is usually egress, not a harness bug.
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.
- 3d ago First seen · 215 lines · 95 tokens per session scan C 7133791b667b
copilot-sdk-e2e-dev is a skill published in the GitHub repository omnigent-ai/omnigent (9,591 stars, last pushed yesterday), licensed Apache-2.0. It adds 95 tokens to every session and 3,028 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it C with 2 findings (recursive force delete, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
agent-production-validator
Agent skill for production-validator - invoke with $agent-production-validator.
inspector-workbench
Runs Inspector UI work on the standalone Threads state lab so the agent can see the overlay. Use when a CopilotKit employee asks an agent to fix, polish, add, or debug Inspector UI, chrome, panes, overlay actions, launcher, Home, Threads, Playground, Memory, or any visual behavior in @copilotkit/web-inspector. Don't…
playwright-cli
Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.
cli-e2e
Write, modify, or debug Docker-based Composio CLI end-to-end tests under ts/e2e-tests/cli, including binary invocation, fixture isolation, output assertions, and package manifests. Use for CLI E2E test suites only; use cli-command for CLI source implementation.
typescript-testing
Select and run TypeScript SDK verification for packages, examples, type checks, linting, builds, Vitest suites, and runtime E2E tests. Use when adding tests, diagnosing TypeScript CI, choosing a focused test command, or validating TypeScript package changes. Do not use for Python-only checks.
agent-integration
Run all three agent integration phases sequentially: research, write-tests, and implement using E2E-first TDD (unit tests written last). For individual phases, use /agent-integration:research, /agent-integration:write-tests, or /agent-integration:implement. Use when the user says "integrate agent", "add agent…