Sponsored Content

All of GitHub, for your AI agents

97 typed operations across pull requests, issues, Actions, releases and security alerts. Presets scope each agent to its job, and every write waits for a person.

Quick startRead the docs
$npx skills add https://github-tools.com
github.com/acme/app/pull/128

Add password reset #128

Open ana wants to merge 3 commits into main

  1. ana opened this 2 days ago

    Summary

    • Adds a "Forgot password?" link to the login page
    • Emails a one-time reset link
    • A new /reset page sets the new password

    Testing

    reset.test.ts covers the email and the reset page.

    Closes #92

Less to read, nothing written behind your back

Handed the raw GitHub API, a model reads every operation and every field GitHub returns, and its writes go straight through. Here is the same agent going through GitHub tools.

Raw GitHub APIGitHub tools

  • Tools the model reads on every request, for a code review

    Presets
    Raw API: 97 tools
    GitHub tools: 28 tools, the code-review preset

  • Tokens the model reads for one issue

    Tools
    Raw API: about 1,130 tokens
    GitHub tools: about 90 tokens

  • Writes that reach GitHub without a person

    Approval
    Raw API: all 48
    GitHub tools: none: each waits for your approval

Built for the jobs agents do on GitHub

Each guide pairs a preset with an integration and the code to run it.

Narrow by default

Pick the preset for the job, and keep approval on. The model then sees only that job's tools, and nothing it writes reaches GitHub until you say yes.

Quick start
agent.ts
import { createGithubAgent } from '@github-tools/sdk'const agent = createGithubAgent({  model: 'anthropic/claude-opus-5.5',  preset: 'code-review', // 28 tools, not 97  requireApproval: true, // every write waits for you})

Works where your agent runs

Compare integrations

Already using something else?

How GitHub tools differs from the GitHub MCP server, Octokit and the gh CLI, and when to use each.