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.
git clone --depth 1 https://github.com/jolliai/jolli-claude-pluginWrote 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/jolliai/jolli-claude-plugin/logout)<a href="https://agentmods.dev/commands/jolliai/jolli-claude-plugin/logout"><img src="https://agentmods.dev/badge/commands/jolliai/jolli-claude-plugin/logout/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/jolliai/jolli-claude-plugin/logout"><img src="https://agentmods.dev/badge/commands/jolliai/jolli-claude-plugin/logout.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.00027 | $0.00158 |
| Opus 5.5 | $0.00011 | $0.00063 |
| Sonnet 5.5 | $0.00005 | $0.00032 |
| Haiku 4.5 | $0.00003 | $0.00016 |
Grade A, and why
logout 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 27d 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
100% identical to logout — 0 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.
What it actually says
Jolli Logout
Clear the user's stored Jolli credentials by running the Jolli CLI through its stable dispatch script:
"$HOME/.jolli/jollimemory/run-cli" auth logout
Report the outcome
Show what the CLI prints. Then make the consequence clear:
- The Jolli auth token and Jolli API Key are removed from local config.
- Memory generation stops until the user signs in again with
/jolli:login, unless an Anthropic API key is configured — logout preserves it, and the CLI will say so when one is present.
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.
- 27d ago First seen · 22 lines · 27 tokens per session scan A 2e7a990e46ea
logout is a command published in the GitHub repository jolliai/jolli-claude-plugin (2 stars, last pushed 28d ago), licensed Apache-2.0. It adds 27 tokens to every session and 158 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to logout, differing in 0 lines, and is treated as a copy.
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.