log-analyzer

A plugin that extracts important information from lengthy command output.

In plain words
What is it for?
Use it when commands produce verbose logs and you need the key information without filling the agent’s context.
Why use it?
It reduces the amount of noisy terminal output that the main conversation needs to retain.

Plugin for Claude Code

Install

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.

Claude Code
/plugin marketplace add ncaq/konoka
agentmods
npx agentmods add plugins/ncaq/konoka/log-analyzer
Clone the repo
git clone --depth 1 https://github.com/ncaq/konoka

Made for: Claude Code.

Per session not measured What this adds to a session before it is invoked.
When invoked not measured Not applicable: nothing here is loaded into a session.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Security

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.

plugins/log-analyzer/.claude-plugin/plugin.json · 16 lines

What it actually says

{
  "$schema": "https://json.schemastore.org/claude-code-plugin-manifest.json",
  "name": "log-analyzer",
  "version": "1.0.2",
  "description": "Extract key information from verbose command output while keeping main conversation context lean.",
  "author": {
    "name": "ncaq",
    "email": "[email protected]",
    "url": "https://github.com/ncaq"
  },
  "homepage": "https://github.com/ncaq/konoka/tree/master/plugins/log-analyzer",
  "repository": "https://github.com/ncaq/konoka",
  "license": "Apache-2.0",
  "keywords": ["log", "analyzer", "output"]
}
Changes

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.

  1. yesterday First seen · 16 lines scan A bd18c7aaa28b

Subscribe to this mod's changes

log-analyzer is a plugin published in the GitHub repository ncaq/konoka (3 stars, last pushed 3d ago), licensed Apache-2.0. Its token cost is not measured: this kind of file is read by the harness, not the model. 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.