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 Snowflake-Labs/cocoplus --skill pull-searchgit clone --depth 1 https://github.com/Snowflake-Labs/cocoplusWrote 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/snowflake-labs/cocoplus/pull-search)<a href="https://agentmods.dev/skills/snowflake-labs/cocoplus/pull-search"><img src="https://agentmods.dev/badge/skills/snowflake-labs/cocoplus/pull-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/snowflake-labs/cocoplus/pull-search"><img src="https://agentmods.dev/badge/skills/snowflake-labs/cocoplus/pull-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.00038 | $0.00749 |
| Opus 5.5 | $0.00015 | $0.00300 |
| Sonnet 5.5 | $0.00008 | $0.00150 |
| Haiku 4.5 | $0.00004 | $0.00075 |
Grade A, and why
pull-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 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.
How it starts
The opening of the file, as written. The whole thing — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Objective
Search the CocoPull session archive for relevant past sessions.
Before proceeding, verify that .cocoplus/ exists. If not, output: "CocoPlus is not initialized. Run $pod init first." Then stop.
Handling $pull index rebuild
If the developer invoked $pull index rebuild:
- Invoke
cocopull/session-indexer --rebuild - Output: "CocoPull index rebuilt. session records indexed."
- Stop.
Handling $pull search "<query>"
Step 1 — Parse Flags
Extract:
<query>— required search string (in quotes)--since <date>— optional date filter (YYYY-MM-DD)--feature <name>— optional feature filter (e.g.,cocoharvest,safety-gate)
If no query provided, ask: "What do you want to search for? Example: $pull search \"schema migration\""
Step 2 — Read Index
Read .cocoplus/index/sessions.jsonl. If absent or empty, output:
"No session archive found. Sessions are indexed automatically at session end. If this is a new project, run $pull index rebuild after completing some sessions." Then stop.
Step 3 — Search
Case-insensitive substring match of query against:
summaryfieldfeatures_usedarray valuesarchetypefield
Apply --since filter (timestamp >= date) and --feature filter (features_used contains value) if provided.
Sort results by timestamp descending.
Step 4 — Output Results
CocoPull Search: "<query>"
Found <n> matching sessions
────────────────────────────────────────────────────────────
Session ID Date Archetype Duration Features
────────────────────────────────────────────────────────────
sess-7e8fa 2026-05-21 deep-build 94 min cocoharvest, cocoflow, secondeye
sess-6c8d1 2026-05-18 review-cycle 42 min sentinel, cocowisdom
Excerpt from sess-7e8fa:
"...decomposed schema migration into 3 parallel CocoHarvest stages, resolved
NULL handling concern in sentinel Dimension B..."
────────────────────────────────────────────────────────────
If no matches: "No sessions match ''. Try a broader search term or --since a wider date range."
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 · 87 lines · 38 tokens per session scan A 4676e08b8705
pull-search is a skill published in the GitHub repository Snowflake-Labs/cocoplus (724 stars, last pushed 16d ago), licensed MIT. It adds 38 tokens to every session and 749 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
knowledge_store_skill
Skill for working with local .knowledge.yaml files via KnowledgeStore. Use this when you need to recall, search, or manage directory-local memories and knowledge links stored in plain YAML alongside the user's project files. KnowledgeStore is directory-scoped. Each directory that contains a .knowledge.yaml file…
remember
Write-side memory: stores decisions, patterns, and outcomes in the MCP memory knowledge graph as entities with typed observations and relations. Use when something worth persisting across sessions was just learned or decided. To search or read existing memory, invoke memory; to debug retrieval internals…
memory
Read-side memory operations on the knowledge graph: search past decisions and patterns, load session context, view decision timelines, render Mermaid graph visualizations. Subcommands: search, load, history, viz, status. Use when finding or reviewing what memory already holds. For storing new knowledge instead, invoke…
llm-wiki
Use when building or maintaining a self-contained personal knowledge base (an LLM wiki) in plain markdown. Triggers: ingesting sources into a wiki, querying wiki knowledge, linting wiki health, auditing article claims against their sources, critiquing a wiki source's reasoning, superseding stale knowledge, 'add to…
authoring-claude-md
Creating and maintaining CLAUDE.md project memory files and .claude/rules/ rule files that provide non-obvious codebase context. Use when (1) creating a new CLAUDE.md for a project, (2) adding architectural patterns or design decisions to existing CLAUDE.md, (3) capturing project-specific conventions that aren't…
screenpipe-resume-work
Recover the last verified state of an interrupted task and identify the next useful action.