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/pi-native-e2e-devnpx skills add omnigent-ai/omnigent --skill pi-native-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.00118 | $0.03574 |
| Opus 5 | $0.00059 | $0.01787 |
| Sonnet 5 | $0.00024 | $0.00715 |
| Haiku 4.5 | $0.00012 | $0.00357 |
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 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.
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.
- 3d 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 (9,591 stars, last pushed yesterday), licensed Apache-2.0. It adds 118 tokens to every session and 3,574 once invoked, about $0.0006 per session on Opus 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
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…