Skip to content
Back to skills

Codex Investigate

ASecurity

Investigate broken behavior using the shared evidence-driven method, scaling from a normal root-cause pass to a deep falsifiable experiment loop.

  • 9 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added September 23, 2026
ai-agents

Works with

  • cli

Security analysis

A100/100

Scanned September 23, 2026

npx -y skills add greenfield-inc/agent-farm --skill codex-investigate --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Codex Investigate?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Codex Investigate
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/greenfield-inc-codex-investigate/badge)](https://www.skillsdirectory.com/skills/greenfield-inc-codex-investigate)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: investigate
description: Investigate broken behavior using the shared evidence-driven method, scaling from a normal root-cause pass to a deep falsifiable experiment loop.
---

# Investigate

Read `.references/artifact-storage.md`; share safe diagnostic artifacts in
Grain when available, keeping local evidence and cleanup requirements intact.

You are the single investigator for this request. Find the root cause before proposing a fix.

1. Read `.references/investigation-method.md`.
2. Build the defect brief: expected behavior, observed behavior, reproduction, environment, frequency, existing evidence, and authorization boundaries.
3. Select **normal** depth for deterministic scoped failures with a clear trail. Select **deep** for intermittent, stateful, cross-boundary, timing-sensitive, renderer-dependent, previously misdiagnosed, or explicitly thorough investigations.
4. Follow the shared method at the selected depth. Escalate normal to deep only when the evidence cannot distinguish the leading hypotheses.
5. Return the root cause and confidence first, followed by reproduction, observations, file:line or runtime evidence, introduction point, and high-level resolution direction.

Rules:

- Diagnose, do not fix.
- Do not spawn sub-agents or invoke agent CLIs.
- Do not guess or silently upgrade confidence.
- Do not edit project files unless the user explicitly authorizes temporary diagnostic logging.
- Remove all diagnostic logging and temporary investigation edits before the final report.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

View all in ai-agents →

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.