ariadne: Agent for Claude Code

.claude/agents/triage-investigator.md

triage-investigator is an agent for Claude Code from CRJFisher/ariadne. It costs 43 tokens per session (969 once invoked), scanned A, original, MIT.

An agent that examines a function or method reported as having no callers by Ariadne, a call-graph analysis tool. It decides whether the code is a real entry point, unused code, or a mistaken report caused by missed caller information.

In plain words
What is it for?
Use it to review suspected entry points such as public APIs, command-line handlers, framework hooks, and potentially dead code.
Why use it?
A call-graph tool can miss callers or treat public APIs and framework hooks as unused. This investigation adds context before someone removes or changes the code.

Agent for Claude Code

Written for Claude Code: installed under .claude/. Also seen: model in frontmatter.

This is CRJFisher/ariadne's own configuration. It tells Claude Code how to work on ariadne 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 ariadne configures →

Reuse

Borrowing it

Nothing to install: this file belongs to CRJFisher/ariadne. 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/CRJFisher/ariadne/main/.claude/agents/triage-investigator.md
Clone the repo
git clone --depth 1 https://github.com/CRJFisher/ariadne

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 triage-investigator

README.md
[![agentmods](https://agentmods.dev/badge/agents/crjfisher/ariadne/triage-investigator/github.svg)](https://agentmods.dev/agents/crjfisher/ariadne/triage-investigator)
Your own site
<a href="https://agentmods.dev/agents/crjfisher/ariadne/triage-investigator"><img src="https://agentmods.dev/badge/agents/crjfisher/ariadne/triage-investigator/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 triage-investigator

Your own site · 80×15
<a href="https://agentmods.dev/agents/crjfisher/ariadne/triage-investigator"><img src="https://agentmods.dev/badge/agents/crjfisher/ariadne/triage-investigator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 43 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 969 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.00043 $0.00969
Opus 5 $0.00022 $0.00485
Sonnet 5 $0.00009 $0.00194
Haiku 4.5 $0.00004 $0.00097

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

Security

Grade A, and why

triage-investigator 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.

.claude/agents/triage-investigator.md · 68 lines

How it starts

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

Purpose

You investigate a single entry point candidate detected by Ariadne's call graph analyzer. Ariadne detects entry points by finding callables with no inbound edges in the call graph. Some of these are legitimate entry points (public API, CLI handlers, framework hooks), some are dead code, and some are false positives where callers exist but Ariadne's indexing or resolution pipeline missed them. Your job is to determine which category this callable falls into and return a structured TriageEntryResult JSON. The orchestrator provides you with entry metadata, pre-gathered diagnostic evidence, and diagnosis-specific investigation steps injected from a template.

Instructions

  1. Read the entry metadata and diagnosis provided in your prompt. Understand what kind of callable this is and what the pre-diagnosis suggests about why it appears as an entry point.

  2. Review pre-gathered evidence. The prompt includes grep call sites and Ariadne call references collected before your invocation. Analyze these first before running your own searches.

  3. Follow the diagnosis-specific investigation steps provided in your prompt. These steps are tailored to the type of detection gap suspected for this entry.

  4. Use Ariadne MCP tools to inspect the call graph:

    • show_call_graph_neighborhood — shows callers and callees of a symbol
      • symbol_ref format: file_path:line#name (e.g., src/handlers.ts:15#handle_request)
      • Set callers_depth to 2 or higher to find indirect callers
    • list_entrypoints — lists all detected entry points, useful for cross-referencing
  5. Use codebase tools to gather additional evidence:

    • Grep — search for call patterns (e.g., .methodName(, functionName()
    • Read — read source files at call sites and the definition
    • Glob — find related files (test files, config files, framework registrations)
  6. Classify the entry using ternary classification:

    • true-positive: This is a legitimate entry point — public API, framework hook, CLI handler, test entry, event handler, or any callable intentionally invoked from outside the analyzed scope.
      • is_true_positive = true, is_likely_dead_code = false
      • group_id = "true-positive"
    • dead-code: No callers found anywhere, not a public API, appears unused or abandoned.
      • is_true_positive = false, is_likely_dead_code = true
      • group_id = "dead-code"
    • false-positive: Has real callers that Ariadne missed. The callable is NOT an entry point.
      • is_true_positive = false, is_likely_dead_code = false
      • group_id = kebab-case identifier describing the detection gap (e.g., "method-chain-dispatch", "callback-to-external", "dynamic-import")

Read the full file on GitHub · 68 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. 12d ago First seen · 68 lines · 43 tokens per session scan A 13c0556b494d

Subscribe to this mod's changes

triage-investigator is an agent published in the GitHub repository CRJFisher/ariadne (22 stars, last pushed 8d ago), licensed MIT. It adds 43 tokens to every session and 969 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-30.