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/paulbreuler/limps/001_agent_semantic-toolsgit clone --depth 1 https://github.com/paulbreuler/limpsWrote 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/agents/paulbreuler/limps/001_agent_semantic-tools)<a href="https://agentmods.dev/agents/paulbreuler/limps/001_agent_semantic-tools"><img src="https://agentmods.dev/badge/agents/paulbreuler/limps/001_agent_semantic-tools.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.00739 |
| Opus 5 | $0.00000 | $0.00369 |
| Sonnet 5 | $0.00000 | $0.00148 |
| Haiku 4.5 | $0.00000 | $0.00074 |
Grade A, and why
001_agent_semantic-tools 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 — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent 1: Semantic Tools
Plan Location: plans/0041-limps-improvements/0041-limps-improvements-plan.md
Scope
Features: #3
Own: packages/limps/src/tools/semantic-search.ts, packages/limps/src/tools/find-similar.ts, packages/limps/src/tools/reindex-vectors.ts, packages/limps/src/tools/index.ts
Depend on: Agent 0 for semantic storage + embeddings
Block: None (Agent 2 is now independent)
Interfaces
Export
- semantic_search MCP tool
- find_similar MCP tool
- reindex_vectors MCP tool
Receive
- Semantic storage + embeddings from Agent 0
Features
#3: Semantic Search Tools
TL;DR: Add semantic MCP tools with plan/path scoping and observability logging.
Status: GAP
Test IDs: semantic-search-basic, find-similar-basic, reindex-vectors-force, semantic-observability
Files: packages/limps/src/tools/semantic-search.ts, packages/limps/src/tools/find-similar.ts, packages/limps/src/tools/reindex-vectors.ts
Observability Requirements: Log structured JSON for:
semantic.search: query_length, result_count, latency_ms, used_semanticsemantic.reindex: total_docs, indexed, skipped, errors, latency_mssemantic.error: operation, error_type, message
Model Change Detection:
- reindex_vectors should detect if config model differs from stored model_name
- If mismatch, warn user and require
force: trueto reindex all
TDD:
semantic-search-basic→ impl search with structured logging → refactorfind-similar-basic→ impl similarity lookup → refactorreindex-vectors-force→ impl rebuild with model detection → refactorsemantic-observability→ impl latency/usage logging → refactor
Done
- semantic_search registered with logging
- find_similar registered
- reindex_vectors with model mismatch detection
- Results include path + snippet + similarity + header context
- Structured observability logs
LIMPS Graph Links
Plan:
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 · 110 lines · 0 tokens per session scan A 9b1da5bb88ef
001_agent_semantic-tools is an agent published in the GitHub repository paulbreuler/limps (10 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 739 tokens. 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-31.
Other agents, from other repositories
domain
How the engineering skills should consume this repo's domain documentation when exploring the codebase.
triage-labels
The skills speak in terms of five canonical triage roles. This file maps those roles to the actual label strings used in this repo's issue tracker.
issue-tracker
Issues and PRDs for this repo live as GitHub issues. Use the gh CLI for all operations.
cpp-reviewer
Expert C++ code reviewer specializing in memory safety, modern C++ idioms, concurrency, and performance. Use for all C++ code changes. MUST BE USED for C++ projects.
dynamic-agents
Dynamic agents use functions instead of static values for instructions, model, and tools. These functions receive runtime context and return the appropriate configuration for each operation.
pixel-art-animation-reviewer
Independent reviewer of pixel-art ANIMATION quality (loop seamlessness, motion physics, multi-component motion, frame timing, period selection, particle determinism). One of four specialized review roles in the pixel-art-quality-board orchestrator. Use when the user asks to "check animation timing", "verify loop…