The OP didn't provide us with an SSCCE tho, it's hard to tell what he really needs.

Shouldn't verbose mode show them?

karlgoethebier suggested it earlier in the discussion, but hv has not come back and told us results in the specific circumstances.

But creating my own simple SSCCE shows that verbose does, in fact, shows TODOs.

C:\tmp\perl
> type t\11163309.t
use 5.014; # //, strict, say, s///r
use warnings;
use Test::More;

ok 1, "gimme";

TODO: {
    local $TODO = "proof of concept";
    ok 0, "failing TODO";
}

done_testing;


C:\tmp\perl
> prove
t\11163309.t .. ok
All tests successful.
Files=1, Tests=2,  1 wallclock secs ( 0.12 usr +  0.00 sys =  0.12 CPU
+)
Result: PASS


C:\tmp\perl
> prove -v
t\11163309.t ..
ok 1 - gimme
not ok 2 - failing TODO # TODO proof of concept
#   Failed (TODO) test 'failing TODO'
#   at t\11163309.t line 11.
1..2
ok
All tests successful.
Files=1, Tests=2,  0 wallclock secs ( 0.09 usr +  0.02 sys =  0.11 CPU
+)
Result: PASS
[download]

And if the TODO test is changed to a passing value, then both non-verbose and verbose indicate in the Test Summary Report that the TODO test is now passing (to tell you that it may be safe to remove the TODO-ness):

C:\tmp\perl
> prove
t\11163309.t .. ok
All tests successful.

Test Summary Report
-------------------
t\11163309.t (Wstat: 0 Tests: 2 Failed: 0)
  TODO passed:   2
Files=1, Tests=2,  0 wallclock secs ( 0.08 usr +  0.03 sys =  0.11 CPU
+)
Result: PASS


C:\tmp\perl
> prove -v
t\11163309.t ..
ok 1 - gimme
ok 2 - passing TODO # TODO proof of concept
1..2
ok
All tests successful.

Test Summary Report
-------------------
t\11163309.t (Wstat: 0 Tests: 2 Failed: 0)
  TODO passed:   2
Files=1, Tests=2,  0 wallclock secs ( 0.09 usr +  0.02 sys =  0.11 CPU
+)
Result: PASS
[download]