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 jolliai/jolli-claude-plugin --skill pushgit 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/skills/jolliai/jolli-claude-plugin/push)<a href="https://agentmods.dev/skills/jolliai/jolli-claude-plugin/push"><img src="https://agentmods.dev/badge/skills/jolliai/jolli-claude-plugin/push/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/jolliai/jolli-claude-plugin/push"><img src="https://agentmods.dev/badge/skills/jolliai/jolli-claude-plugin/push.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.00051 | $0.00457 |
| Opus 5.5 | $0.00020 | $0.00183 |
| Sonnet 5.5 | $0.00010 | $0.00091 |
| Haiku 4.5 | $0.00005 | $0.00046 |
Grade A, and why
push 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.
This is a copy
100% identical to push — 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 Push
Publish the current branch's commit memories to a Jolli Space as articles, so they are shareable with the team.
Requires being signed in to Jolli — pushing talks to the Jolli backend. If
the user is not signed in (check /jolli:status), tell them to run /jolli:login
first.
Step 1: Make sure memories are ready
Call the queue_status tool with { "wait": true } so freshly-committed
summaries are included. Do not proceed while generation is still in progress.
Step 2: Push
Call the push_memory tool (defaults to the current branch, range base..HEAD).
Handle the result by type:
-
type:"pushed"→ reportpushed(articles created/updated) andskipped, then show the returnedurls. -
type:"binding_required"→ the repo is not bound to a Space yet. The result carries the availablespacesanddefaultSpaceId. Show them and ask which Space to use, then either:- call
bind_spacewith{ "space": "<id|slug|name>" }, thenpush_memoryagain; or - call
push_memoryagain with{ "space": "<id|slug|name>" }(binds and pushes in one step).
If the user has no preference and
defaultSpaceIdis present, offer that Space. - call
-
type:"error"→ surfacemessage. If it mentions sign-in / auth, suggest/jolli:login; if it mentions an outdated client, relay the upgrade hint.
Notes
Push only what push_memory returns — never invent article content. If you need
the full Space list to help the user choose, call list_spaces.
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 First seen · 43 lines · 51 tokens per session scan A d22c9cff44e9
push is a skill published in the GitHub repository jolliai/jolli-claude-plugin (2 stars, last pushed 28d ago), licensed Apache-2.0. It adds 51 tokens to every session and 457 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to push, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
knowledge-ingest
Ingest documents, articles, conversations, or supplied text into Knowledge with retained originals, sourced claims, entity updates, timelines, and cross-links; also learn durable lessons from a set of conversations, transcripts, or past sessions (/learn), including the Learn from conversations and Learn from Memory…
mem0-oss-to-platform
Plan, then execute, a migration of a project from the mem0 open-source / self-hosted SDK (local Memory class) to the mem0 Platform / hosted SDK (MemoryClient). TRIGGER when: the developer wants to move, switch, or migrate mem0 off OSS/self-hosted to the hosted API, e.g. "migrate my mem0 setup to the platform", "switch…
forget
Remove a personal fact, preference, relationship detail, topic, or prior event from Muse's active memory and stop existing copies or automations from bringing it back. Use for explicit requests such as 'forget that', 'don't remember this about me', or 'remove that from your memory'. Do not use when 'forget it' merely…
Cortex
LifeOS memory, prior-session recall, and learning capture. USE WHEN capture this learning, document this learning, what did we learn recently, recent learnings, cortex, knowledge, knowledge base, search knowledge, what do we know about, archive, harvest, knowledge status, develop note, add to knowledge, add a people…
memory
Use when the user asks to remember, recall, forget, update, search, or inspect durable OpenSquilla memory, including profile facts in USER.md and long-term notes in MEMORY.md or memory//.md.
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…