codex-hygiene

Audit Codex Desktop context and tool surfaces with read-only SQLite telemetry queries.

251|7|Updated Jul 7, 2026
One-click install
npx skills add https://github.com/sunflower-of-parchman/codex-hygiene --skill codex-hygiene
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: codex-hygiene
Source: https://github.com/sunflower-of-parchman/codex-hygiene/tree/main
Command: npx skills add https://github.com/sunflower-of-parchman/codex-hygiene --skill codex-hygiene

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Codex Hygiene addresses the need for auditing and tuning Codex Desktop's context and tool surfaces, helping users measure recent telemetry, review availability, and maintain scoped workflows.

Core Features & Use Cases

  • Telemetry Measurement: Measures tool-list and per-thread token telemetry with read-only SQLite queries.
  • Availability Review: Identifies app surface size, MCP/plugin state, and snapshot reuse.
  • Hygiene Suggestions: Suggests reversible steps to maintain system health without deleting logs or caches.
  • Workflow Scope: Keeps long-running goal workflows scoped to the current work, enhancing quality and efficiency.

Quick Start

Run the measure_codex_context.sh script to measure Codex Desktop context and tool surfaces.

Frequently Asked Questions about codex-hygiene

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit Codex Desktop tool surfaces and telemetry?

Auditing Codex Desktop tool surfaces involves running read-only SQLite queries via the measure_codex_context.sh script to measure tool-list and per-thread token telemetry, identifying app surface size and plugin state without modifying logs or caches.

What is the best way to measure per-thread token telemetry in Codex Desktop?

Measuring per-thread token telemetry in Codex Desktop is done through read-only SQLite queries that analyze recent telemetry data, allowing you to review tool-list availability and maintain scoped workflows for long-running goals.

Do I need Bash and sqlite3 to run Codex Desktop context audits?

Running Codex Desktop context audits requires Bash, sqlite3, Perl, awk, and sort for execution, ensuring the read-only queries can accurately measure telemetry and assess system health within the environment.

Can I review MCP plugin state in Codex Desktop without deleting logs?

Reviewing MCP plugin state in Codex Desktop uses read-only queries that identify app surface size and snapshot reuse, providing reversible hygiene suggestions to maintain system health without deleting logs or caches.

Why does my long-running goal workflow lose context scope in Codex Desktop?

Long-running goal workflows in Codex Desktop lose context scope when tool surfaces are not properly tuned, requiring telemetry measurement and hygiene adjustments to keep workflows scoped to current work and enhance efficiency.

What are the limitations of using read-only SQLite queries for Codex Desktop hygiene?

Read-only SQLite queries for Codex Desktop hygiene are limited to analyzing recent telemetry and suggesting reversible steps, meaning they cannot directly delete logs, clear caches, or automatically apply system modifications.