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.
npx agentmods add commands/taoidle/plan-cascade/check-gitignoregit clone --depth 1 https://github.com/Taoidle/plan-cascadeWhat 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 | $0.00025 | $0.00856 |
| Opus 5 | $0.00013 | $0.00428 |
| Sonnet 5 | $0.00005 | $0.00171 |
| Haiku 4.5 | $0.00003 | $0.00086 |
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.
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:
- They are regenerated each session
- They may contain environment-specific paths
- They can cause merge conflicts
- 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
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.
- 2d ago First seen · 145 lines · 25 tokens per session scan A 5b9909240b17
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.
Other commands, from other repositories
conv_release
Command "conv_release" from John-Wendell/Attention-MoA, covering chatbot arena conversations, all conversations and prompt distribution.
data_cleaning
Command "data_cleaning" from John-Wendell/Attention-MoA, covering data cleaning, requirements, steps, convert html to markdown and keep or remove specific languages.
pypi
Command "pypi" from John-Wendell/Attention-MoA, covering requirement and upload.
local_cluster
node-01.
webserver
Command "webserver" from John-Wendell/Attention-MoA, covering install, launch servers, check the launch time, increase the limit of max open files and gradio edit (3.35.2).
leaderboard
Command "leaderboard" from John-Wendell/Attention-MoA, covering get logs, clean battle data, run elo analysis, copy files to hf space and update files on webserver.