kempt-checkup

kempt-checkup is a skill for Codex from xz1220/Kempt. It costs 89 tokens per session (647 once invoked), scanned A, original, MIT.

A read-only health check for local AI coding-agent files and settings. It looks for accumulated problems such as stale instructions, unused tools, and conflicting configuration.

In plain words
What is it for?
Use it to scan the local agent state, report a health score and problem areas, and identify the most important cleanup items.
Why use it?
It shows what may be making an agent slow, inconsistent, or confused without changing the files it examines.

Skill for Codex

Written for Codex: reads ~/.codex or $CODEX_HOME. Also seen: reads .claude/ paths; mentions Claude Code; mentions Codex.

Good fit Use it to scan the local agent state, report a health score and problem areas, and identify the most important cleanup items.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/xz1220/kempt/kempt-checkup
View source ↗ xz1220/Kempt
Install

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.

Any agent
npx skills add xz1220/Kempt --skill kempt-checkup
Clone the repo
git clone --depth 1 https://github.com/xz1220/Kempt

Made for: Codex.

Wrote 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.

agentmods badge for kempt-checkup

README.md
[![agentmods](https://agentmods.dev/badge/skills/xz1220/kempt/kempt-checkup/github.svg)](https://agentmods.dev/skills/xz1220/kempt/kempt-checkup)
Your own site
<a href="https://agentmods.dev/skills/xz1220/kempt/kempt-checkup"><img src="https://agentmods.dev/badge/skills/xz1220/kempt/kempt-checkup/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.

agentmods 80×15 button for kempt-checkup

Your own site · 80×15
<a href="https://agentmods.dev/skills/xz1220/kempt/kempt-checkup"><img src="https://agentmods.dev/badge/skills/xz1220/kempt/kempt-checkup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 89 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 647 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00089 $0.00647
Opus 5 $0.00044 $0.00324
Sonnet 5 $0.00018 $0.00129
Haiku 4.5 $0.00009 $0.00065

Measured 11d ago against content hash 1cfe95c5a7fd, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

kempt-checkup scanned grade A with 0 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 11d 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.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/kempt-checkup/SKILL.md · 50 lines

How it starts

The opening of the file, as written. The whole thing — 50 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Kempt Checkup — diagnose agent debt (read-only)

You are running a read-only diagnosis of the user's local agent state with the Kempt CLI. Nothing is modified, nothing leaves the machine.

Steps

  1. Locate the CLI. Run command -v kempt. If missing, try node <kempt-repo>/bin/kempt.mjs (ask the user where the Kempt repo is, or suggest npm install && npm link inside it). Use whichever works as $KEMPT below.

  2. Scan. Run:

    kempt scan --json
    

    This performs the read-only scan and prints the full report as JSON.

  3. Interpret the report for the user. From the JSON, extract:

    • healthScore (0–100) and verdict
    • the five dimensions (memory / tools / conflict / runtime / reclaimable), each with severity (crit/warn/good), metricValue and summary
    • summary.totalFindings and summary.reclaimableBytes
    • worstDimension — lead with this one.

    Present a short, plain-language readout in the user's language: what is hurting the agent most, why it matters (stale memory gets re-read every session; unused skills eat context budget; conflicting instructions make behavior random), and the 2–3 highest-impact items from findings (use title + reason; findings are already path-redacted).

  4. Offer the next step, don't take it. If anything is cleanable, tell the user a reversible cleanup is available via the kempt-clean skill or kempt clean (dry-run by default). Do not clean anything in this skill.

Rules

  • This skill is strictly read-only: only kempt scan, kempt report, kempt plan and kempt history may be run. Never run kempt clean --yes or kempt empty-recycle here.
  • Never paste raw secrets or file contents into the conversation; the report is already redacted — stick to what it provides.
  • If the scan fails, show the error and suggest kempt help; do not retry more than once.
  • Health score bands for your summary: ≥80 tidy ("kempt"), 60–79 needs a tidy-up, 40–59 noticeable debt, <40 the agent is being actively degraded.

Read the full file on GitHub · 50 lines

Changes

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.

  1. 11d ago First seen · 50 lines · 89 tokens per session scan A 1cfe95c5a7fd

Subscribe to this mod's changes

kempt-checkup is a skill published in the GitHub repository xz1220/Kempt (2 stars, last pushed 3mo ago), licensed MIT. It adds 89 tokens to every session and 647 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

codegraph

Analyze indexed codebases via graph database (neug) and vector index (zvec). Covers call graphs, dependencies, dead code, hotspots, module coupling, architecture reports, semantic search, impact analysis, bug root cause from GitHub issues, class diagrams (UML), and PR review (risk scoring, conflict detection…

QwenLM/qwen-code · 0 tokens

stuck

Diagnose frozen, stuck, or slow Qwen Code sessions on this machine. Scans for problematic processes, high CPU/memory usage, hung subprocesses, and debug logs. Use /stuck or /stuck to focus on a specific process.

QwenLM/qwen-code · 57 tokens

structured-debugging

Hypothesis-driven debugging methodology for hard bugs. Use this skill whenever you're investigating non-trivial bugs, unexpected behavior, flaky tests, or tracing issues through complex systems. Activate proactively when debugging requires more than a quick glance — especially when the first attempt at a fix didn't…

QwenLM/qwen-code · 85 tokens

memory-leak-debug

Diagnose memory leaks in the Qwen Code CLI using heap snapshots and the chrome-devtools CLI. Use when investigating high memory usage, unbounded growth, or suspected object retention issues.

QwenLM/qwen-code · 42 tokens

bugfix

Fix a bug from a GitHub issue, following the reproduce-first workflow. Use when the user asks to fix a bug, investigate a GitHub issue, or debug a user-reported problem. Takes a GitHub issue URL or number as input.

QwenLM/qwen-code · 53 tokens

autofix

Review and repair current local changes until they converge, or run Qwen Code Autofix issue and review workflows from GitHub Actions.

QwenLM/qwen-code · 30 tokens