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-process-syntax-consultant)<a href="https://agentmods.dev/agents/madgraphteam/madagents/ma-process-syntax-consultant"><img src="https://agentmods.dev/badge/agents/madgraphteam/madagents/ma-process-syntax-consultant/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.
<a href="https://agentmods.dev/agents/madgraphteam/madagents/ma-process-syntax-consultant"><img src="https://agentmods.dev/badge/agents/madgraphteam/madagents/ma-process-syntax-consultant.svg" alt="Reviewed on agentmods" width="80" 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.00224 | $0.03752 |
| Opus 5.5 | $0.00090 | $0.01501 |
| Sonnet 5.5 | $0.00045 | $0.00750 |
| Haiku 4.5 | $0.00022 | $0.00375 |
Grade A, and why
ma-process-syntax-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 1mo 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.
How it starts
The opening of the file, as written. The whole thing — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Process-Syntax Consultant
Role
You are the consultant for the process-syntax parser entry in MadGraph. You describe how generate and add process lines are tokenized and validated — the extract_process orchestration, particle-name resolution, multiparticle expansion at the process line, tagged particles (!a!), the process number @N, the check command and the validators it calls, and the define command.
Cross-seam — does the model carry the vertex. With ma-ufo-consultant (the UFO-content owner) you jointly own whether the loaded model actually declares the vertex the process line presumes — the failure that runs cleanly while computing the wrong thing. Run that cross-check yourself rather than assume the model side did; flag to the lead when a process line presumes an interaction the model may not declare.
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.
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.
- 1mo ago First seen · 132 lines · 224 tokens per session scan A 8f29236ce0d9
ma-process-syntax-consultant is an agent published in the GitHub repository MadGraphTeam/MadAgents (14 stars, last pushed 2mo ago), licensed MIT. It adds 224 tokens to every session and 3,752 once invoked, about $0.0009 per session on Opus 5.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-09-03.
Other agents, from other repositories
diagnose equipment root cause
Performs root cause analysis on process equipment — compressor trips and vibration, pump and compressor efficiency loss, separator carryover, heat-exchanger fouling and U-value degradation, cooling-water and cooling-medium performance loss, valve and capacity limitations — using NeqSim's diagnostics framework, which…
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.
equation-consistency-auditor
Audits equations, units, symbols, notation, and formula variants across a PaperLab book.
debugger
Diagnoses data quality issues and analysis failures using scientific hypothesis-testing methodology. Invoked by orchestrator when errors occur during pipeline execution or when code-reviewer identifies complex issues requiring root-cause analysis.
debugger
Diagnose a repeated gate or slice-verify failure via bounded scientific-method hypothesis cycles, auto-invoked before the retry budget is spent.
scientific-evidence-reviewer
Independently review scientific tool outputs and generated artifacts for numerical correctness, reproducibility, missing evidence, and unsupported success claims.