Perf improvement: antiforgery-generation, csrf-accepted, fortunes

| Scenario | Environment | Date | Old RPS | New RPS | Change | Deviation | StDev | Dependencies |
| -------- | ----------- | ---- | ------- | ------- | ------ | --------- | ----- | ------------ |
| antiforgery-generation | Antiforgery Token Generation 13- Trends cobalt-hosted-lin | 08/20/2026 21:02:07 | 193,172 | 223,725 | 15.82 % (30,554) :thumbsup: | 2.63 σ | 11,600.23 | Changes NameVersionDiff Antiforgery.dll `1.0.0` -> `1.0.0` https://github.com/aspnet/Benchmarks/compare/09ea584cdf617e9dc64286db9805476bb7a98c6c...2c03e2788692535e81a6eea412a35a0a181d1d1e |
| csrf-accepted | CSRF Accepted 13- Trends cobalt-hosted-lin | 08/20/2026 21:03:04 | 295,137 | 691,791 | 134.40 % (396,655) :thumbsup: | 2.14 σ | 185,401.58 | Changes NameVersionDiff Antiforgery.dll `1.0.0` -> `1.0.0` https://github.com/aspnet/Benchmarks/compare/09ea584cdf617e9dc64286db9805476bb7a98c6c...2c03e2788692535e81a6eea412a35a0a181d1d1e |
| fortunes | Fortunes Blazor SSR 19- Trends Database cobalt-hosted-lin | 08/20/2026 23:43:18 | 62,147 | 97,534 | 56.94 % (35,387) :thumbsup: | 2.69 σ | 13,159.62 | Changes NameVersionDiff BlazorSSR.dll `1.0.0` -> `1.0.0` https://github.com/aspnet/Benchmarks/compare/09ea584cdf617e9dc64286db9805476bb7a98c6c...2c03e2788692535e81a6eea412a35a0a181d1d1e |

[PowerBI Dashboard](https://aka.ms/aspnet/benchmarks)

@sebastienros

Start by reviewing the antiforgery-generation, csrf-accepted, and fortunes benchmark results in the issue, then inspect the linked PowerBI dashboard for context. The issue does not name files, tests, an entry point, or a specific change, so the desired implementation and completion criteria remain undefined.

Written by the indexing model from the issue text.