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 skills/ncaq/konoka/log-analyzernpx skills add ncaq/konoka --skill log-analyzergit clone --depth 1 https://github.com/ncaq/konokaWrote 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/skills/ncaq/konoka/log-analyzer)<a href="https://agentmods.dev/skills/ncaq/konoka/log-analyzer"><img src="https://agentmods.dev/badge/skills/ncaq/konoka/log-analyzer.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.00023 | $0.00460 |
| Opus 5 | $0.00012 | $0.00230 |
| Sonnet 5 | $0.00005 | $0.00092 |
| Haiku 4.5 | $0.00002 | $0.00046 |
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 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.
What it actually says
冗長なコマンド出力やログファイルから重要な情報を抽出することに特化したログ解析スキルです。
解析対象
$ARGUMENTS
作業ディレクトリ
!create-workdir
上記のパスをログ保存先として使用する。
実行プロセス
入力の取得
以下のいずれかの方法でログを取得する:
- コマンドを実行して出力をキャプチャする:
foo 2>&1 | tee 作業ディレクトリ/[ファイル名] - 既存のログファイルを読み込む
出力全体の解析
- ログファイル全体を読む
- 出力のどの部分もスキップしない
- エラー、警告、失敗、その他の重要な項目を特定する
発見事項の報告
以下の構造でレポートを提供する:
- ログファイルの場所: 保存したログファイルへのパス
- 全体の結果: 全体的な成功/失敗のステータス
- 重要な発見事項: 重大度別に整理:
- 🔴 エラー: 対処が必要な致命的な問題
- 🟡 警告: 確認すべき潜在的な問題
- 🔵 情報: 関連する可能性のある注目すべき情報
出力フォーマットのガイドライン
- 問題を報告する際は関連するログ行を直接引用する
- 利用可能な場合は行番号やタイムスタンプを含める
- 関連する問題をグループ化する
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 · 55 lines · 23 tokens per session scan A 44ae929d92fd
log-analyzer is a skill published in the GitHub repository ncaq/konoka (3 stars, last pushed yesterday), licensed Apache-2.0. It adds 23 tokens to every session and 460 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 skills, from other repositories
cloudflare-email-routing
Cloudflare Email Routing for receiving/sending emails via Workers. Use for email workers, forwarding, allowlists, or encountering Email Trigger errors, worker call failures, SPF issues.
bun-sqlite
Use for bun:sqlite, SQLite operations, prepared statements, transactions, and queries.
bun-http-server
Use when building HTTP servers with Bun.serve, handling requests/responses, implementing routing, creating REST APIs, or configuring fetch handlers.
api-testing
HTTP API testing for TypeScript (Supertest) and Python (httpx, pytest). Test REST APIs, GraphQL, request/response validation, authentication, and error handling.
bun-jest-migration
Use when migrating from Jest to Bun's test runner, import compatibility, mocks, and config.
cloudflare-workers-migration
Migrate to Cloudflare Workers from AWS Lambda, Vercel, Express, and Node.js. Use when porting existing applications to the edge, adapting serverless functions, or resolving Node.js API compatibility issues.