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-kinematic-cuts-consultant)<a href="https://agentmods.dev/agents/madgraphteam/madagents/ma-kinematic-cuts-consultant"><img src="https://agentmods.dev/badge/agents/madgraphteam/madagents/ma-kinematic-cuts-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-kinematic-cuts-consultant"><img src="https://agentmods.dev/badge/agents/madgraphteam/madagents/ma-kinematic-cuts-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.00242 | $0.03605 |
| Opus 5 | $0.00121 | $0.01802 |
| Sonnet 5 | $0.00048 | $0.00721 |
| Haiku 4.5 | $0.00024 | $0.00361 |
Grade A, and why
ma-kinematic-cuts-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 9d 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.
This is a copy
84% identical to ma-aloha-consultant — 53 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Kinematic-Cuts Consultant
Role
You are the consultant for kinematic cuts configured in run_card.dat and enforced in the generated cuts.f. You describe what each cut parameter does, how the run-card knob maps to the Fortran cut routine, what the cut implementation actually checks, and the validity-time auto-corrections that adjust user choices for consistency with isolation, matching, and PDF setups.
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.
- 9d ago First seen · 126 lines · 242 tokens per session scan A 390bbd7689ca
ma-kinematic-cuts-consultant is an agent published in the GitHub repository MadGraphTeam/MadAgents (10 stars, last pushed 1mo ago), licensed MIT. It adds 242 tokens to every session and 3,605 once invoked, about $0.0012 per session on Opus 5. A static security scan graded it A with 0 findings. It is 84% identical to ma-aloha-consultant, differing in 53 lines, and is treated as a copy.
Other agents, from other repositories
editor
Journal editor who desk-reviews manuscripts, selects two referees with deliberately different dispositions, calibrates to a target journal from .claude/references/journal-profiles.md, and synthesizes an editorial decision (FATAL / ADDRESSABLE / TASTE). Used by /review-paper --peer [journal].
Geoprocessing Specialist
ArcPy and Python toolbox expert who automates spatial workflows — builds .pyt toolboxes, Model Builder processes, batch geoprocessing automation, and custom analysis scripts for ArcGIS Pro.
research-scout
Scans the NeqSim codebase to discover scientific paper opportunities that will drive code improvement. Every paper must improve NeqSim — adding tests, validating models against data, hardening algorithms, or implementing new capabilities. Produces ranked, actionable topics that feed into the planner agent.
mathodology-problem-analyst
Understand contest questions, requirements, mechanisms and decision needs.
astronomical-instrumentation-scientist
Reasons from system-level error budgets, the diffraction limit and Strehl ratio, detector figures of merit, and resolving power through Zemax/Code V tolerancing, ETC radiometry, AO modeling, and on-sky standard-star commissioning while treating flexure drift, IR persistence, ghosts, and quasi-static speckles as…
eic_agent
Journal-Fit Reviewer seat; contributes the journal-fit / originality / overall-quality review card — the final editorial decision is editorialsynthesizeragent's Phase 2 work.