Code

GitHub

Git repository hosting and collaboration

Overview Context types Tools Use cases Connection Security

Overview

Code is the least ambiguous statement of how something works. Modus mines the repositories you select, including files and pull requests, and gives agents a deep code Q&A tool plus the full GitHub API surface.

What Modus reads

1Repository
2Pull request
2File

You select the level Modus is allowed to mine. Everything below it is discovered automatically; everything outside it is never touched.

3context types mined

5agent tool groups

2connection methods

4security controls

Context types

Each object Modus mines produces typed context items, addressed by their position in the hierarchy. This is what an agent actually receives.

Repository metadata
The selected repositories, their languages, topics, and structure.
File metadata
Paths and content of the files that explain how the system behaves.
Pull request metadata
Titles, descriptions, reviews, and the reasoning captured in review threads.

Example context item

github_pull_request_metadata

acme/billing-servicePR #2841

Title: Exclude cancelled orders from net revenue
Merged: 2026-06-18 by @dana
Files: src/revenue/aggregate.ts · tests/revenue.spec.ts
Review note: "Matches the finance definition, not the warehouse one."

Tools

Tools are granted per skill, never globally. Anything that changes state in GitHub is marked as a write and stops for human approval.

Ask Codebase
Ask complex questions about a connected repository — code exploration, architecture, debugging, and deep analysis.
Read repository content
Repos, branches, trees, blobs, file contents, READMEs, tags, and releases.
Issues & pull requests
Search, list, and read issues, pull requests, reviews, review comments, and commits.
Write actions
Approval required
Create issues, comments, reviews, branches, commits, and file changes — each gated behind explicit approval.
Workflows
Inspect workflows, runs, and jobs, and dispatch a workflow when granted.

Common use cases

Settle "how is this actually calculated" by reading the implementation, not the docs.
Give an onboarding agent an accurate map of a service it has never seen.
Trace a metric change back to the PR that made it.

Connection method

Connect once. Modus stores credentials in a managed secret store, rotates what it can, and never asks an agent to handle them.

GitHub App (OAuth)

Install the Modus GitHub App and grant it the repositories you choose. Access is revocable from GitHub at any time.

Personal access token

A fine-grained PAT if you prefer to manage the credential yourself.

Security & governance

Governance is applied once, at the layer every agent runs through, so it holds no matter which agent asks.

Metadata-first mining

Modus learns from structure and usage, not bulk data. Raw records stay in your environment; only the metadata needed to understand the system is stored.

Scoped selection

You choose exactly which schemas, folders, spaces, or boards Modus is allowed to see. Nothing outside the selection is ever mined.

Write approval

Actions that change state in the source system are marked as writes and require an explicit human confirmation before they run.

Group access by sensitivity

Map your identity groups to sensitivity tiers so each team only ever composes context at or below its clearance.

Put GitHub to work.

Connect it in minutes and give every agent a governed understanding of what is inside, without moving a single row of data.

Book a demo