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/wangke19/gemini-ai-helpers/continue-sessiongit clone --depth 1 https://github.com/wangke19/gemini-ai-helpersWrote 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/commands/wangke19/gemini-ai-helpers/continue-session)<a href="https://agentmods.dev/commands/wangke19/gemini-ai-helpers/continue-session"><img src="https://agentmods.dev/badge/commands/wangke19/gemini-ai-helpers/continue-session.svg" alt="Measured on agentmods" 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 | $0.00014 | $0.01424 |
| Opus 5 | $0.00007 | $0.00712 |
| Sonnet 5 | $0.00003 | $0.00285 |
| Haiku 4.5 | $0.00001 | $0.00142 |
Grade A, and why
continue-session 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 4d 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
88% identical to continue-session — 26 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 — 154 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Name
ci:continue-session
Synopsis
/ci:continue-session <prowjob-url>
Description
Downloads Gemini session artifacts from a Prow CI job and allows you to continue one of those sessions locally. This is useful when Gemini ran as part of a CI job and you want to pick up where it left off.
The command accepts:
- prowjob-url (required): URL to a Prow job run
Prerequisites
-
gcloud CLI — for accessing GCS artifacts
- Check:
which gcloud - The
test-platform-resultsbucket is publicly accessible (no auth needed)
- Check:
-
Python 3 (3.6+)
- Check:
which python3
- Check:
-
tar — for extracting archives
Implementation
Step 1: Search for session archives
Load the ci:prow-job-artifact-search skill and use its search operation to find files matching **/claude-session*.tar* in the job's artifacts.
Parse the JSON output. If no matches are found (count: 0), tell the user "No Gemini session archives found in this job's artifacts." and stop.
Step 2: Download archives to current directory
For each matched archive file, download it from GCS using gcloud storage cp:
gcloud storage cp --no-user-output-enabled <gcs_uri> ./
Step 3: Download payload artifacts
Search for payload artifacts using the ci:prow-job-artifact-search skill with the pattern **/payload*.yaml, **/payload*.json, and **/payload*.html.
For each matched file, download it to the current directory:
gcloud storage cp --no-user-output-enabled <gcs_uri> ./
These are supplementary artifacts — if none are found, continue without error.
Step 4: Extract archives
For each downloaded archive in the current directory:
# tar auto-detects compression format (.tar, .tar.gz, .tar.zst, .tar.bz2, etc.)
tar xf <filename>
After extraction, the structure contains a projects/ directory. Each session consists of two parts:
- A JSONL file at
projects/<project-path>/<session-uuid>.jsonl(the main conversation log) - A directory at
projects/<project-path>/<session-uuid>/(containing subagent data and other session state)
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.
- 4d ago First seen · 154 lines · 14 tokens per session scan A 03345dbdc423
continue-session is a command published in the GitHub repository wangke19/gemini-ai-helpers (2 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 14 tokens to every session and 1,424 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 88% identical to continue-session, differing in 26 lines, and is treated as a copy.
Other commands, from other repositories
spec-design
Create comprehensive technical design for a specification.
release-prod
Guide you through promoting stage → production.
claude-request
Send a prompt to Claude Code via the LLM gateway with session tracking.
modernize-extract-rules
Mine business logic from legacy code into testable, human-readable rule specifications.
mem-search
Full-text search in the memory vault (archives, contexts, histories, index).
a
Quick alias for /analyze.