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.
git clone --depth 1 https://github.com/WYRE-AI/msp-claude-pluginsWrote 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/commands/wyre-ai/msp-claude-plugins/search-logs)<a href="https://agentmods.dev/commands/wyre-ai/msp-claude-plugins/search-logs"><img src="https://agentmods.dev/badge/commands/wyre-ai/msp-claude-plugins/search-logs/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/commands/wyre-ai/msp-claude-plugins/search-logs"><img src="https://agentmods.dev/badge/commands/wyre-ai/msp-claude-plugins/search-logs.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.00007 | $0.00666 |
| Opus 5 | $0.00003 | $0.00333 |
| Sonnet 5 | $0.00001 | $0.00133 |
| Haiku 4.5 | $0.00001 | $0.00067 |
Grade A, and why
search-logs 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 5d 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 — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Better Stack Log Search
Search and query logs via Better Stack Logtail using structured queries. Use for incident investigation, error pattern analysis, and proactive monitoring.
Prerequisites
- Better Stack MCP server connected with valid API token (Global API Token required for Telemetry)
- MCP tools
execute_queryandlist_sourcesavailable
Steps
-
Identify log sources
If a
sourcefilter is provided, resolve the source name to a source ID. Otherwise, search across all sources. Calllist_sourcesto see available sources if needed. -
Build and execute query
Call
execute_querywith the ClickHouse SQL query based on the providedquerystring. Applyfromandtotime range filters. Limit results to the specifiedlimit. -
Format results
For each log entry, extract: timestamp, level, message, service, host, and any relevant custom fields.
-
Identify patterns
Group results by error type or service. Highlight recurring errors, error rate spikes, or unusual patterns.
-
Provide investigation context
Suggest related queries for deeper investigation. Cross-reference with monitor incidents using
/incident-triage.
Parameters
| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
| query | string | Yes | Search query (field:value, text search, boolean operators) | |
| source | string | No | all | Log source name or ID |
| from | string | No | last 1 hour | Start time (ISO 8601) |
| to | string | No | now | End time (ISO 8601) |
| limit | integer | No | 100 | Maximum number of log entries to return |
Examples
Search for Errors
/search-logs --query "level:error"
Search Specific Service
/search-logs --query "level:error AND service:api-gateway" --from "2026-03-27T08:00:00Z"
Search for Specific Error Message
/search-logs --query "\"connection refused\""
Search from a Specific Source
/search-logs --query "level:fatal" --source "Production API"
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.
- 5d ago First seen · 86 lines · 7 tokens per session scan A 2a05ab061611
search-logs is a command published in the GitHub repository WYRE-AI/msp-claude-plugins (45 stars, last pushed 6d ago), licensed Apache-2.0. It adds 7 tokens to every session and 666 once invoked, about $0.0000 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 commands, from other repositories
resolve-codeql
Analyze and resolve CodeQL alerts systematically.
site-audit
Crawl a website and audit for broken links, spelling errors, console errors, and visual issues.
check
Run static analysis on the Java project — detects configured tools (Checkstyle, SpotBugs, PMD) and reports findings.
analyze-issue
A command that runs a systematic problem investigation and searches for the root cause through a five-agent analysis process.
quick-analyze
A command for quickly analysing a problem when you already have a clear error message.
checklist
Generate a custom checklist for the current feature based on user requirements.