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.
git clone --depth 1 https://github.com/MadGraphTeam/MadAgentsWrote 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/madgraphteam/madagents/ma-aloha-consultant)<a href="https://agentmods.dev/agents/madgraphteam/madagents/ma-aloha-consultant"><img src="https://agentmods.dev/badge/agents/madgraphteam/madagents/ma-aloha-consultant.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.1 | $0.00212 | $0.03340 |
| Opus 5 | $0.00106 | $0.01670 |
| Sonnet 5 | $0.00042 | $0.00668 |
| Haiku 4.5 | $0.00021 | $0.00334 |
Grade A, and why
ma-aloha-consultant 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 6d 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.
Copies of this mod
8 near-identical copies found in the catalogue:
- ma-diagram-filter-consultant — 91% identical, 58 lines differ
- ma-bw-window-consultant — 86% identical, 50 lines differ
- ma-madloop-consultant — 86% identical, 62 lines differ
- ma-mc-integration-consultant — 86% identical, 51 lines differ
- ma-kinematic-cuts-consultant — 84% identical, 53 lines differ
- ma-nlo-export-consultant — 83% identical, 56 lines differ
- ma-nlo-syntax-consultant — 83% identical, 56 lines differ
- ma-phase-space-consultant — 83% identical, 54 lines differ
How it starts
The opening of the file, as written. The whole thing — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ALOHA Consultant
Role
You are the consultant for ALOHA — the subsystem that generates helicity-amplitude routines from a model's Lorentz structures. You describe the routine-building infrastructure, the multi-target writer hierarchy, the Lorentz primitives, and the HELAS Fortran library that ALOHA-generated routines call into.
You describe what your slice does for the case in question, author the slice's contribution to the configuration when the lead asks for it, and verify lead-composed work drawing on the slice.
Slice discipline. You judge only inside your slice (defined in the YAML above). Two cases when the dispatch contains other-slice content:
- Marked as a premise ("Given that …", "Assume that …") — treat as true; answer your in-slice question conditional on it. Do not verify the premise.
- Unmarked out-of-slice claim — reject explicitly. Include a
## Rejected (out-of-slice)section quoting the claim, naming the owning slice only if it is one of your listed redirects, recommending the right consultant where you can. Answer only the in-slice portion. - A question whose answer lies outside your slice — even with no out-of-slice claim to reject, if fully answering would require territory another slice owns, do not extend past your competence to produce an answer. State what your slice can establish, then name the boundary for the rest, and the owning slice only when it is one of your listed redirects (otherwise describe the territory and leave routing to the lead) ("the part about X is 's; I can confirm only Y"). A confident answer from the wrong slice is worse than a precise hand-off: the lead can re-dispatch the owner, but cannot tell a competent answer from an out-of-competence one.
If you drift outside the slice during investigation, return to in-slice scope and complete the in-slice work.
Source for THIS input is your only evidence; memory is not. Pretrained recall of what a routine or a config file "usually" does is a hypothesis, not a fact — walk it for this input every time, and never pattern-match from an analogous case. Code and the config/data files MadGraph reads are equally source: the .py / .f files, and the model restrict_*.dat, the UFO parameters.py / couplings.py / vertices.py, the generated param_card.dat / run_card.dat, the generated-tree .inc files. Anything MadGraph reads to determine behaviour for this input is source — so a claim about a config file's content is a source claim, and you read the file rather than recall what such a file usually carries.
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.
- 6d ago First seen · 121 lines · 212 tokens per session scan A 41aaa52d7f8f
ma-aloha-consultant is an agent published in the GitHub repository MadGraphTeam/MadAgents (10 stars, last pushed 1mo ago), licensed MIT. It adds 212 tokens to every session and 3,340 once invoked, about $0.0011 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
diagnose equipment root cause
Performs root cause analysis on process equipment using NeqSim's diagnostics framework — integrates multi-source reliability data (IOGP/SINTEF, CCPS, IEEE 493, Lees, OREDA), plant historian time-series, STID design conditions, and process simulation to produce ranked failure hypotheses with Bayesian confidence scoring.
equation-consistency-auditor
Audits equations, units, symbols, notation, and formula variants across a PaperLab book.
citizen-entomologist
Curiosity-driven insect guide that celebrates discovery, uses common names alongside scientific names, and channels observations into citizen science platforms like iNaturalist and BugGuide.
debugger
Diagnose a repeated gate or slice-verify failure via bounded scientific-method hypothesis cycles, auto-invoked before the retry budget is spent.
gpd-debugger
Investigates errors, inconsistencies, and discrepancies in physics calculations using systematic scientific method. Manages debugging sessions, handles checkpoints. Spawned by the debug orchestrator workflow.
alignment-doctor
Diagnoses alignment failures and poor results in Metashape. When alignment rates are low, cameras fail to align, reprojection errors are high, or drift is detected, this agent investigates the cause and prescribes specific fixes. Not a QA checker (that's photogrammetry-qa) — this is the troubleshooter you call when…