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 VioletCranberry/coco-search --skill cocosearch-debugginggit clone --depth 1 https://github.com/VioletCranberry/coco-searchWrote 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/violetcranberry/coco-search/cocosearch-debugging)<a href="https://agentmods.dev/skills/violetcranberry/coco-search/cocosearch-debugging"><img src="https://agentmods.dev/badge/skills/violetcranberry/coco-search/cocosearch-debugging/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/violetcranberry/coco-search/cocosearch-debugging"><img src="https://agentmods.dev/badge/skills/violetcranberry/coco-search/cocosearch-debugging.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 3 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Anti-Refusal · line 28 Skill instructs the agent to omit warnings, disclaimers, or ethical commentary. Stripping safety caveats hides risk from the user and is a common jailbreak preamble.Fix: Remove instructions that suppress warnings, disclaimers, or ethical commentary. Let the agent surface safety-relevant caveats to the user.
- medium Tool Misuse · line 233 Tool defaults are unsafe or overly permissive (e.g. disabled TLS verification, no authentication, world-writable permissions). Unsafe defaults widen the attack surface.Fix: Override unsafe defaults with secure settings (verify=True, auth required, restrictive permissions). Review and harden all tool configurations.
- medium Tool Misuse · line 237 Tool defaults are unsafe or overly permissive (e.g. disabled TLS verification, no authentication, world-writable permissions). Unsafe defaults widen the attack surface.Fix: Override unsafe defaults with secure settings (verify=True, auth required, restrictive permissions). Review and harden all tool configurations.
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.00037 | $0.02713 |
| Opus 5.5 | $0.00015 | $0.01085 |
| Sonnet 5.5 | $0.00007 | $0.00543 |
| Haiku 4.5 | $0.00004 | $0.00271 |
Grade A, and why
cocosearch-debugging 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 — 350 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Debugging with CocoSearch
Pre-flight Check
- Resolve index name (use the resolved name for all operations):
- Try
cocosearch.yamlforindexNamefield -- if found, use it - If no config file, call
list_indexes()and match the current project's directory name against available indexes. The MCP tools auto-derive index names from directory paths (e.g.,my-project/->my_project), so a match is likely if the repo was indexed without a config file. - If no match found, the project is genuinely not indexed -- offer to index it. Do NOT abandon CocoSearch tools just because
cocosearch.yamlis missing.
- Try
list_indexes()to confirm project is indexedindex_stats(index_name="<resolved-name>")to check freshness
- No index → offer to index before debugging
- Stale (>7 days) → warn: "Index is X days old -- results may not reflect recent changes. Want me to reindex first?"
-
Check dependency freshness — call
get_file_dependencieson any known file from the error context:get_file_dependencies(file="<file-from-error>", depth=1)- If response contains
warningswith typedeps_outdatedordeps_branch_drift: Warn: "Dependency data is outdated — call chain tracing may be incomplete. Want me to re-extract dependencies first?" - If response contains
warningswith typedeps_not_extracted: Note: "No dependency data found. I'll use search-based call tracing instead. Dependency data can improve tracing accuracy — want me to extract dependencies?" - If no warnings: Proceed normally (use dependency Fast Path when applicable).
- If response contains
-
Linked index health (if
cocosearch.yamlhaslinkedIndexes):- Check the
warningsarray fromindex_stats()for entries starting with "Linked index" - If stale/missing: warn user — "Linked index 'X' is stale/missing. Cross-project results may be incomplete. Want me to reindex?"
- Check the
Step 1: Understand the Symptom
Parse what the user is reporting. Different inputs require different extraction:
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 · 350 lines · 37 tokens per session scan A 13cd441116a2
cocosearch-debugging is a skill published in the GitHub repository VioletCranberry/coco-search (37 stars, last pushed 6d ago), licensed MIT. It adds 37 tokens to every session and 2,713 once invoked, about $0.0001 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-08-30.
Other skills, from other repositories
vera
Code search over the current repository. Your first search in a repository goes through Vera, not grep, rg, or file reads. Run vera overview in an unfamiliar repository, vera search " " for how or where something works, vera structural definitions or vera references when the question names a symbol, and vera grep…
tilth
Use the tilth CLI for code reading, outlining, search, callers, blast-radius deps, and structural diffs. Activate when the user asks to explore a repo, find a symbol, trace callers, read a file, view a diff, or analyze impact. Prefer tilth over grep/cat/find/ls — one invocation returns AST-aware outlines, definitions…
codebase-search
Task-specific semantic code and documentation retrieval. Use compact context for unfamiliar repository orientation, direct lookup for known definitions, graph tools for relationships, and grep for exhaustive literal matches.
gno
Search local documents, files, notes, and knowledge bases. Index directories, search with BM25/vector/hybrid, get AI answers with citations. Use when user wants to search files, find documents, query notes, look up information in local folders, index a directory, set up document search, build a knowledge base, needs…
codebase-search
Task-specific local codebase-understanding workflow for OpenCode, MCP, Pi, omp, and Codex. Use compact context for unfamiliar repository orientation, direct definition and graph tools for known targets.
rawq
Context retrieval engine. Semantic + lexical hybrid search over codebases. Returns ranked code chunks with file paths, line ranges, scope labels, and confidence scores.