Have you checked the Templates section of this community? I'd also suggest gathering the requirements from your key stakeholders and put together a simple draft and go through a few inspect & adapt iterative cycles to fit their needs.
My project reporting, like my projects, is uniquely tailored to meet the needs of my stakeholders. It ranges from what we did-what we'll do-obstacles all the way to full dashboards with budget, milestones, issues, risks and dependencies. The amount of reporting should be proportional to the size of your project.
Be wary of agile project reporting to senior management. You often have to educate senior management that scope is the variable, not the constant. Answering questions like "when will all the scope be completed" becomes a nightmare to answer Saving Changes...
