Omnigent is an open-source orchestration layer for running and coordinating different AI coding agents through one system. It is for developers who want to combine agents, apply policies and sandboxing, and continue sessions across devices. The catalogue add-ons extend its agent workflows.
Borrowing it
Nothing to install: this file belongs to omnigent-ai/omnigent. 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/omnigent-ai/omnigent/main/.claude/skills/copilot-sdk-e2e-dev/SKILL.mdgit clone --depth 1 https://github.com/omnigent-ai/omnigentWrote 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/skills/omnigent-ai/omnigent/copilot-sdk-e2e-dev)<a href="https://agentmods.dev/skills/omnigent-ai/omnigent/copilot-sdk-e2e-dev"><img src="https://agentmods.dev/badge/skills/omnigent-ai/omnigent/copilot-sdk-e2e-dev/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/omnigent-ai/omnigent/copilot-sdk-e2e-dev"><img src="https://agentmods.dev/badge/skills/omnigent-ai/omnigent/copilot-sdk-e2e-dev.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Tool Misuse · line 212 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
- high Tool Misuse · line 212 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
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.00095 | $0.03028 |
| Opus 5.5 | $0.00038 | $0.01211 |
| Sonnet 5.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 21d 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.
- 21d ago Changed 443b9fe8c33d
- 2mo 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 (11,100 stars, last pushed today), licensed Apache-2.0. It adds 95 tokens to every session and 3,028 once invoked, about $0.0004 per session on Opus 5.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
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.
emulate-seed
Generate emulate seed configs for stateful API emulation. Wraps Vercel's emulate tool for GitHub, Vercel, Google OAuth, Slack, Apple Auth, Microsoft Entra, AWS, Okta, Clerk, Resend, Stripe, and MongoDB Atlas APIs — full state machines, not mocks. Use when setting up test environments, CI pipelines, integration tests…
testing-e2e
End-to-end testing patterns with Playwright — page objects, AI agent testing, visual regression, accessibility testing with axe-core, and CI integration. Use when writing E2E tests, setting up Playwright, implementing visual regression, or testing accessibility.
design-ship
One-shot pipeline turning a claude.ai/design link into a pull request: scaffold via /ork:design-import, stories and specs via /ork:cover, browser verification via /ork:expect, then open the PR. Use when a design link should come back as a PR with no intermediate steps; if all you need is the components written to…
storybook-testing
Storybook 10 testing patterns with Vitest integration, ESM-only distribution, CSF3 typesafe factories, play() interaction tests, Chromatic TurboSnap visual regression, module automocking, accessibility addon testing, and autodocs generation. Use when writing component stories, setting up visual regression testing…
testing-patterns
Redirect — testing-patterns was split into 5 focused sub-skills. Use when looking for testing-patterns, writing tests, or test automation. Redirects to testing-unit, testing-e2e, testing-integration, testing-llm, or testing-perf.