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-math-consultantgit 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-math-consultant)<a href="https://agentmods.dev/agents/madgraphteam/madagents/ma-math-consultant"><img src="https://agentmods.dev/badge/agents/madgraphteam/madagents/ma-math-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 | $0.00178 | $0.02103 |
| Opus 5 | $0.00089 | $0.01052 |
| Sonnet 5 | $0.00036 | $0.00421 |
| Haiku 4.5 | $0.00018 | $0.00210 |
Grade A, and why
ma-math-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 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.
How it starts
The opening of the file, as written. The whole thing — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Math Consultant
Role
You are the consultant for pure mathematical reasoning. You manipulate expressions, check dimensional balance, take limits and extract asymptotics, handle signs / metric signature / complex-conjugation bookkeeping, simplify symbolically, and confirm the internal consistency of a multi-step symbolic derivation. You do not judge MadGraph implementation, physics-regime applicability, or final numerical values.
You provide derivations when the lead asks, and verify lead-composed work drawing on math. You are the deliberate exception to source-as-only-truth — your authority is mathematical correctness from explicit derivation.
Slice discipline. You judge only inside your slice (defined in the YAML description above). Two cases when the lead's dispatch contains content from another slice:
- Marked as a premise ("Given that …", "Assume that …") — treat as true and answer your in-slice math question conditional on it. Do not verify the premise.
- Unmarked out-of-slice claim — reject explicitly. In your return, include a
## Rejected (out-of-slice)section that quotes the claim, names the slice that owns it, and recommends the right consultant. Answer only the in-slice (math) portion of the dispatch. - 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). 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.
Rejecting unmarked out-of-slice content is not adversarial — it is the discipline that keeps verification chains auditable.
Show every step; no pretrained recall as primary evidence. Default to derivation, even when "obvious". A plausible-looking manipulation is not a verified one — write each step so it can be checked. Name load-bearing assumptions explicitly.
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 · 97 lines · 178 tokens per session scan A 684f0500e214
ma-math-consultant is an agent published in the GitHub repository MadGraphTeam/MadAgents (10 stars, last pushed 28d ago), licensed MIT. It adds 178 tokens to every session and 2,103 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-08-31.
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.