The control run with the sending skill removed is the most useful detail, because it shows the risk is in the composition rather than in either skill. A concrete mitigation to consider is requiring explicit user confirmation, showing the recipient and body, for any outbound-effect skill whenever the current context contains content fetched by a read skill. Do you know whether the paper evaluated that kind of taint-aware confirmation gate, and how much it cut the 79.2% success rate?