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 skills/code-yeongyu/lazycodex/coding-agent-sessionsnpx skills add code-yeongyu/lazycodex --skill coding-agent-sessionsgit clone --depth 1 https://github.com/code-yeongyu/lazycodexWhat 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.00247 | $0.02816 |
| Opus 5 | $0.00123 | $0.01408 |
| Sonnet 5 | $0.00049 | $0.00563 |
| Haiku 4.5 | $0.00025 | $0.00282 |
Grade A, and why
coding-agent-sessions 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 — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Coding Agent Sessions
Find local coding-agent sessions across agent products before answering from memory. Prefer the bundled finder for broad cross-platform search, then read the selected session or raw file when you need exact evidence.
PHASE 0 - PLATFORM ROUTER
-
IF the user names a platform, load its reference first.
Platform Read Codex / OpenAI Codex CLI references/codex.mdClaude Code / Claude Desktop histories references/claude.mdSenpi / pi coding-agent logs references/senpi.mdoh-my-pi ( omp,~/.omp) and gajae-code (gjc,~/.gjc) logsreferences/senpi.mdOpenCode / oh-my-openagent (formerly oh-my-opencode) storage references/opencode.mdOpenClaw, Droid, Amp, Gemini, Kimi, Qwen, Codebuff, Roo/Kilo/Cline, Kodu, Cursor CLI, Aider, Kiro, Goose, Hermes, Crush, Zed, Aside references/all-platforms.mdUnknown / "any session" / cross-agent search references/all-platforms.md -
Run the broad finder first unless the user gave an exact file path. For fuzzy recall, expand the query first.
When the user remembers a task vaguely ("that OpenCode bug", "the dashboard PR", "when did we fix X"), derive 3-6 short query lanes before searching: product/tool aliases, repo/package names, exact error text, issue/PR/session IDs, English/Korean phrasing, and likely verbs such as fix, review, plan, deploy, or merge. Run the lanes together with repeated --query so match_reasons shows which wording found the hit.
python3 scripts/find-agent-sessions.py list --limit 20
python3 scripts/find-agent-sessions.py find "commit" --from 7d --platform senpi --platform opencode
python3 scripts/find-agent-sessions.py find "proxy" --platform openclaw --platform droid --platform amp
python3 scripts/find-agent-sessions.py find "refactor" --platform oh-my-pi --platform gajae-code
python3 scripts/find-agent-sessions.py find --query "deploy" --query "token usage" --workers 64
python3 scripts/find-agent-sessions.py find --query "opencode bug" --query "fix opencode" --query "OpenCode parent session" --include-subagents --workers 64
python3 scripts/find-agent-sessions.py read <session-id>
What ships with it
23 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- agents/openai.yaml 232 B
- references/all-platforms.md 5.8 KB
- references/claude.md 2.3 KB
- references/codex.md 1.8 KB
- references/opencode.md 2.5 KB
- references/senpi.md 1.7 KB
- scripts/agent_sessions/__init__.py 35 B runs code
- scripts/agent_sessions/aside_scanner.py 4.8 KB runs code
- scripts/agent_sessions/claude.py 2.4 KB runs code
- scripts/agent_sessions/cli.py 11 KB runs code
- scripts/agent_sessions/codex.py 3.8 KB runs code
- scripts/agent_sessions/file_scanners.py 12 KB runs code
- scripts/agent_sessions/jsonio.py 1.3 KB runs code
- scripts/agent_sessions/kiro_scanner.py 3.1 KB runs code
- scripts/agent_sessions/opencode.py 9.8 KB runs code
- scripts/agent_sessions/pi_family.py 1.8 KB runs code
- scripts/agent_sessions/scanners.py 3.2 KB runs code
- scripts/agent_sessions/sqlite_optional_scanners.py 7.5 KB runs code
- scripts/agent_sessions/sqlite_scanners.py 5.9 KB runs code
- scripts/agent_sessions/timeparse.py 1.9 KB runs code
- scripts/agent_sessions/transcript.py 5.5 KB runs code
- scripts/agent_sessions/types.py 1.5 KB runs code
- scripts/find-agent-sessions.py 514 B runs code
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 · 133 lines · 247 tokens per session scan A c60bc47a3108
coding-agent-sessions is a skill published in the GitHub repository code-yeongyu/lazycodex (3,350 stars, last pushed 23d ago), licensed MIT. It adds 247 tokens to every session and 2,816 once invoked, about $0.0012 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…