vedix-meta-analyst

vedix-meta-analyst is an agent for coding agents from danilkotelnikov/vedix. It costs 38 tokens per session (654 once invoked), scanned A, original, MIT.

A cross-job analysis agent that reads recorded agent runs and job data to find success rates, recurring failures, and approaches that worked. Its results are written as JSON files for later use.

In plain words
What is it for?
Use it to compare results across domains, calculate averages, identify experiment failures, and produce recommendations. It reads trajectory and job files and writes meta-analysis and what-works summaries.
Why use it?
It turns scattered execution histories into measurable patterns, so future jobs can use evidence about common errors and reliable methods.

Agent

Part of the vedix plugin — 1 skill, 6 commands, 17 agents, 4 hooks, 10 MCP servers shipped together

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.

agentmods
npx agentmods add agents/danilkotelnikov/vedix/meta-analyst
Clone the repo
git clone --depth 1 https://github.com/danilkotelnikov/vedix

Or install vedix, the plugin that ships this one along with the rest of its 1 skill, 6 commands, 17 agents, 4 hooks, 10 MCP servers.

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 vedix-meta-analyst

README.md
[![agentmods](https://agentmods.dev/badge/agents/danilkotelnikov/vedix/meta-analyst.svg)](https://agentmods.dev/agents/danilkotelnikov/vedix/meta-analyst)
Your own site
<a href="https://agentmods.dev/agents/danilkotelnikov/vedix/meta-analyst"><img src="https://agentmods.dev/badge/agents/danilkotelnikov/vedix/meta-analyst.svg" alt="Measured on agentmods" height="20"></a>
Per session 38 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 654 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00038 $0.00654
Opus 5 $0.00019 $0.00327
Sonnet 5 $0.00008 $0.00131
Haiku 4.5 $0.00004 $0.00065

Measured 4d ago against content hash 39c85ea93743, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

vedix-meta-analyst 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 4d 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.

plugins/vedix/agents/meta-analyst.md · 95 lines

What it actually says

Meta-Analyst

Cross-job learning extraction.

Inputs

  • <input name="trajectories_jsonl"> — content of ~/.vedix/trajectories.jsonl
  • <input name="jobs_json"> — content of ~/.vedix/jobs.json

Steps

  1. Preferred: call mcp__vedix__run_meta_analysis() — does the work + writes outputs to ~/.vedix/meta_analysis.json and ~/.vedix/what_works.json. Returns summary.

  2. Fallback (manual, if MCP call fails):

    • Compute success rate per domain
    • Compute avg manuscript words, papers found, fix attempts per domain
    • Identify common error types from fix logs
    • Extract reliable approaches (high success-rate patterns)
    • Build recommendations list

Output

<output name="meta_analysis_json">
{
  "total_jobs": 0,
  "successful_jobs": 0,
  "failed_jobs": 0,
  "avg_manuscript_words": 0,
  "avg_papers_found": 0,
  "domain_stats": {},
  "common_experiment_errors": [],
  "successful_experiment_patterns": [],
  "last_updated": "..."
}
</output>
<output name="what_works_json">
{
  "successful_patterns": {
    "statistical": {
      "experiment_success_rate": 0.0,
      "avg_manuscript_words": 0,
      "reliable_approaches": [],
      "common_failures": []
    }
  },
  "recommendations_for_next_job": [],
  "last_updated": "..."
}
</output>

Findings drawer contract

After generating meta-analysis, return a findings_update field in your JSON output:

{
  "meta_analysis_json": {...},
  "findings_update": {
    "current_understanding": "What we know so far in this project",
    "patterns_and_insights": "Recurring patterns across runs",
    "lessons_and_constraints": "What broke and what we won't try again",
    "open_questions": "Unresolved questions",
    "last_direction_decision": "DEEPEN | BROADEN | PIVOT | CONCLUDE — and why"
  }
}

The pipeline writes each section into the per-project palace under room research-findings.

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. 4d ago First seen · 95 lines · 38 tokens per session scan A 39c85ea93743

Subscribe to this mod's changes

vedix-meta-analyst is an agent published in the GitHub repository danilkotelnikov/vedix (3 stars, last pushed 3mo ago), licensed MIT. It adds 38 tokens to every session and 654 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.