Maintainer of this skill?
by EvannZhongg
Nosis is a lightweight personal agent runtime: per-session execution boundaries with OS-level sandboxing, computer use, a full built-in toolset, Skill / Plugin / MCP extensions, one runtime shared by GUI and TUI, and file-persisted sessions, plans, and memory.
# Add to your Claude Code skills
git clone https://github.com/EvannZhongg/NosisLast scanned: 10/21/2026
{
"issues": [
{
"type": "npm-audit",
"message": "@vitest/mocker: Vitest: Path Traversal / Arbitrary File Read via @vitest/mocker Redirect Mock",
"severity": "medium"
},
{
"type": "npm-audit",
"message": "source-map-js: source-map-js allows event-loop denial of service through indexed source-map section offsets",
"severity": "high"
},
{
"type": "npm-audit",
"message": "tinypool: Tinypool: Prototype Pollution gadget in worker options leads to Remote Code Execution",
"severity": "critical"
},
{
"type": "npm-audit",
"message": "vite: launch-editor: escapeCmdArgs() omits % escaping on Windows",
"severity": "high"
},
{
"type": "npm-audit",
"message": "vitest: Vulnerability found",
"severity": "critical"
}
],
"status": "FAILED",
"scannedAt": "2026-10-21T09:09:31.226Z",
"npmAuditRan": true,
"pipAuditRan": true,
"promptInjectionRan": true
}See how Nosis compares with popular alternatives.
Nosis is an open-source ai agents skill for AI coding assistants such as Claude Code, Codex CLI, and ChatGPT, built by EvannZhongg. Nosis is a lightweight personal agent runtime: per-session execution boundaries with OS-level sandboxing, computer use, a full built-in toolset, Skill / Plugin / MCP extensions, one runtime shared by GUI and TUI, and file-persisted sessions, plans, and memory. It has 176 GitHub stars.
Nosis failed SkillsLLM's automated security scan, which flagged one or more high-severity issues. Review the Security Report section carefully before using it.
Clone the repository with "git clone https://github.com/EvannZhongg/Nosis" and add it to your Claude Code skills directory (see the Installation section above).
Nosis is primarily written in Python. It is open-source under EvannZhongg on GitHub, so you can review or fork the full source.
Yes. SkillsLLM lists many other AI Agents skills you can browse and compare side by side. Open the AI Agents category from the badge at the top of this page, or use the Related Skills and comparison links further down to weigh Nosis against similar tools.
No comments yet. Be the first to share your thoughts!
Requires a passing catalog security scan.
⚠️ Third-Party Software Notice
This skill is third-party open-source software developed and hosted independently on GitHub. SkillsLLM is an informational directory and does not control or maintain the underlying repository.
Any security checks, ratings, or warnings displayed by SkillsLLM are automated and limited in scope. They do not constitute a security certification or guarantee that the software is safe, error-free, or free from malicious code, vulnerabilities, compromised dependencies, or prompt-injection risks.
Review the source code, permissions, dependencies, and configuration before installing or running any third-party skill. Use is at your own risk. To the maximum extent permitted by applicable law, SkillsLLM is not liable for losses arising from third-party software.
Nosis is an open-source, lightweight personal agent application. It provides local workspace operations, human approval, session persistence, context management, long-term memory, plans, subagents, scheduled tasks, and Skill / Plugin / MCP extensibility — with both a TUI and a GUI.
TUI ────────────┐
├── Bridge ── agent_runtime ── agent_core
GUI ── FastAPI ─┘
agent_core provides frontend-agnostic agent mechanisms.agent_runtime reads application configuration and assembles the Core into a runnable instance.Ask for approval, Workspace Access, and Full Access. Shell enters the workspace sandbox or the host environment according to scope, while file tools are always confined to the current workspace.computer_screenshot and computer_action, covering screenshots, clicks, drags, scrolling, key presses, and text input. Both tools are on by default and visible only to the main agent, and each call is confirmed according to the current permission preset.web_fetch reads public pages directly or via DeepSeek; web_search, when enabled, queries DuckDuckGo by default and can switch to Exa or DeepSeek.Requirements: Python >= 3.11, Node.js >= 22, and uv.
git clone https://github.com/EvannZhongg/Nosis.git
cd Nosis
npm install
npm run build
uv tool install --editable ".[gui]"
If you create the project environment with uv sync, install the GUI extra as well, otherwise Uvicorn cannot serve the session WebSocket:
uv sync --extra gui
Start the TUI once in the current directory:
nosis
The first launch initializes ~/.nosis/. After quitting the TUI, create ~/.nosis/.env and fill in the environment variables required by the default provider, for example:
OPENAI_KEY=your-api-key
Then restart the TUI:
nosis
Or start the GUI:
nosis-gui
The GUI listens on http://127.0.0.1:8737 by default.
Third-party frontends can launch the installed nosis-bridge command and use the
public stdio protocol or the lightweight
@nosis/client TypeScript SDK. See the
protocol review and design for the public/internal boundary.
| Document | Scope |
|---|---|
agent_core |
Agent loop, context, session, tools, execution, permissions, memory, plans, jobs, scheduler, providers, skills, and MCP mechanisms |
agent_runtime |
Configuration, prompts, plugin discovery, runtime assembly, execution plane, session binding, and turn entry |
interfaces/bridge |
The standalone Bridge process, protocol routing, event translation, and frontend interaction forwarding |
interfaces/protocol |
The TypeScript protocol types and connection-state conventions shared by the TUI and GUI |
interfaces/client |
Public Node/TypeScript stdio client, process lifecycle and integration example |
interfaces/tui |
The Ink terminal interface, commands, input state, and Bridge subprocess attachment |
interfaces/gui |
The FastAPI service, React interface, multi-session connections, HTTP / WebSocket API, and media access |
agent_runtime creates the configuration directory on first launch and is responsible for reading and updating the application configuration inside it:
| Path | Contents |
|---|---|
~/.nosis/provider_config.json |
Providers, models, and role routing, including the optional fast_model |
~/.nosis/agent_config.json |
Tools, context, memory, skill paths, subagents, MCP, workspace instructions, and scratch workspace settings |
~/.nosis/tool_config.json |
Web Search and Web Fetch provider selection and API keys |
~/.nosis/.env |
The secrets and environment variables referenced by the configuration |
~/.nosis/prompts/ |
Main agent, subagent, compaction, and memory prompts |
~/.nosis/skills/ |
Standalone skills |
~/.nosis/plugins/ |
Plugin capability packages |
~/.nosis/AGENTS.md |
User-level global workspace instruction |
~/.nosis/MEMORY.md |
Global long-term memory |
~/.nosis/sessions/ |
Session journals, workspace memory, artifacts, subagent records, and per-session auxiliary usage logs |
~/.nosis/schedule.jsonl |
Scheduled tasks and run records |
<workspace>/.nosis/attachments/ |
Uploaded attachments and agent-generated images |
The default configuration and built-in resources live in agent_runtime/defaults/. See agent_runtime/README.md for how assembly works.
Python tests use a mock provider and need no real API key:
python -m venv .venv
source .venv/bin/activate
python -m pip install -e ".[gui]"
python -m unittest discover -s tests -v
On Windows, activate the environment with .venv\Scripts\Activate.ps1.
The GUI extra includes FastAPI, Uvicorn, the WebSocket backend, and multipart support; Windows, macOS, and Linux use the same installation.
Frontend build, type checking, and tests:
npm run build
npm run typecheck
npm test
The Linux sandbox integration tests require a working bubblewrap and user namespaces; when the runtime conditions are not met, the tests explicitly skip.
On Windows the shell tool uses PowerShell 7, so PowerShell 7 has to be installed separately.