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 daeryundf2-prog/LAZYANTIGRAVITY --skill coding-agent-sessionsgit clone --depth 1 https://github.com/daeryundf2-prog/LAZYANTIGRAVITYWrote 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/daeryundf2-prog/lazyantigravity/coding-agent-sessions)<a href="https://agentmods.dev/skills/daeryundf2-prog/lazyantigravity/coding-agent-sessions"><img src="https://agentmods.dev/badge/skills/daeryundf2-prog/lazyantigravity/coding-agent-sessions/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/daeryundf2-prog/lazyantigravity/coding-agent-sessions"><img src="https://agentmods.dev/badge/skills/daeryundf2-prog/lazyantigravity/coding-agent-sessions.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.00063 | $0.02698 |
| Opus 5.5 | $0.00025 | $0.01079 |
| Sonnet 5.5 | $0.00013 | $0.00540 |
| Haiku 4.5 | $0.00006 | $0.00270 |
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 19d 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.
This is a copy
92% identical to coding-agent-sessions — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 134 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.mdOMO / Senpi / 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.md 3.9 KB
- references/all-platforms.md 5.9 KB
- references/claude.md 2.3 KB
- references/codex.md 1.8 KB
- references/opencode.md 2.5 KB
- references/senpi.md 1.8 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.
- 19d ago First seen · 134 lines · 63 tokens per session scan A 9b00f11c1aad
coding-agent-sessions is a skill published in the GitHub repository daeryundf2-prog/LAZYANTIGRAVITY (14 stars, last pushed 2d ago), licensed MIT. It adds 63 tokens to every session and 2,698 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 92% identical to coding-agent-sessions, differing in 2 lines, and is treated as a copy.
Other skills, from other repositories
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
generate-run-commands
Generate or modify run commands for the current session. Use when the user wants to set up or update run commands that appear in the session's Run button.
get-search-view-results
Get the current search results from the Search view in VS Code.
refit
Cross-session environment retrospective driven by OMC's own instrumentation — trace timelines, friction reports, logs, and plan notepads. Every finding lands on the surface that owns the fix (deterministic check, steering volume, tooling, or information access); nothing is written without user approval.
minimal-code-discipline
YAGNI-ladder coding discipline for writing changes — existence-first, reuse before writing, dependency ladder, shortest correct diff, with non-negotiables that must never be minimized away.
planned-task-runtime
Handles system follow-up turns: planned-task-follow-up (synthesize, replan, build-workflow, checkpoint), background-task-completed, running-tasks context, and create-tasks silence rules. Load whenever any of these tags appear or after calling create-tasks.