Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add openshift-eng/ai-helpers/plugin install ciWrote 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/openshift-eng/ai-helpers/continue-session)<a href="https://agentmods.dev/commands/openshift-eng/ai-helpers/continue-session"><img src="https://agentmods.dev/badge/commands/openshift-eng/ai-helpers/continue-session/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/commands/openshift-eng/ai-helpers/continue-session"><img src="https://agentmods.dev/badge/commands/openshift-eng/ai-helpers/continue-session.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.00014 | $0.01448 |
| Opus 5.5 | $0.00006 | $0.00579 |
| Sonnet 5.5 | $0.00003 | $0.00290 |
| Haiku 4.5 | $0.00001 | $0.00145 |
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 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.
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.
Copies of this mod
1 near-identical copy found in the catalogue:
- continue-session — 88% identical, 28 lines differ
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 Claude session artifacts from a Prow CI job and allows you to continue one of those sessions locally. This is useful when Claude 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-results-publicbucket is publicly accessible (no auth needed)
- Check:
-
Python 3 (3.7+)
- Check:
which python3
- Check:
-
tar — for extracting archives
Implementation
Step 1: Search for session archives
Load the ci:prow-job-analysis skill and use its artifact search script (prow_job_artifact_search.py) 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 Claude 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-analysis skill's artifact search script 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.
- 1mo ago Changed 5a9844b96283
- 1mo ago First seen · 154 lines · 14 tokens per session scan A 575b1b78751e
continue-session is a command published in the GitHub repository openshift-eng/ai-helpers (119 stars, last pushed yesterday), licensed Apache-2.0. It adds 14 tokens to every session and 1,448 once invoked, about $0.0001 per session on Opus 5.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
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
speckit.bug.fix
Apply the remediation from a bug assessment and record what was changed.