Skip to content
GitHub Agentic Workflows

Meet the Workflows: Metrics & Analytics

Peli de Halleux

Excellent journey! Now it’s time to plunge into the observatory - the nerve center of Peli’s Agent Factory! Where we watch everything and know all!

In our previous post, we explored quality and hygiene workflows - the vigilant caretakers that investigate failed CI runs, detect schema drift, and catch breaking changes before users do. These workflows maintain codebase health by spotting problems before they escalate.

But here’s a question: when you’re running dozens of AI agents, how do you know if they’re actually working well? How do you spot performance issues, cost problems, or quality degradation? That’s where metrics and analytics workflows come in - they’re the agents that monitor other agents, turning raw activity data into actionable insights. This is where we got meta and built our central nervous system.

Data scientists, rejoice! These agents turn raw repository activity into actual insights:

  • Metrics Collector - Tracks daily performance across the entire agent ecosystem
  • Portfolio Analyst - Identifies cost reduction opportunities (because AI isn’t free!)
  • Audit Workflows - A meta-agent that audits all the other agents’ runs - very Inception

Here’s where things got meta: we built agents to monitor agents. The Metrics Collector became our central nervous system, gathering performance data that feeds into higher-level orchestrators. What we learned: you can’t optimize what you don’t measure. The Portfolio Analyst was eye-opening - it identified workflows that were costing us money unnecessarily (turns out some agents were way too chatty with their LLM calls).

These workflows taught us that observability isn’t optional when you’re running dozens of AI agents - it’s the difference between a well-oiled machine and an expensive black box.

You can add these workflows to your own repository and remix them. Get going with our Quick Start, then run one of the following:

Metrics Collector:

Terminal window
gh aw add https://github.com/github/gh-aw/blob/v0.37.7/.github/workflows/metrics-collector.md

Portfolio Analyst:

Terminal window
gh aw add https://github.com/github/gh-aw/blob/v0.37.7/.github/workflows/portfolio-analyst.md

Audit Workflows:

Terminal window
gh aw add https://github.com/github/gh-aw/blob/v0.37.7/.github/workflows/audit-workflows.md

Then edit and remix the workflow specifications to meet your needs, recompile using gh aw compile, and push to your repository. See our Quick Start for further installation and setup instructions.

Now that we can measure and optimize our agent ecosystem, let’s talk about the moment of truth: actually shipping software to users.

Continue reading: Operations & Release Workflows →


This is part 9 of a 19-part series exploring the workflows in Peli’s Agent Factory.