cc-discipline: Skill for Claude Code

.claude/skills/investigate/SKILL.md

investigate is a skill for Claude Code from TechHU-GS/cc-discipline. It costs 41 tokens per session (1,768 once invoked), scanned A, original, MIT.

A multi-agent investigation workflow that assigns different parts of a question to parallel agents and combines their findings. It supports research from scratch, review of an existing proposal, and step-by-step simulation of a plan.

In plain words
What is it for?
Use it to research a topic, stress-test a document or design, or dry-run a plan so that problems can surface before implementation.
Why use it?
It reduces the chance that one investigation misses an important angle or hidden weakness. In review mode, it specifically challenges the proposal instead of merely summarizing it.

Skill for Claude Code

Written for Claude Code: installed under .claude/. Also seen: mentions subagents.

This is TechHU-GS/cc-discipline's own configuration. It tells Claude Code how to work on cc-discipline itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything cc-discipline configures →

Reuse

Borrowing it

Nothing to install: this file belongs to TechHU-GS/cc-discipline. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/TechHU-GS/cc-discipline/main/.claude/skills/investigate/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/TechHU-GS/cc-discipline

Made for: Claude Code.

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 investigate

README.md
[![agentmods](https://agentmods.dev/badge/skills/techhu-gs/cc-discipline/investigate/github.svg)](https://agentmods.dev/skills/techhu-gs/cc-discipline/investigate)
Your own site
<a href="https://agentmods.dev/skills/techhu-gs/cc-discipline/investigate"><img src="https://agentmods.dev/badge/skills/techhu-gs/cc-discipline/investigate/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 investigate

Your own site · 80×15
<a href="https://agentmods.dev/skills/techhu-gs/cc-discipline/investigate"><img src="https://agentmods.dev/badge/skills/techhu-gs/cc-discipline/investigate.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 41 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,768 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.00041 $0.01768
Opus 5 $0.00020 $0.00884
Sonnet 5 $0.00008 $0.00354
Haiku 4.5 $0.00004 $0.00177

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

Security

Grade A, and why

investigate 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 9d 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.

.claude/skills/investigate/SKILL.md · 193 lines

How it starts

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

Mode detection

Determine which mode based on user input:

  • Research mode — User gives a topic/question with no existing proposal. Goal: build comprehensive understanding before forming an opinion.
  • Review mode — User gives an existing document, proposal, or design. Goal: stress-test it from multiple angles, find blind spots and weaknesses.
  • Simulate mode — User gives a plan and wants to "dry run" it. Goal: walk through execution step by step, let hidden problems surface naturally.

State which mode you're using and why.


Research Mode

You are about to research a topic or design a solution. Do NOT go deep on one angle. Your job is to see the full picture before converging.

Step 1: Decompose into dimensions

Before researching anything, identify 3-5 independent dimensions of the problem. Ask yourself:

  • What are the different angles this could be viewed from?
  • What are the stakeholders / affected systems / competing concerns?
  • What would a devil's advocate focus on?

Output the dimensions as a numbered list. Each dimension should be genuinely different, not sub-points of the same thing.

Example for "should we migrate from REST to GraphQL?":

  1. Performance & scalability — latency, payload size, caching implications
  2. Developer experience — learning curve, tooling, debugging
  3. Existing ecosystem — what breaks, migration cost, backward compatibility
  4. Security — query complexity attacks, authorization model changes
  5. Business — timeline pressure, team skills, client requirements

Step 2: Parallel investigation

Spawn one subagent per dimension. Each agent:

  • Investigates ONLY its assigned dimension
  • Reads relevant code/docs for that angle
  • Lists findings with evidence (file paths, code references, data)
  • Flags risks and unknowns specific to that dimension
  • Does NOT try to propose a final solution — just reports findings

Launch agents in parallel, not sequentially.

Step 3: Synthesize

After all agents return, synthesize in the main conversation:

Read the full file on GitHub · 193 lines

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. 9d ago First seen · 193 lines · 41 tokens per session scan A 7768d38e43f8

Subscribe to this mod's changes

investigate is a skill published in the GitHub repository TechHU-GS/cc-discipline (0 stars, last pushed 5d ago), licensed MIT. It adds 41 tokens to every session and 1,768 once invoked, about $0.0002 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.

Related

Other skills, from other repositories

tokf-discover

Find missed token savings by scanning AI coding session files for commands that ran without tokf filtering.

mpecan/tokf · 24 tokens

ring:exploring-codebases

Exploring a codebase across phases: scopes the target, detects architecture, components, and layers, deep-dives each discovered perspective, then synthesizes findings into actionable guidance with file:line evidence. Use to understand how a feature or system works before planning changes, or to orient on an unfamiliar…

LerianStudio/ring · 91 tokens

skillnote

Self-hosted skill registry for OpenClaw. Stores procedures your team writes (name, description, body), syncs them to disk before each task, and collects which-helped/which-failed signals from the agent so the registry improves over time.

luna-prompts/skillnote · 54 tokens

xiaohongshu-image-creator

An image-making assistant for Xiaohongshu, a Chinese social platform for lifestyle, product, and educational posts. It creates vertical covers and supporting images matched to the post’s topic, audience, and visual style.

huangrichao2020/pretty-skills · 121 tokens

cross-campaign

Discover and reference other camps, projects, and files across camp boundaries. Use when the user mentions another camp or campaign by name, references work done "in another project/camp", or needs to find/copy/compare code across camps.

Obedience-Corp/festival · 52 tokens

activerecord

This skill should be used when the user asks to "write a migration", "add a column", "add column to table", "create an index", "add a foreign key", "set up associations", "fix N+1 queries", "optimize queries", "add validations", "create callbacks", "use eager loading", or mentions ActiveRecord, belongsto, hasmany…

hoblin/claude-ruby-marketplace · 180 tokens