Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/MadGraphTeam/MadAgentsnpx agentmods add skills/madgraphteam/madagents/installWrote 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/skills/madgraphteam/madagents/install)<a href="https://agentmods.dev/skills/madgraphteam/madagents/install"><img src="https://agentmods.dev/badge/skills/madgraphteam/madagents/install/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/skills/madgraphteam/madagents/install"><img src="https://agentmods.dev/badge/skills/madgraphteam/madagents/install.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.00062 | $0.02468 |
| Opus 5.5 | $0.00025 | $0.00987 |
| Sonnet 5.5 | $0.00012 | $0.00494 |
| Haiku 4.5 | $0.00006 | $0.00247 |
Grade B, and why
install scanned grade B with 1 finding 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
cp ../madagents_codex/.codex/config.toml <target>/.codex/ How it starts
The opening of the file, as written. The whole thing — 214 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Install MadAgents into a folder
Your working directory is install/; the repo root is ... You perform the
install — there is no installer script. What is left of installer.py is a
read-only verify command.
Read install-policy.md before you write anything. It holds the five
invariants (never remove what you do not own; copy bytes, never transcribe;
report collisions by name; no automatic git init; always verify) and the
manifest format. This file is the procedure; that one is the contract, and the
Claude Code installer works to the same one.
In install/ beside the policy, read on demand:
example-install.md— a finished install in full: the tree, the wrapper, the manifest.troubleshooting.md— the failure modes and how to tell them apart.
1. Ask, then survey — and survey before you write
Where. The folder to install into. It becomes the project root, so it should
be the folder the user will actually work in. Accept ~.
Which memory pack. List them from the source of truth, not from memory:
python3 -c "import sys; sys.path.insert(0,'../src'); from launcher.setup import memory_options; [print(f'{n:18} {d}') for n, d in memory_options()]"
pretrained is the default and right for Anthropic models; the -local packs
are for a self-hosted model; none starts cold.
Which CLI to install for. codex or claude_code. This is independent of
which CLI you run under: you are Codex, and you can install either. An install
belongs to one provider, and there is no conversion afterwards.
Then survey the target and report what you find before writing anything:
ls -A <target> 2>/dev/null
cat <target>/.madagents/install.json 2>/dev/null
2. Classify — the step that used to be a bad guess
| What you see | What it is | What you do |
|---|---|---|
| Folder empty or absent | a fresh install | §3 |
.madagents/install.json present |
an existing MadAgents install | §4, upgrade |
| Files present, no manifest | the user's own project | §5, additive — ask first |
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 · 214 lines · 62 tokens per session scan B 43aae40d4bed
install is a skill published in the GitHub repository MadGraphTeam/MadAgents (14 stars, last pushed 2mo ago), licensed MIT. It adds 62 tokens to every session and 2,468 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…