Home / The Index / GitHub
Developing

How agent-ready is GitHub?

Independent agentability audit of GitHub, scored across the 8 principles of Agent Factors Engineering — how well AI agents can parse, navigate, and operate it.

Audited June 12, 2026 · Rubric v0 · 3 page(s) evaluated

Audit summary

GitHub's agentability audit returned an overall score of 41 out of 100 on its homepage, with similar results across pricing (36) and documentation (39) pages. These scores indicate that autonomous AI agents will encounter significant friction when attempting to parse, navigate, and interact with GitHub's public web presence.

The platform performs adequately on shadow UI avoidance (85) and status communication (65), meaning interactive elements are genuine HTML and system state is reasonably clear. However, GitHub scores poorly on transparency (0), clean handoffs (10), and defaults (26). Machine readability (61) and control mechanisms (45) fall into the mid-range, while chunking (37) also presents challenges for programmatic consumption.

These gaps suggest that while GitHub's interface works well for human users, it lacks the structured metadata, sensible pre-filled values, and clear action boundaries that AI agents need to operate reliably and safely.

Score by principle

Machine Readability61 / 100
Chunking37 / 100
Control45 / 100
Status65 / 100
Defaults26 / 100
Clean Handoffs10 / 100
No Shadow UI85 / 100
Transparency0 / 100

Key findings

Defaults
Pre-fill inputs with sensible defaults wherever a reasonable one exists.
Transparency
Surface confidence/certainty on key outputs (a confidence field in API responses, or a 'verified vs best-guess' label in the UI).
Transparency
Offer a one-line summary plus an expandable drill-down for important results.
Transparency
Attach source references or input citations (link or id) to generated outputs.
Control
Gate destructive actions behind an explicit, distinctly-labelled confirmation step — not a same-styled button.
Control
Support undo/override on completed actions (an 'Undo' on destructive changes, editable results).
No Shadow UI
Among the stronger areas for GitHub, scored 85/100.
Status
Among the stronger areas for GitHub, scored 65/100.
Machine Readability
Among the stronger areas for GitHub, scored 61/100.

How GitHub could improve its score

GitHub can improve its agentability by addressing the following issues identified in the audit:

  • Add JSON-LD structured data using schema.org vocabularies to describe primary entities on each page, enabling agents to parse content semantically.
  • Pre-fill form inputs with sensible defaults wherever a reasonable value exists, reducing the decision burden on autonomous systems.
  • Gate destructive actions behind explicit, distinctly-labelled confirmation steps rather than same-styled buttons, giving agents clear signals about action consequences.
  • Provide source references or input citations on generated outputs, allowing agents to trace provenance and verify information.
  • Use a single H1 element per page and maintain a contiguous heading hierarchy without skipped levels to improve document structure parsing.
  • Support undo or override capabilities on completed actions, particularly for destructive changes, so agents can recover from errors.

Work at GitHub? Re-audit any page free.

Scores refresh automatically when we re-crawl — or run an instant audit on any URL now.

Run a free audit

Embed this score

Show your agent-readiness in your docs or README. The badge links back to this live report.

<a href="https://agentability.io/index/github.html"> <img src="https://agentability.io/badge/github.svg" alt="GitHub — Agentability score 41/100 (Developing)" /> </a>