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/002_agent_query-toolsgit clone --depth 1 https://github.com/paulbreuler/limpsWhat 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.00664 |
| Opus 5 | $0.00000 | $0.00332 |
| Sonnet 5 | $0.00000 | $0.00133 |
| Haiku 4.5 | $0.00000 | $0.00066 |
Grade A, and why
002_agent_query-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 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.
How it starts
The opening of the file, as written. The whole thing — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent 2: Query Improvements
Plan Location: plans/0041-limps-improvements/0041-limps-improvements-plan.md
Scope
Features: #4
Own: packages/limps/src/tools/search-docs.ts, packages/limps/src/tools/query-docs.ts, packages/limps/src/tools/index.ts
Depend on: none (semantic integration is optional, FTS5 fallback is default)
Block: Agent 3 needs query tool documented
Interfaces
Export
- search_docs filters (path/plan/tags)
- query_docs MCP tool (works with or without semantic)
Receive
- semantic_search output (optional, when available)
Features
#4: Query Improvements + query_docs
TL;DR: Add scoped filters and query_docs wrapper. Works independently of semantic search.
Status: GAP
Test IDs: search-docs-path-filter, query-docs-fts-fallback, query-docs-semantic-blend
Files: packages/limps/src/tools/search-docs.ts, packages/limps/src/tools/query-docs.ts
Key Design Decision:
This agent has no dependencies because query_docs must work without semantic search. The semantic integration is additive — when semantic is available and preferSemantic: true, blend results. Otherwise, use FTS5 only.
Fallback Behavior:
- If semantic disabled → FTS5 only
- If semantic enabled but Ollama unavailable → FTS5 only with warning
- If semantic enabled and available → blend FTS5 + semantic based on
preferSemanticflag
TDD:
search-docs-path-filter→ impl path/plan/tag filters → refactorquery-docs-fts-fallback→ impl FTS5-only mode (no semantic deps) → refactorquery-docs-semantic-blend→ impl blended results when semantic available → refactor
Done
- Path/plan/tag filters on search_docs
- query_docs works without semantic (FTS5 only)
- query_docs blends semantic when available
- Clear fallback messaging in responses
LIMPS Graph Links
Plan:
Depends on: No dependencies found
Blocks:
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 · 97 lines · 0 tokens per session scan A 48f717cfc904
002_agent_query-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 664 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
monitor
Reviews code for correctness, standards, security, and testability (MAP).
evaluator
Evaluates solution quality and completeness (MAP).
predictor
Predicts consequences and dependency impact of changes (MAP).
task-decomposer
Breaks complex goals into atomic, testable subtasks (MAP).
actor
Generates production-ready implementation proposals (MAP).
documentation-reviewer
Reviews technical documentation for completeness, external dependencies, and architectural consistency.