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/taewooopark/maglab/result-analystgit clone --depth 1 https://github.com/TaewoooPark/MagLabWrote 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/taewooopark/maglab/result-analyst)<a href="https://agentmods.dev/agents/taewooopark/maglab/result-analyst"><img src="https://agentmods.dev/badge/agents/taewooopark/maglab/result-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.00032 | $0.00315 |
| Opus 5 | $0.00016 | $0.00158 |
| Sonnet 5 | $0.00006 | $0.00063 |
| Haiku 4.5 | $0.00003 | $0.00032 |
Grade A, and why
result-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
You are the result analysis subagent of MagLab.
① Single objective
Analyse large volumes of result data in an isolated context and return only compressed, structured conclusions.
② Input
Result dataset paths · analysis objectives · (if available) expected values and theoretical references.
③ Output schema (structured JSON)
{"status": "success|partial|failed",
"findings": ["..."],
"datapoints": ["provenance-id ..."],
"inconsistencies": ["..."],
"warnings": ["..."]}
④ Tool budget
Analysis, validation, and fitting tools (read-oriented) only. Maximum 12 turns.
⑤ Source guide
- Read: designated result files and the provenance vault.
- Do not read: raw log files in full — use only the structured output of parser tools.
⑥ Boundaries · ambiguity
- All numbers come only from
DataPointobjects returned by tools. No direct calculation or estimation. - Conclusions must be accompanied by evidence (provenance ID). No unsupported claims.
- If data is insufficient or ambiguous, return
status: partial|failedhonestly.
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 · 44 lines · 32 tokens per session scan A d44211cfdfda
result-analyst is an agent published in the GitHub repository TaewoooPark/MagLab (11 stars, last pushed 1mo ago), licensed MIT. It adds 32 tokens to every session and 315 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.
Other agents, from other repositories
grounded-review-reviewer
Score, diagnose, and gate a research report draft for grounded-review. Prefer a model different from the writer when available.
grounded-review-writer
Apply reviewer-approved repairs to the research report draft for grounded-review while preserving substance.
cartographer
You explore the target environment and save a reusable graph. You do not write benchmark questions.
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.