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 monkey1wizard/Golem-Agents-Legion --skill local-first-searchgit clone --depth 1 https://github.com/monkey1wizard/Golem-Agents-LegionWrote 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/monkey1wizard/golem-agents-legion/local-first-search)<a href="https://agentmods.dev/skills/monkey1wizard/golem-agents-legion/local-first-search"><img src="https://agentmods.dev/badge/skills/monkey1wizard/golem-agents-legion/local-first-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/monkey1wizard/golem-agents-legion/local-first-search"><img src="https://agentmods.dev/badge/skills/monkey1wizard/golem-agents-legion/local-first-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.00698 |
| Opus 5 | $0.00021 | $0.00349 |
| Sonnet 5 | $0.00008 | $0.00140 |
| Haiku 4.5 | $0.00004 | $0.00070 |
Grade A, and why
local-first-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 4d 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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Local-First Search Strategy
Core Philosophy
Context first, local first means: before answering conceptual questions, proposing solutions, or planning note-adjacent work, search repo-owned material first.
Avoid generic answers that ignore existing local context.
Search Order
Use this order unless the user explicitly asks for a different source:
-
codebase
- source files
- comments
- tests
- adjacent call sites
-
docs
docs/- plan documents
- workflow and convention docs
-
repo text artifacts
.dev/- configuration files
- notes stored in the repo itself
-
optional external notes
- only after the first three lanes are insufficient
- only when the
local-notesoptional-capability lane isready
Optional local-notes Lane
When repo-local retrieval is insufficient, consult the local-notes contract in
optional-capabilities.md, with operational setup in
docs/manual.md and docs/integrations.md.
Rules:
- treat external notes as optional additional evidence, not a Core prerequisite
- do not assume any specific note application, vault shape, diary ritual, or personal taxonomy
- do not assume semantic search exists
- if local-notes is not
ready, degrade silently to repo-local retrieval only
Execution Workflow
Phase 1 — Codebase Search
- search the owning code path first
- prefer exact text or symbol search for known identifiers
- read the minimum surrounding context needed to answer accurately
Phase 2 — Docs Search
- search durable docs and plan files relevant to the question
- use conventions and workflow docs when the question is about process or contract behavior
Phase 3 — Repo Artifact Search
- search
.dev/, repo-local notes, and tracked config surfaces when they carry task context - keep repo-owned state ahead of any private note system
Phase 4 — Optional External Notes
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.
- 4d ago First seen · 95 lines · 42 tokens per session scan A d6ed116a5941
local-first-search is a skill published in the GitHub repository monkey1wizard/Golem-Agents-Legion (15 stars, last pushed yesterday), licensed MIT. It adds 42 tokens to every session and 698 once invoked, about $0.0002 per session on Opus 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-04.
Other skills, from other repositories
media-ingest
Ingest video, audio, PDF, book, screenshot, and GitHub repo content into the brain. Multi-format handling with entity extraction and backlink propagation. Covers video-ingest, youtube-ingest, and book-ingest subtypes.
mem0-oss-to-platform
Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…
Cortex
Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…
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…
establishing-project-context
Use when the user asks to establish shared project language, or project work exposes a conflicting, renamed, or deprecated domain term that needs active semantic modeling. Routine small tasks stay on the fast path.