A command for finding and managing temporary documents created during software work, such as checklists, investigation notes, and reports. It helps decide whether these files should be kept, updated, or removed before they clutter the repository.

Use it to audit a project for temporary documentation or apply the project’s cleanup process to specified notes.

It reduces unwanted documentation in version control and prevents later agents from treating old notes as current tasks. The command can scan for temporary files and show a short summary.

temp-doc — Command for Claude Code by Jamie-BitFlight/claude

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.

Clone the repo

git clone --depth 1 https://github.com/Jamie-BitFlight/claude_skills

Made for: Claude Code.

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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/jamie-bitflight/claude_skills/temp-doc/github.svg)](https://agentmods.dev/commands/jamie-bitflight/claude_skills/temp-doc)

Your own site

<a href="https://agentmods.dev/commands/jamie-bitflight/claude_skills/temp-doc"><img src="https://agentmods.dev/badge/commands/jamie-bitflight/claude_skills/temp-doc/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/jamie-bitflight/claude_skills/temp-doc"><img src="https://agentmods.dev/badge/commands/jamie-bitflight/claude_skills/temp-doc.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 23 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 4,016 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.

Model	Per session	Once invoked
Fable 5.1	$0.00023	$0.04016
Opus 5.5	$0.00009	$0.01606
Sonnet 5.5	$0.00005	$0.00803
Haiku 4.5	$0.00002	$0.00402

Measured 2mo ago against content hash 9bf282b203b6, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

temp-doc 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 2mo 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.

.claude/commands/temp-doc.md · 579 lines

How it starts

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

Temporary Documentation Lifecycle Command

Purpose

Manage temporary documentation created during task execution - prevent git pollution from AI-generated checklists, reports, and investigation notes.

Script Location

.claude/utilities/find-temp-documentation.py - Standalone Python script with Typer CLI.

Primary User: Claude Code orchestrator (not human users) Secondary User: Sub-agents (to update document status)

Critical Rules

PROBLEM: AI agents create temporary docs (bug reports, checklists, investigation notes) that:

Pollute git history
Confuse future AI sessions (treats fixed bugs as active)
Create maintenance burden
Are never read by humans or AI after task completion

SOLUTION: Enforce strict lifecycle for ALL temporary documentation.

Your Task

Apply temporary documentation lifecycle policy to: $ARGUMENTS

If $ARGUMENTS is empty, audit current directory for temporary docs and recommend cleanup.

Script Usage

For Orchestrator (Claude Code Main Instance)

Context-Efficient Workflow:

# Step 1: Check summary (50-100 tokens)
.claude/utilities/find-temp-documentation.py scan --summary

# Step 2: Peek at frontmatter of specific doc (100-150 tokens)
.claude/utilities/find-temp-documentation.py show --index 0 --frontmatter

# Step 3: Read full content only if needed (use Read tool)
Read("path/from/frontmatter")

# Step 4: Before completing task, cleanup completed docs
.claude/utilities/find-temp-documentation.py cleanup --no-dry-run

Common Scenarios:

# User asks: "What bugs did you find?"
# → Find bug reports quickly
.claude/utilities/find-temp-documentation.py scan --summary
# See: bugs: 2
.claude/utilities/find-temp-documentation.py show --index 0 --frontmatter
# description: "Bug tracking for config.py. 3 bugs (1 critical)"

# Multiple parallel tasks - organize by task
.claude/utilities/find-temp-documentation.py scan --group-by task

# Check what needs cleanup
.claude/utilities/find-temp-documentation.py cleanup  # dry-run by default

# Actually cleanup (moves to .wastepaper/)
.claude/utilities/find-temp-documentation.py cleanup --no-dry-run

Read the full file on GitHub · 579 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.

2mo ago First seen · 579 lines · 23 tokens per session scan A 9bf282b203b6

Subscribe to this mod's changes

temp-doc is a command published in the GitHub repository Jamie-BitFlight/claude_skills (67 stars, last pushed 18d ago), licensed MIT. It adds 23 tokens to every session and 4,016 once invoked, about $0.0001 per session on Opus 5.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-30.

Writing and docs

temp-doc next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
temp-docJamie-BitFlight/claude_skills	Command	67	18d ago	MIT	A	23	Claude Code
checklistgithub/spec-kit	Command	148k	yesterday	MIT	A	13	Claude Code
clarifygithub/spec-kit	Command	148k	yesterday	MIT	A	27	Claude Code
specifygithub/spec-kit	Command	148k	yesterday	MIT	A	13	Claude Code
analyzegithub/spec-kit	Command	148k	yesterday	MIT	A	26	Claude Code
convergegithub/spec-kit	Command	148k	yesterday	MIT	A	35	Claude Code
implementgithub/spec-kit	Command	148k	yesterday	MIT	A	14	Claude Code