agentmods.dev

writing-investigation-log

writing-investigation-log is a skill for Claude Code, Codex from syou6162/agent-skills. It costs 115 tokens per session (1,499 once invoked), scanned A, original, MIT.

A format for keeping an internal record of investigations, including sources, commands, queries, results, and unanswered questions. It stores this record separately from polished documents for users.

In plain words
What is it for?
Use it during code reading, web or GitHub checks, document research, command-line investigations, and database queries.
Why use it?
It keeps evidence and trial-and-error available for later agents without cluttering reports, proposals, pull requests, or other final writing.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

not rated 11repo 2mo ago A scan 115 tokens original MIT

Good fit Use it during code reading, web or GitHub checks, document research, command-line investigations, and database queries.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/syou6162/agent-skills/writing-investigation-log
View source ↗ syou6162/agent-skills
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.

Any agent
npx skills add syou6162/agent-skills --skill writing-investigation-log
Clone the repo
git clone --depth 1 https://github.com/syou6162/agent-skills

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for writing-investigation-log

README.md
[![agentmods](https://agentmods.dev/badge/skills/syou6162/agent-skills/writing-investigation-log/github.svg)](https://agentmods.dev/skills/syou6162/agent-skills/writing-investigation-log)
Your own site
<a href="https://agentmods.dev/skills/syou6162/agent-skills/writing-investigation-log"><img src="https://agentmods.dev/badge/skills/syou6162/agent-skills/writing-investigation-log/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.

agentmods 80×15 button for writing-investigation-log

Your own site · 80×15
<a href="https://agentmods.dev/skills/syou6162/agent-skills/writing-investigation-log"><img src="https://agentmods.dev/badge/skills/syou6162/agent-skills/writing-investigation-log.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 115 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,499 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00115 $0.01499
Opus 5 $0.00057 $0.00749
Sonnet 5 $0.00023 $0.00300
Haiku 4.5 $0.00012 $0.00150

Measured 12d ago against content hash ca8a8fc1b734, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

writing-investigation-log 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 12d 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.

skills/writing-investigation-log/SKILL.md · 110 lines

How it starts

The opening of the file, as written. The whole thing — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Writing Investigation Log

調査や裏取りの結果を、後続のエージェントが再利用できる内部ログとして残すスキルです。ユーザー向けの清書用Markdownや資料本文に、調査ログ、試行錯誤、コマンド履歴を混ぜないために使います。

  • 調査したら、ユーザーが明示しなくても .agent_work/investigations/ に記録すること
  • 調査ログはユーザー向け成果物ではなく、エージェント向けの内部作業ログとして扱うこと
  • 清書用ドキュメント、提案書、発表資料、PR本文、esaやNotionに貼る本文には調査ログを混ぜないこと
  • 結論だけを書かず、根拠URL、ローカルパス、実行コマンド、クエリ、結果、未確認事項を残すこと
  • 調査結果、確認したこと、結論、未確認事項は日本語で書くこと。URL、コマンド、クエリ、引用は原文のままでよい
  • 推測と確認済みを混ぜないこと。根拠が弱い内容は「未確認」または「推測」と明記すること
  • シークレット値やトークン値は記録しないこと。存在確認やマスク済みの状態だけを書くこと

保存先

調査ログは以下に保存します。

.agent_work/
  investigations/
    <topic>.md

<topic> は短い英数字とハイフンのファイル名にします。例:

  • conformed-fact-usage.md
  • periodic-snapshot-examples.md
  • planned-work-minutes-definition.md

既存の .claude_work は過去作業の参照対象にはなり得ますが、新規の標準保存先には使いません。

発動タイミング

以下を行うときは、このスキルを使って調査ログを作成または更新します。

  • GitHub PR、Issue、review comment、file permalink を調べる
  • esa、Notion、公式ドキュメント、社内ドキュメント、Webページを調べる
  • rg、git、gh、bq、SQL、MCP tool などで裏取りする
  • BigQueryなどにクエリを投げる
  • 資料、設計判断、レビュー、計画、PR説明の根拠になる情報を集める
  • 同じ調査を繰り返しそうなとき
  • コンテキスト圧縮やhandoffの有無に関係なく、調査をしたとき

短い事実確認でも、後から根拠として使うなら記録します。単なるファイル一覧確認や一時的な作業で、後続の判断材料にならないものは省略して構いません。

手順

  1. 既存ログを確認する

    • .agent_work/investigations/ に同じトピックのログがないか確認する
    • 既存ログがある場合は追記または更新し、重複ファイルを増やさない

  2. テンプレートを使う

    • 新規作成時は references/investigation-log-template.md の構成に従う
    • テンプレートの見出しは、不要なものを消さず「該当なし」と書く
    • 記入粒度に迷う場合は references/investigation-log-example.md を参照する

  3. 調査の問いを先に書く

    • 何を確認する調査なのか
    • どの成果物、判断、資料、レビューに使う根拠なのか

  4. 根拠を記録する

    • GitHub PRはフルURLで書く
    • GitHub fileは可能な限りbranchのblob URLではなく、行番号付きpermalinkや該当commitのURLを書く
    • esa、Notion、公式docs、WebページはURLと確認した内容を書く
    • ローカルファイルはパスと確認した行や内容を書く

  5. コマンドやクエリを記録する

    • 実行したコマンド、クエリ、MCP tool、主要な引数を残す
    • BigQueryなどのクエリは、クエリ本文と結果をセットで残す
    • 結果が長い場合は、重要な出力と保存先を書く

  6. 結論と限界を書く

    • 結果から直接言えることを書く
    • 結果からは言えないこと、未確認事項、追加調査が必要な点を書く

  7. ユーザーへ能動的に報告しない

    • 調査ログを残したことを、通常の完了報告に含めない
    • ユーザーから「この部分の根拠は?」などと明示的に聞かれたときだけ、調査ログを参照して根拠を答える

Read the full file on GitHub · 110 lines

Files

What ships with it

2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. 12d ago First seen · 110 lines · 115 tokens per session scan A ca8a8fc1b734

Subscribe to this mod's changes

writing-investigation-log is a skill published in the GitHub repository syou6162/agent-skills (11 stars, last pushed 2mo ago), licensed MIT. It adds 115 tokens to every session and 1,499 once invoked, about $0.0006 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-30.

Research
Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens