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 skills add wan-huiyan/agent-traffic-control --skill claude-code-projects-jsonl-worktree-fanoutgit clone --depth 1 https://github.com/wan-huiyan/agent-traffic-controlWrote 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.
[](https://agentmods.dev/skills/wan-huiyan/agent-traffic-control/claude-code-projects-jsonl-worktree-fanout)<a href="https://agentmods.dev/skills/wan-huiyan/agent-traffic-control/claude-code-projects-jsonl-worktree-fanout"><img src="https://agentmods.dev/badge/skills/wan-huiyan/agent-traffic-control/claude-code-projects-jsonl-worktree-fanout/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.
<a href="https://agentmods.dev/skills/wan-huiyan/agent-traffic-control/claude-code-projects-jsonl-worktree-fanout"><img src="https://agentmods.dev/badge/skills/wan-huiyan/agent-traffic-control/claude-code-projects-jsonl-worktree-fanout.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00048 | $0.02007 |
| Opus 5.5 | $0.00019 | $0.00803 |
| Sonnet 5.5 | $0.00010 | $0.00401 |
| Haiku 4.5 | $0.00005 | $0.00201 |
Grade B, and why
claude-code-projects-jsonl-worktree-fanout scanned grade B with 1 finding 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 1mo 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
The user asks: *"find that session ~2 weeks ago where we discussed X"*. You grep `~/.claude/projects/-Users-<user>-Documents-foo-project/*.jsonl` for keywords, get partial or zero hits, and report "couldn't find it" — bu How it starts
The opening of the file, as written. The whole thing — 162 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Claude Code projects/ JSONL transcripts fan out across worktrees
Problem
The user asks: "find that session ~2 weeks ago where we discussed X". You grep ~/.claude/projects/-Users-<user>-Documents-foo-project/*.jsonl for keywords, get partial or zero hits, and report "couldn't find it" — but the session does exist, just under a different directory because it ran inside a git worktree.
Claude Code maps each git worktree to its own project directory under ~/.claude/projects/. The canonical project at /Users/<user>/Documents/foo-project/ becomes:
~/.claude/projects/-Users-<user>-Documents-foo-project/
But a worktree created via git worktree add .claude/worktrees/<wt-name> becomes a separate sibling:
~/.claude/projects/-Users-<user>-Documents-foo-project--claude-worktrees-<wt-name>/
Each worktree dir holds its own JSONL transcripts for sessions started from that working directory. A project that's seen heavy worktree use (typical for superpowers:using-git-worktrees workflow) can have dozens of sibling dirs.
Context / Trigger Conditions
- User asks about a prior session, conversation, or work in a project
- Project uses
superpowers:using-git-worktreesor has.claude/worktrees/populated - Your initial grep of
~/.claude/projects/<project-name>/*.jsonlreturned fewer hits than expected, or none - You want to enumerate every session that ever ran against the project (e.g. for a knowledge audit)
- Symptom:
~/.claude/projects/contains a<project-name>dir AND multiple<project-name>--claude-worktrees-<wt>siblings
Solution
Quick lookup (one-liner)
Glob the wildcard suffix to cover canonical + all worktrees:
ls ~/.claude/projects/ | grep -iE "<project-keyword>" | wc -l # confirm fan-out
Then search across all of them at once:
find ~/.claude/projects/ -name "*.jsonl" -newermt "<earliest-date>" 2>/dev/null \
| grep -iE "<project-keyword>" \
| grep -v subagents \
| while read f; do
c=$(grep -ic -E "<your-search-keywords>" "$f" 2>/dev/null)
[ "$c" -gt 0 ] && echo "$c | $(stat -f "%Sm" -t "%Y-%m-%d %H:%M" "$f") | $f"
done | sort -rn | head -10
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.
- 1mo ago First seen · 162 lines · 48 tokens per session scan B 7adacfa031bf
claude-code-projects-jsonl-worktree-fanout is a skill published in the GitHub repository wan-huiyan/agent-traffic-control (3 stars, last pushed 1mo ago), licensed MIT. It adds 48 tokens to every session and 2,007 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
llm-wiki
Build and maintain an LLM-curated knowledge base from papers, articles, transcripts, notes and project findings. Ingest sources into linked Markdown, answer questions with citations, lint or upgrade a wiki, and preserve useful synthesis across sessions and agents. Also capture verified task experience, consolidate…
resume
Write down where this stretch of work stopped, so the next session continues instead of restarting. Use at the end of a working session, or when handing the repository to someone else.
wrap
Use when ending a session, wrapping up, or saying "session end", "wrap up", "update files". Reviews the conversation and updates brain files, workflows, registry, and decisions log based on what happened.
context-driven-development
Use this skill when working with Conductor's context-driven development methodology, managing project context artifacts, or understanding the relationship between product.md, tech-stack.md, and workflow.md files.
lembas
Use between workflow phases or when context feels bloated. Writes a structured checkpoint capturing task, findings, files, state, and next steps, then continues from that summary instead of the full history. Invoke standalone or automatically between quest phases.
knowledge-manager
Loads relevant patterns and known errors before track planning. Searches conductor/knowledge/ for solutions we've used before and errors we've encountered. Injects findings into the planner prompt to prevent reinventing solutions and repeating mistakes. Triggered automatically by orchestrator before PLAN step.