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 agentmods add agents/neturely/okffs/semble-searchgit clone --depth 1 https://github.com/neturely/okffsWhat 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 | $0.00047 | $0.00433 |
| Opus 5 | $0.00023 | $0.00217 |
| Sonnet 5 | $0.00009 | $0.00087 |
| Haiku 4.5 | $0.00005 | $0.00043 |
Grade A, and why
semble-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 2d 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
78% identical to semble-search — 16 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
Use semble search to find code by describing what it does or naming a symbol/identifier, instead of grep:
semble search "authentication flow" ./my-project
semble search "save_pretrained" ./my-project
semble search "save model to disk" ./my-project --top-k 10
Results are cached automatically on first run and invalidated when files change.
Use --content docs to search documentation and prose, --content config for config files (yaml, toml, etc.), or --content all to search code, docs, and config:
semble search "deployment guide" ./my-project --content docs
semble search "database host port" ./my-project --content config
semble search "authentication" ./my-project --content all
Use semble find-related to discover code similar to a known location (pass file_path and line from a prior search result):
semble find-related src/auth.py 42 ./my-project
path defaults to the current directory when omitted; git URLs are accepted.
If semble is not on $PATH, use uvx --from "semble[mcp]" semble in its place.
Workflow
- Start with
semble searchto find relevant chunks. The index is built and cached automatically. - Use
--content docsfor documentation,--content configfor config files, or--content allfor everything. - Inspect full files only when the returned chunk does not give enough context.
- Optionally use
semble find-relatedwith a promising result'sfile_pathandlineto discover related implementations. - Use grep only when you need exhaustive literal matches or quick confirmation of an exact string.
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.
- 2d ago First seen · 42 lines · 47 tokens per session scan A df7e5107f5f2
semble-search is an agent published in the GitHub repository neturely/okffs (2 stars, last pushed 12d ago), licensed MIT. It adds 47 tokens to every session and 433 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 78% identical to semble-search, differing in 16 lines, and is treated as a copy.
Other agents, from other repositories
cross-file-impact
Analyzes how changes in one file affect consumers across the codebase, catching cross-file breakage from signature changes, interface violations, and broken references.
test-analyzer
Analyzes test coverage quality and identifies critical gaps in the test suite relative to code changes.
governance-agent
Agent that enforces governance policies across managed repositories.
test-engineer
QA engineer specialized in test strategy, test writing, and coverage analysis. Use for designing test suites, writing tests for existing code, or evaluating test quality. Familiar with GitScape's pytest + FastAPI TestClient setup.
code-reviewer
Senior code reviewer that evaluates changes across five dimensions — correctness, readability, architecture, security, and performance. Use for thorough code review before merge.
AGENTS
Subagent contracts. Each .md is a system prompt with enforced YAML frontmatter.