ariadne: Agent for Claude Code

.claude/agents/triage-aggregator.md

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

A triage-results grouping tool that combines investigations describing the same underlying cause.

In plain words
What is it for?
Reading a triage state file, filtering completed false positives, merging related group IDs, and writing a shared cause for each canonical group.
Why use it?
It prevents duplicate false-positive groups when separate investigators identify the same detection gap.

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

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

Your own site · 80×15
<a href="https://agentmods.dev/agents/crjfisher/ariadne/triage-aggregator"><img src="https://agentmods.dev/badge/agents/crjfisher/ariadne/triage-aggregator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 28 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 557 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.00028 $0.00557
Opus 5 $0.00014 $0.00279
Sonnet 5 $0.00006 $0.00111
Haiku 4.5 $0.00003 $0.00056

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

Security

Grade A, and why

triage-aggregator 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/agents/triage-aggregator.md · 57 lines

How it starts

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

Purpose

You read a triage state file containing completed investigation results and group all false-positive entries by shared root cause. Independent investigator agents may have assigned different group_id values to entries that share the same underlying detection gap — your job is to merge these into canonical groups.

Instructions

  1. Read the triage state file at the path provided in your prompt. Parse the JSON to access the entries array.

  2. Filter to completed false-positive results. Only process entries where:

    • status === "completed"
    • result !== null
    • result.is_true_positive === false
    • result.is_likely_dead_code === false
  3. Analyze group_id and root_cause values across all false-positive results. Identify entries that describe the same detection gap even if they use different group_id strings. For example, "method-chain" and "chained-method-call" likely describe the same root cause.

  4. Merge into canonical groups:

    • Choose the most descriptive and precise group_id as the canonical name
    • Use kebab-case for all group IDs
    • Write a unified root_cause description that covers all entries in the group
    • Track which entry indices (0-based position in the entries array) belong to each group
  5. Preserve true-positive and dead-code entries in separate groups. Create a "true-positive" group and a "dead-code" group for entries classified as such.

  6. Verify completeness: Every completed entry must appear in exactly one group. No entries should be orphaned or duplicated.

Output Format

Return raw JSON (no markdown fencing, no extra text):

{
  "groups": [
    {
      "group_id": "canonical-kebab-case-id",
      "root_cause": "Precise description of the shared detection gap",
      "entry_indices": [0, 3, 7]
    }
  ],
  "total_entries_grouped": 15,
  "total_groups": 4
}
  • groups contains all canonical groups, including "true-positive" and "dead-code" groups
  • entry_indices are 0-based positions in the state file's entries array
  • total_entries_grouped must equal the count of completed entries
  • total_groups must equal the length of the groups array

Read the full file on GitHub · 57 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 · 57 lines · 28 tokens per session scan A 684ea061d548

Subscribe to this mod's changes

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