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/lovelaceloom/grok-plugin-cc/sessionsgit clone --depth 1 https://github.com/LovelaceLoom/grok-plugin-ccWrote 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/lovelaceloom/grok-plugin-cc/sessions)<a href="https://agentmods.dev/commands/lovelaceloom/grok-plugin-cc/sessions"><img src="https://agentmods.dev/badge/commands/lovelaceloom/grok-plugin-cc/sessions.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.00017 | $0.00370 |
| Opus 5 | $0.00009 | $0.00185 |
| Sonnet 5 | $0.00003 | $0.00074 |
| Haiku 4.5 | $0.00002 | $0.00037 |
Grade A, and why
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 5d 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.
What it actually says
Wrap grok sessions. The plugin tracks its OWN job ids (/grok:status,
/grok:result) — those are wrappers around invocations the plugin launched.
This command surfaces Grok's native sessions (~/.grok/sessions/...),
which include everything Grok has run in this workspace (including outside
the plugin).
Subcommands match the underlying CLI:
/grok:sessionsor/grok:sessions list— list recent Grok sessions/grok:sessions search <query>— search session contents. If the query starts with-or--(e.g. searching for previous--timeoutmentions), use the POSIX--terminator to escape it:/grok:sessions search -- --timeout. Everything after--is treated as a literal search term and forwarded to grok as a positional argv after a re-emitted--./grok:sessions restore <id>— restore a prior session for resume
Pair with --resume <id> on /grok:ask, /grok:research, /grok:rescue,
etc. to continue an existing session.
Raw user input:
$ARGUMENTS
Run:
node "${CLAUDE_PLUGIN_ROOT}/scripts/companion.mjs" sessions "$ARGUMENTS"
Output rules:
- Return the companion's stdout verbatim.
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.
- 5d ago First seen · 39 lines · 17 tokens per session scan A 5462f40255c0
sessions is a command published in the GitHub repository LovelaceLoom/grok-plugin-cc (5 stars, last pushed 27d ago), licensed Apache-2.0. It adds 17 tokens to every session and 370 once invoked, about $0.0001 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-31.
Other commands, from other repositories
self-improve
Bootstrap and operate a self-improving agent workspace. Scaffolds .learnings/ and memory/ directories, captures errors and learnings during a session, detects recurring patterns, and promotes stable entries to project memory (CLAUDE.md, AGENTS.md, or references/). Also implements the Proactive Agent pillars — WAL…
checkpoint
Write a new link in the continuum chain summarizing decisions/changes since the last link.
dream
Roll up the last N links into a single phase-digest link; originals move to archived/ (never deleted).
promote
Move .memory/ artifacts to permanent knowledge locations.
checkpoint
Create or update .memory/ with current conversation state.
recall
Search past links in the continuum chain by tag/keyword and return matched summaries.