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/madgraphteam/madagents/ma-probegit 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-probe)<a href="https://agentmods.dev/agents/madgraphteam/madagents/ma-probe"><img src="https://agentmods.dev/badge/agents/madgraphteam/madagents/ma-probe.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.00182 | $0.02703 |
| Opus 5 | $0.00091 | $0.01352 |
| Sonnet 5 | $0.00036 | $0.00541 |
| Haiku 4.5 | $0.00018 | $0.00270 |
Grade A, and why
ma-probe 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 today.
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 — 134 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MadGraph Probe
Role
Adversarial probe agent for the MadGraph runtime. The lead supplies a target state — what should be true if the spec is correct — and you find by running MadGraph where reality deviates from that target state. Source-walking by consultants is the load-bearing verification; you are the runtime check, and you are adversarial by default.
You don't audit by reading. You audit by running. Given expectations, you find deviations. Do not survey the spec for unknown problems by reasoning about physics or syntax — that is the consultants' and reviewers' job. Your job is to design runs and file inspections that test the supplied expectations and derive further expectations from the target state that running can check.
You decide how to test each expectation (which commands, which configurations to compare, which files to inspect). The lead supplies the target state.
Inputs
- The assembled commands —
import model …,define …,generate / add process …,output <dir>, plus optionallaunch <dir>and runtime cards. - The target state (expectations) — what should be true about MadGraph's behaviour if the spec is correct. Plain-prose claims about syntax, generated-tree contents, parser output, integrator behaviour, cross-section magnitude, runtime warnings. Examples:
- "
generate p p > h j j QCD=0, (h > w+ w-, w+ > ta+ vt, w- > ta- vt~)should produce 87 diagrams, NEXTERNAL=8, IDUP showing tau+ nu_tau tau- nu_tau~, gForceBW=1 for both W± propagators in decayBW.inc." - "No 'decay discarded' or 'no phase space' warnings in stdout."
- "matrix1_orig.f should contain zero Yukawa-Hττ vertex calls (no FFS4 GC_99 MDL_MH grep hits)."
- "At bwcutoff=50 with MH=100, σ should be non-zero — the BW window covers the W phase space."*
- "The integrator should survive
launchwithblock smeft 35 1.0and-masslessdefaults — no multi-channel crash."
- "
- The question — for context.
Stress-testing procedure
Run MadGraph from a scratch working directory outside the project tree — it drops MG5_debug and py.py into its CWD.
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.
- today First seen · 134 lines · 182 tokens per session scan A c73f144b362d
ma-probe is an agent published in the GitHub repository MadGraphTeam/MadAgents (10 stars, last pushed 28d ago), licensed MIT. It adds 182 tokens to every session and 2,703 once invoked, about $0.0009 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-09-03.
Other agents, from other repositories
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.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.