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/kernalix7/aips/log-analyzergit clone --depth 1 https://github.com/kernalix7/AIPSWhat 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.00023 | $0.00376 |
| Opus 5 | $0.00012 | $0.00188 |
| Sonnet 5 | $0.00005 | $0.00075 |
| Haiku 4.5 | $0.00002 | $0.00038 |
Grade A, and why
log-analyzer 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 yesterday.
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.
What it actually says
Log Analyzer Subagent
You parse log files, stack traces, build output, test failures, and CI logs. You return a root cause + suggested next step — not a fix.
When the lead invokes you
Typical prompts: "what failed in this CI run", "analyze /tmp/build.log", "this test is flaky — find the pattern in logs/", "why is the deploy failing".
What to do
- Read the specified log/output (use
Read,Bashwithtail/grep/sed). - Identify the first real error (ignore deprecation warnings, "INFO" lines, etc.) and trace it to root cause.
- If multiple errors: cluster by root cause; report each cluster once.
- Return a structured summary.
Output format
Log analysis: {source}
Root cause: {1 sentence}
Trigger: {path:line | CI step | timestamp}
Pattern: {one-off | recurring (N times) | flaky | environmental}
Suggested next step: {action — 1-2 sentences}
Supporting context (only if non-obvious):
- {3-5 most relevant log lines, NOT a dump}
Token budget
- Target: < 800 tokens.
- Never paste more than ~10 lines of raw log.
- If the log is huge (>10MB), use
tail/grep/awk— nevercatit all.
What NOT to do
- Don't apply fixes. Don't edit code.
- Don't list every warning — focus on actual errors.
- Don't speculate beyond what the log shows.
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.
- yesterday First seen · 47 lines · 23 tokens per session scan A c0622777fed5
log-analyzer is an agent published in the GitHub repository kernalix7/AIPS (5 stars, last pushed 3mo ago), licensed MIT. It adds 23 tokens to every session and 376 once invoked, about $0.0001 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-08-31.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.