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/nevaberry/nevaberry-plugins/codex-knowledge-patchnpx skills add Nevaberry/nevaberry-plugins --skill codex-knowledge-patchgit clone --depth 1 https://github.com/Nevaberry/nevaberry-pluginsWhat 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.00009 | $0.01783 |
| Opus 5 | $0.00005 | $0.00892 |
| Sonnet 5 | $0.00002 | $0.00357 |
| Haiku 4.5 | $0.00001 | $0.00178 |
Grade B, and why
codex-knowledge-patch scanned grade B with 1 finding 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 2d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
Settings go to `~/.codex/config.toml` or the selected profile. `--search` How it starts
The opening of the file, as written. The whole thing — 184 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Codex Knowledge Patch
Use this skill when working with the Codex desktop app, CLI, TUI, remote app server, MCP integrations, cloud tasks, plugins, or collaborative agent workflows.
Reference index
| Reference | Topics |
|---|---|
| app-and-collaboration.md | Desktop platforms, projects, skills, automations, imports, browser and voice context, image review, iOS |
| security-and-configuration.md | Approval and sandbox modes, flags, feature settings, search, login, policy checks, diagnostics, Windows behavior |
| remote-mcp-and-connectors.md | Remote TUI security, app-server authentication, MCP, connectors, proxied WebSockets, plugin sign-in |
| cli-execution-and-cloud.md | Scripted execution, resume and review, cloud tasks, plugin marketplaces, desktop launching |
| tui-and-session-controls.md | Steering, prompt editing, themes, planning, conversation controls, status UI, background commands, subagents |
Replace deprecated approval behavior
Choose among the supported untrusted, on-request, and never approval
policies. on-failure is deprecated. --full-auto combines the workspace-write
sandbox with on-request approvals. --yolo bypasses sandboxing and approval
prompts, so reserve it for an externally isolated environment.
Read security-and-configuration.md before changing approval, sandbox, authentication, policy, or search settings.
Account for hosted Code Mode approvals
Since 0.144.0, Code Mode defaults to hosted mode. Every approval request
causes an elicitation pause. The writes app-approval mode lets declared
read-only app actions proceed without prompting but requires approval for
writes.
Use interactive MCP authentication directly
Since 0.144.0, MCP tools may request interactive authentication without an
experimental opt-in. App-server hosts may provide authentication at runtime,
hosted login may redirect success to a hosted page, and long-running app
sessions refresh expired authentication for the hosted codex_apps connector.
What ships with it
6 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2d ago First seen · 184 lines · 9 tokens per session scan B e89b0c48ca43
codex-knowledge-patch is a skill published in the GitHub repository Nevaberry/nevaberry-plugins (24 stars, last pushed 5d ago), licensed MIT. It adds 9 tokens to every session and 1,783 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
design-mcp-server
Design the tool surface, resources, and service layer for a new MCP server. Use when starting a new server, planning a major feature expansion, or when the user describes a domain/API they want to expose via MCP. Produces a design doc at docs/design.md that drives implementation.
api-context
Canonical reference for the unified Context object passed to every tool and resource handler in @cyanheads/mcp-ts-core. Covers the full interface, its RequestContext base, all sub-APIs (ctx.log, ctx.state, ctx.requestInput, ctx.inputs, ctx.enrich, ctx.content), and when to use each.
api-canvas
DataCanvas primitive reference — a Tier 3 SQL/analytical workspace for tabular MCP servers, backed by DuckDB. Use when registering tables from upstream APIs, running ad-hoc SQL across them, and exporting results. Covers the acquire → register → query → export flow, per-table TTL, the token-sharing pattern for…
api-testing
Testing patterns for MCP tool/resource handlers using createMockContext and Vitest. Covers mock context options, handler testing, McpError assertions, format testing, Vitest config setup, and test isolation conventions.
field-test
Exercise tools, resources, and prompts against a live HTTP server via MCP JSON-RPC over curl. Starts the server, surfaces the catalog, runs real and adversarial inputs, and produces a tight report with concrete findings and numbered follow-up options. Use after adding or modifying definitions, or when the user asks to…
maintenance
Investigate, adopt, and verify dependency updates — with special handling for @cyanheads/mcp-ts-core. Captures what changed, understands why, cross-references against the codebase, adopts framework improvements, syncs project skills, and runs final checks. Supports two entry modes: run the full flow end-to-end, or…