check-staleness

check-staleness is a skill for Claude Code from mhashim6/kauri. It costs 36 tokens per session (365 once invoked), scanned A, original, MIT.

A checker for finding potentially outdated Kauri decision records. A decision is considered stale when enough time has passed since review or when an associated file’s contents have changed.

In plain words
What is it for?
Use it when reviewing project decisions or investigating a staleness warning. It helps validate still-relevant decisions, create replacements, or mark obsolete ones as deprecated.
Why use it?
It shows which recorded decisions need attention without assuming they are wrong. Developers can confirm, replace, or retire each record after reviewing the current code.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Part of the kauri plugin — 5 skills, 2 hooks, 1 MCP server shipped together

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.

agentmods
npx agentmods add skills/mhashim6/kauri/check-staleness
Any agent
npx skills add mhashim6/kauri --skill check-staleness
Clone the repo
git clone --depth 1 https://github.com/mhashim6/kauri

Made for: Claude Code.

Or install kauri, the plugin that ships this one along with the rest of its 5 skills, 2 hooks, 1 MCP server.

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 check-staleness

README.md
[![agentmods](https://agentmods.dev/badge/skills/mhashim6/kauri/check-staleness.svg)](https://agentmods.dev/skills/mhashim6/kauri/check-staleness)
Your own site
<a href="https://agentmods.dev/skills/mhashim6/kauri/check-staleness"><img src="https://agentmods.dev/badge/skills/mhashim6/kauri/check-staleness.svg" alt="Measured on agentmods" height="20"></a>
Per session 36 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 365 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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.00036 $0.00365
Opus 5 $0.00018 $0.00182
Sonnet 5 $0.00007 $0.00073
Haiku 4.5 $0.00004 $0.00036

Measured 6d ago against content hash 4ab5c89d223e, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

check-staleness 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 6d 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.

plugins/claude-code/skills/check-staleness/SKILL.md · 36 lines

What it actually says

Check Decision Staleness

Run a staleness check on all active Kauri decisions and help the user resolve any stale records.

Steps

  1. Run the check: Use kauri_check to scan all active records.

  2. For each stale record:

    • Use kauri_show to see the full decision content.
    • Assess whether the decision is still valid given the current code state.
    • Explain to the user what changed and why the record was flagged.
  3. Resolve each stale record by asking the user to choose:

    • Still valid: Use kauri_validate with verdict still_valid to refresh the timestamp.
    • Needs updating: Use kauri_record with supersedes to create a new decision replacing the old one.
    • No longer relevant: Use kauri_validate with verdict deprecate.

What "stale" means

A record is stale when:

  • Time-based: More than ttl_days have passed since last validation (default 90 days).
  • File-based: A file associated with the record has changed content since the last validation.

Stale does NOT mean wrong — it means "please review." The decision might still be perfectly valid.

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. 6d ago First seen · 36 lines · 36 tokens per session scan A 4ab5c89d223e

Subscribe to this mod's changes

check-staleness is a skill published in the GitHub repository mhashim6/kauri (5 stars, last pushed 4mo ago), licensed MIT. It adds 36 tokens to every session and 365 once invoked, about $0.0002 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.