check-gitignore

A command that checks whether Plan Cascade’s temporary planning files are excluded from Git, the version-control system used to track code changes.

In plain words
What is it for?
Use it to inspect and update a project’s .gitignore file for Plan Cascade files.
Why use it?
It reduces the chance of committing generated plans, state files, or worktree folders to the project history.

Command

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 commands/taoidle/plan-cascade/check-gitignore
Clone the repo
git clone --depth 1 https://github.com/Taoidle/plan-cascade
Per session 25 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 856 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 $0.00025 $0.00856
Opus 5 $0.00013 $0.00428
Sonnet 5 $0.00005 $0.00171
Haiku 4.5 $0.00003 $0.00086

Measured 2d ago against content hash 5b9909240b17, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

check-gitignore 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 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.

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.

commands/check-gitignore.md · 145 lines

How it starts

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

Plan Cascade - Check and Update .gitignore

This command checks if your project's .gitignore is configured to exclude Plan Cascade temporary files, and updates it if needed.

Why This Matters

Plan Cascade creates various temporary files during planning and execution:

  • prd.json, mega-plan.json - Planning documents
  • .worktree/ - Git worktree directories
  • .plan-cascade-link.json - Project link file
  • State files (.agent-status.json, .iteration-state.json, etc.)

These files should NOT be committed to version control because:

  1. They are regenerated each session
  2. They may contain environment-specific paths
  3. They can cause merge conflicts
  4. They clutter the repository history

Step 1: Check Current Status

First, check the current state of .gitignore:

uv run python -c "
from plan_cascade.utils.gitignore import GitignoreManager
from pathlib import Path

manager = GitignoreManager(Path.cwd())
result = manager.check()

print('=== .gitignore Status ===')
print()
print(f'File exists: {result.gitignore_exists}')
print(f'Has Plan Cascade section: {result.has_plan_cascade_section}')
print(f'Needs update: {result.needs_update}')
print()

if result.missing_entries:
    print('Missing entries:')
    for entry in result.missing_entries:
        print(f'  - {entry}')
else:
    print('All Plan Cascade entries are present.')
"

Step 2: Update if Needed

If the check shows missing entries, update .gitignore:

uv run python -c "
from plan_cascade.utils.gitignore import GitignoreManager
from pathlib import Path

manager = GitignoreManager(Path.cwd())
result = manager.update()

if result.success:
    if result.action == 'created':
        print('Created .gitignore with Plan Cascade entries')
    elif result.action == 'updated':
        print(f'Updated .gitignore: added {len(result.entries_added)} entries')
    else:
        print('No update needed - all entries already present')
else:
    print(f'Error: {result.message}')
"

Step 3: Show Summary

Read the full file on GitHub · 145 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. 2d ago First seen · 145 lines · 25 tokens per session scan A 5b9909240b17

Subscribe to this mod's changes

check-gitignore is a command published in the GitHub repository Taoidle/plan-cascade (131 stars, last pushed 5mo ago), licensed MIT. It adds 25 tokens to every session and 856 once invoked, about $0.0001 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-30.