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/pi-native-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/pi-native-e2e-dev)<a href="https://agentmods.dev/skills/omnigent-ai/omnigent/pi-native-e2e-dev"><img src="https://agentmods.dev/badge/skills/omnigent-ai/omnigent/pi-native-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/pi-native-e2e-dev"><img src="https://agentmods.dev/badge/skills/omnigent-ai/omnigent/pi-native-e2e-dev.svg" alt="Reviewed on agentmods" width="80" 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.00118 | $0.03594 |
| Opus 5.5 | $0.00047 | $0.01438 |
| Sonnet 5.5 | $0.00024 | $0.00719 |
| Haiku 4.5 | $0.00012 | $0.00359 |
Grade E, and why
pi-native-e2e-dev scanned grade E with 3 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 26d 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.
Downloads and executes remote codehighSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
curl -s "$SERVER/v1/sessions/$CONV/items" | python -m json.tool | tail -40 Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
# rm -rf "$(.venv/bin/python -c "from omnigent.pi_native import pi_bridge_dir_for_session as d; print(d('$CONV'))")" Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s "$SERVER/health" # {"status":"ok"} How it starts
The opening of the file, as written. The whole thing — 260 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pi native harness: end-to-end dev & testing (local server/runner)
The pi-native harness wraps the real Pi coding-agent TUI
(@earendil-works/pi-coding-agent, the pi CLI). Unlike the SDK harnesses
(cursor / copilot / antigravity), it does not run in-process: omnigent pi
ensures a host daemon, the daemon spawns a runner that launches pi inside a
runner-owned tmux terminal, and your TTY attaches to it. Omnigent's web-UI
turns are forwarded into that live pi process through a file-inbox bridge +
a packaged JS extension (pi.sendUserMessage). This skill is the proven
recipe for running it for real against a live local server + runner — not
just the unit tests.
Like the other harnesses, the runner imports from your current checkout, so testing here exercises exactly the code you're on. (CWD/venv selects the code, not
PYTHONPATH.)
What actually runs where
your TTY ── (attach / pexpect) ──► omnigent pi (CLI, local)
│ ensures
▼
host daemon ──► local Omnigent server (AP)
│ spawns ▲
▼ │ HTTP
runner ── launches ──► pi (TUI, in tmux)
│ loads
▼
omnigent pi-native extension (JS)
Two ways a turn reaches Pi — test both:
- Type in the TUI (your attached terminal). Exercises Pi natively; the
extension mirrors the transcript back to the server (
POST …/events). - Web / API message. Server → runner →
PiNativeExecutor.run_turn→enqueue_user_message()writesinbox/<ordinal>_msg_*.json→ the resident extension polls the inbox →pi.sendUserMessage(...). This is the harness-specific path most worth covering.
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.
- 26d ago Changed efb1932f6366
- 2mo ago First seen · 260 lines · 118 tokens per session scan E 8216b949de9e
pi-native-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 118 tokens to every session and 3,594 once invoked, about $0.0005 per session on Opus 5.5. A static security scan graded it E with 3 findings (downloads and executes remote code, 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.