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 searchgit 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/search)<a href="https://agentmods.dev/skills/jolliai/jolli-claude-plugin/search"><img src="https://agentmods.dev/badge/skills/jolliai/jolli-claude-plugin/search/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/search"><img src="https://agentmods.dev/badge/skills/jolliai/jolli-claude-plugin/search.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.00042 | $0.00516 |
| Opus 5 | $0.00021 | $0.00258 |
| Sonnet 5 | $0.00008 | $0.00103 |
| Haiku 4.5 | $0.00004 | $0.00052 |
Grade A, and why
search 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 12d 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 search — 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 Search
Full-text (BM25) search over this repo's historical decisions and
implementations. Lightweight by design — returns title / snippet / slug / hash.
For depth on a branch, point the user to /jolli:recall.
Run the search
<user-arg> is the query.
Preferred — MCP tool. If the search tool from the jollimemory MCP
server is available, call it with { "query": "<user-arg>" }. It returns
{ hits }.
Fallback — bundled CLI. Run the Jolli CLI through its stable dispatch script. Pass the query via here-doc (never interpolate it into argv or a quoted string).
Generate a fresh random 16-character hex string (the "delimiter token") for
this invocation — e.g. 3f8a9b2c5d7e1f4a — and replace the two <DELIM>
occurrences below with it. If the query contains a line that is exactly
JOLLI_ARG_<delimiter token>_END, regenerate the token and re-check. A
per-invocation random delimiter is what makes a pre-computed prompt-injection
payload (a line that closes the here-doc early to smuggle shell) useless — do
NOT hardcode a fixed delimiter.
JOLLI_INVOKED_VIA=skill:search "$HOME/.jolli/jollimemory/run-cli" search --arg-stdin <<'JOLLI_ARG_<DELIM>_END'
<user-arg>
JOLLI_ARG_<DELIM>_END
Present the hits
List each hit's title, a one-line snippet, its branch, and the 8-char hash.
Offer to /jolli:recall a branch for the full context behind a hit.
No hits? An empty result can mean there are simply no matches — or that no
memories exist yet. If the user is not signed in to Jolli (see /jolli:status),
note that memories are only generated once signed in, and suggest /jolli:login
(no Anthropic API key needed). Otherwise suggest committing some work first.
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.
- 12d ago First seen · 47 lines · 42 tokens per session scan A 0c4ed24fba4c
search is a skill published in the GitHub repository jolliai/jolli-claude-plugin (2 stars, last pushed 14d ago), licensed Apache-2.0. It adds 42 tokens to every session and 516 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to search, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
gh-auth-isolation
Safely manage multiple GitHub identities (EMU + personal) in agent workflows.
comet-github
A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.
github-skill
Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.
changelog-composer
Generates structured changelogs and release notes from git history and PRs, classifying breaking changes, features, fixes, performance, docs. Triggers on: "generate changelog", "write release notes", "what changed since", "prepare release", "release notes for", "diff since tag".
re0-merge
Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…