@Felipe P2
Here's your model with some changes so that the task executors will carry 100 boxes at a time:
simulacionbaseanswer.fsm
The way I did this was through a few changes to your Process Flow. First, I added a "Batch" activity to your Process Flow so that each Task Executor would take a batch of 100 items.

Here, 100 tokens are converted into 1 token with an array of items named "boxes". This is useful so that every 100 tokens will only need to acquire one AGV resource.
Next, I edited your load and unload activities so that 100 items would be loaded or unloaded at a time:

Here, a subflow is started that includes 100 child tokens, one for each box. I've given each token a label called "Index" to identify which box in the array the token corresponds to.
Finally, in the load and unload subflows, I set it up so that each child token would cause it's corresponding box in the array to be loaded:

This causes 100 boxes to be loaded onto an AGV. I used a similar subflow for unloading.
I also made a few other changes. I removed a "wait for processor to finish" activity since it was never firing and I made it so that it simply released the processors after the AGVs are done unloading. I also changed the capacity of the processors to 100 so that they could accept all of the items at once, but you can change that back if you want them to process one item at a time.
If you would like to change how fast the boxes are loaded/unloaded onto the AGVs, make sure to change the load/unload time in the AGV properties:

I hope this helps!