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.
npx agentmods add agents/danilkotelnikov/vedix/meta-analystgit clone --depth 1 https://github.com/danilkotelnikov/vedixWrote 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.
[](https://agentmods.dev/agents/danilkotelnikov/vedix/meta-analyst)<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>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.
| Model | Per session | Once 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 |
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.
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
-
Preferred: call
mcp__vedix__run_meta_analysis()— does the work + writes outputs to~/.vedix/meta_analysis.jsonand~/.vedix/what_works.json. Returns summary. -
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.
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.
- 4d ago First seen · 95 lines · 38 tokens per session scan A 39c85ea93743
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.
Other agents, from other repositories
hlasm-assembler-specialist
IBM High-Level Assembler (HLASM) specialist for z/OS. Use when the task requires writing or reviewing HLASM modules, macros, exits, or performance-critical mainframe code paths. For example: authoring a user SVC, reviewing a system exit, writing a macro for a shared copybook convention, or diagnosing an S0Cx abend…
AGENTS
Each file implements an AgentAdapter that reads local AI coding agent data.
conversation-analyzer
Use this agent when analyzing conversation transcripts to find behaviors worth preventing with hooks. Triggered by /egc-hookify without arguments.
signal-scorer
Searches and ranks prospects by relevance signals across X, Exa, and LinkedIn. Assigns weighted scores based on role, industry, activity, influence, and location.
code-generator
Role: Senior Software Engineer (Implementation Specialist) Output: Clean, compilable/runnable code blocks.
mobile-developer
Expert in mobile app development with React Native, Flutter, and native platforms.