After looking into your arsenal, I have considered adding support to work with this mod. Namely, adding the portable MOX-reactor equipment.
88 mm and 128 mm variants of cannon shells for my heavy & super-heavy tanks are also possible. Just your existing cannon shells are too vastly overpowered in my taste. :D I am not a nuclear physicists (though I have a major in physics), but it seems if there is a thing called "depleted plutonium" (not used in real world because of several concerns, like being quite unstable, but I totally ACCEPT this as a sci-fi game mod) and use it in armour-piercing rounds like in DU-style, they are not that vastly better if considering the physical properties. The penetration power of DU rounds mainly comes from the very high density (19.1 g/cm^3). In comparison, Plutonium has 19.8 g/cm^3, which is just a bit denser. It would not be sufficient for the extra +50% damage over the DU cannon shells. From my unprofessional knowledge in physics, it would be about +11% penetration power. But exaggerating it up to +20% is still fine (gameplay-wise).
But before that, there is one thing bothering me, the license of your mod: AGPL v3.
Before talking about those license terms, first let me list what I have to do with your code & resources:
1. My mod does nothing if your mod is not enabled. Thus, the "new" items are added only when both mods are enabled.
2. Using graphics (icons & spritesheet) from your mod, with some modification. Like adding a lower-left tank mini-icon to indicate the MOX-reactor is a tank-equipment variant. (Though I don't have to "pack" your graphics in my mod actually. Just linking your icons and second overlay for the caliber and tank equipment indicators.)
3. Using part of your code with modification. Since that would be based on your reactor and ammo items.
4. I do not want to change my mod's license to AGPL v3. The terms are somehow ambiguous. I do not want to prevent other people from developing any compatible mods with mine, just because of this. In comparison, currently I can give permissions to people in using my code, not enforcing them to change to the same license. (see below)
I am not a lawyer, my following conclusions are made by reading some (if not a lot of) articles about the license. It seems there are two main opinions which are quite opposite:
1. Since I would be using your code (and resources), this counts as "modifying" and "derivative" work. My work needs to be bounded by the same license (AGPL v3), which is what I want to avoid exactly. (Because it then make any mods doing anything with mine enforced under the same license, like a chain...)
2. It is seen as a "compatible" work. Those parts will not show up without your mod, rather than as independent items. An example (maybe not a good one though) is like OpenOffice having the compatibility to open MS Office documents. OpenOffice obviously has very different license from the copyrighted MS products.
BUT, in the first place, do you want such mods compatibility? ONLY if you agree, then we can start to find out what can be done with the license...