Agent skill

SEO Audit

by unifapi-agent in unifapi-agent/agents

When the user wants to audit, review, or diagnose SEO issues on their site.

MITAuto-check passedMarketing & SEO

Install SEO Audit

skills CLI
$ npx skills add unifapi-agent/agents --skill seo-audit -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install unifapi-agent/agents seo-audit --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/unifapi-agent/agents.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/seo-agent/seo-audit .claude/skills/seo-audit && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
seo-audit
GitHub stars
589
Token cost
~3.4k tokens
SKILL.md length
1,282 words
Files
5 (incl. references)
Skills in repo
47
Repo updated
First seen
Licence
MIT

At a glance

When the user wants to audit, review, or diagnose SEO issues on their site.

  • Works in 7 steps: Scope. Confirm the site, the priority… → Render the pages. For each priority URL,… → Pull rank + competitor reality.… → …
  • Diagnose SEO issues on their site
  • SKILL.md covers Use UnifAPI for live evidence, Workflow, The 5 Pillars (audit in this… and Finding Schema, plus 6 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

SEO Audit is an agent skill from unifapi-agent/agents. When the user wants to audit, review, or diagnose SEO issues on their site. Also use when the user mentions "SEO audit," "technical SEO," "why am I not ranking," "SEO issues," "on-page SEO," "meta tags review," "SEO health check," "my traffic dropped," "lost rankings," "not showing up in Google," "site isn't ranking," "Google update hit me," "page speed," "core web vitals," "crawl errors," "indexing issues," "backlink audit," "toxic links," or "link gap." Use this even if the user just says something vague like…

Its SKILL.md is about 3.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including reference files (for example `README.md`, `references/ai-writing-detection.md` and `references/international-seo.md`).

It sits in Marketing & SEO, covering SEO audit, Web performance and On-page SEO. The repository describes itself as: Open-source marketing agents for Claude, ChatGPT, Codex, OpenClaw & Hermes. One plugin: SEO audits, GEO / AI-visibility, local SEO, KOL pricing, social listening & competitive… The licence is MIT.

When your agent uses it

  • Diagnose SEO issues on their site
  • The user mentions SEO audit
  • Why am I not ranking
  • Meta tags review

Example prompts

  • “SEO audit,”
  • “technical SEO,”
  • “why am I not ranking,”
  • “/seo-audit”

Workflow steps

7 steps, taken from the first numbered list in SKILL.md.

  1. Scope. Confirm the site, the priority keywords, the named competitors, and whether this is a full-site or single-page audit. (Read…
  2. Render the pages. For each priority URL, browser/markdown + browser/html to capture the rendered title, meta, headings, body copy, and…
  3. Pull rank + competitor reality. seo/competitors/domain → who the organic competitors actually are; seo/competitors/domain-rank-overview →…
  4. Pull the authority profile. seo/backlinks/summary for the headline, then referring-domains, anchors, bulk-spam-score, and the gap pair…
  5. Audit in the fixed 5-pillar priority order (below), writing every finding in the Finding Schema. Pillar order is deliberate — an…
  6. Prioritize into the 4-tier plan. Sort every finding into Critical → High-impact → Quick wins → Long-term by impact × effort.
  7. Report & hand off. Produce the structured report (Output). Route keyword/competitor gap expansion to keyword-research and structured-data…

What it can do on your machine

Read from SKILL.md and the folder at commit fb53247. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

SEO Audit loads about 3.4k tokens when it runs, and up to ~11k if it reads all its reference files. Until then it costs about 173 tokens; SKILL.md has 1,282 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~173
When it runs · the whole SKILL.md, loaded when a task matches
~3.4k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~11k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from unifapi-agent/agents at commit fb53247, republished under its MIT licence (© unifapi-agent). 1,282 words, ~3,438 tokens.

Download SKILL.mdSave it as .claude/skills/seo-audit/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.
name
seo-audit
description
When the user wants to audit, review, or diagnose SEO issues on their site. Also use when the user mentions "SEO audit," "technical SEO," "why am I not ranking," "SEO issues," "on-page SEO," "meta tags review," "SEO health check," "my traffic dropped," "lost rankings," "not showing up in Google," "site isn't ranking," "Google update hit me," "page speed," "core web vitals," "crawl errors," "indexing issues," "backlink audit," "toxic links," or "link gap." Use this even if the user just says something vague like "my SEO is bad" or "help with SEO" — start with an audit. For keyword and competitor gaps, see the keyword-research skill. For structured data, see the schema skill.
license
MIT
metadata.author
UnifAPI
metadata.version
1.0.0
metadata.adapted_from
https://github.com/coreyhaines31/marketingskills
metadata.adapted_author
Corey Haines

SEO Audit

You are an expert in search engine optimization. Your goal is to diagnose what is holding a site back in organic search and return a prioritized fix list — every finding backed by what is actually rendered and actually ranking, not a generic checklist.

This is an enhanced skill: it reads live public data through UnifAPI. The original framework drew its data manually (Search Console, PageSpeed, Ahrefs/Semrush exports). Here every pillar is grounded in a live read — the rendered page, the real SERP, and the real backlink profile — so each finding ships with evidence, not an assumption.

Use UnifAPI for live evidence

A static web_fetch/curl cannot see JS-injected content (including JSON-LD), cannot tell you where you actually rank, and cannot see your link profile at all. Pull the real thing before judging anything. Use the unifapi skill to connect (OAuth MCP), then call the operations below, grouped by the pillar they feed. Pass location + language consistently so every metric is comparable.

  • Crawl & on-page reality (Pillars 1–3) — browser/markdown and browser/html render the JS page so you read the actual title, headings, meta, copy, and JS-injected JSON-LD; browser/links returns the internal-link graph (orphans, depth, anchor text).
  • Rank reality (Pillars 3–4) — seo/serp gives live organic positions, target visibility, and the SERP features each query triggers; seo/competitors/relevant-pages and seo/competitors/ranked-keywords show what the site truly ranks for (and which pages); seo/competitors/domain and seo/competitors/domain-rank-overview name the organic competitors and their traffic.
  • On-page targeting (Pillar 3) — seo/keywords/overview (volume/CPC/competition/KD) and seo/keywords/intent confirm whether a page targets a real query with matching intent, or is mis-aimed.
  • Authority & links (Pillar 5 — the originally-manual pillar, now live) — seo/backlinks/summary (domain rank, referring domains, backlink count), seo/backlinks/referring-domains, seo/backlinks/bulk-spam-score (toxic flag), seo/backlinks/anchors (over-optimization / unnatural anchor mix), seo/backlinks/competitors and seo/backlinks/domain-intersection (link-gap / outreach list), and seo/backlinks/history (link-velocity trend, useful after a traffic drop).

UnifAPI reads public data only — it never changes the site or touches Search Console. Report fixes; the operator's own assistant makes the changes. Keep each response's billing block so the report can state record cost.

Workflow

  1. Scope. Confirm the site, the priority keywords, the named competitors, and whether this is a full-site or single-page audit. (Read .agents/product-marketing.md / .claude/product-marketing.md / legacy product-marketing-context.md first if present, and only ask for what it doesn't cover.) If a traffic drop is the trigger, set a before/after window and plan to lean on seo/backlinks/history and seo/competitors/historical-rank-overview.
  2. Render the pages. For each priority URL, browser/markdown + browser/html to capture the rendered title, meta, headings, body copy, and JSON-LD; browser/links for the internal-link graph. This is the raw material for Pillars 1–3 — never judge on-page from static HTML.
  3. Pull rank + competitor reality. seo/competitors/domain → who the organic competitors actually are; seo/competitors/domain-rank-overview → their traffic vs the target; seo/competitors/relevant-pages + seo/competitors/ranked-keywords → what the site ranks for today; seo/serp on each priority query → live position, target visibility, and SERP features. Tie every "you're not ranking" claim to a seo/serp record and name who beats the page.
  4. Pull the authority profile. seo/backlinks/summary for the headline, then referring-domains, anchors, bulk-spam-score, and the gap pair (competitors + domain-intersection). This turns the old manual link pillar into evidence: real referring-domain count, toxic-link flag, anchor over-optimization, and a concrete outreach/link-gap list.
  5. Audit in the fixed 5-pillar priority order (below), writing every finding in the Finding Schema. Pillar order is deliberate — an indexation block makes on-page polish irrelevant, so never reorder. Load the long per-pillar checklists from references/pillar-checklists.md; load references/international-seo.md when the site is multi-locale.
  6. Prioritize into the 4-tier plan. Sort every finding into Critical → High-impact → Quick wins → Long-term by impact × effort.
  7. Report & hand off. Produce the structured report (Output). Route keyword/competitor gap expansion to keyword-research and structured-data fixes to schema.

The 5 Pillars (audit in this priority order)

Audit top-down; a failure in an earlier pillar usually outranks anything below it.

  1. Crawlability & Indexation — Can Google find and index it? robots.txt, XML sitemap, canonicalization, noindex, redirect chains, orphan pages. Evidence: browser/links (orphans, depth), browser/html (canonical/robots meta as rendered), seo/serp for site: reality.
  2. Technical Foundations — Is the site fast and functional? Core Web Vitals (LCP/INP/CLS), HTTPS, mobile-friendliness, URL structure. Use PageSpeed Insights / Search Console for vitals; confirm the rendered page with browser/markdown.
  3. On-Page Optimization — Is the content targeted correctly? Title/meta/H1, heading hierarchy, keyword targeting, cannibalization, internal-link anchors. Evidence: browser/html/browser/markdown (what's actually on the page), seo/keywords/overview + seo/keywords/intent (is the target query real and intent-matched), seo/serp (is the page even visible).
  4. Content Quality — Does it deserve to rank? E-E-A-T signals, depth vs the pages that beat it, freshness. Evidence: seo/competitors/relevant-pages + the live seo/serp page-1 set (compare the target against what actually wins). See references/ai-writing-detection.md to flag low-effort AI copy that erodes quality signals.
  5. Authority & Links — Does it have credibility? Referring-domain count and quality, toxic links, anchor distribution, link gap vs competitors, link velocity. Evidence: seo/backlinks/summary, referring-domains, bulk-spam-score, anchors, competitors, domain-intersection, history.
Show full SKILL.md (485 more words)Show less

Finding Schema

Write every finding in this exact shape so the operator can triage fast:

text
Issue:    <what is wrong, one line>
Impact:   High | Medium | Low   (effect on rankings/traffic)
Evidence: <the live read — name the op + value, e.g. "seo/serp 2026-06-04: target absent, page 1 = g2.com, dev.to" or "browser/html: no <h1>; canonical points to /home">
Fix:      <specific, actionable recommendation>
Priority: 1–5   (1 = do first)

The Evidence line is the enhancement: it must cite the live source (operation + observed value + run date), never "best practice says." A finding without evidence is a guess — drop it or go pull the read.

International SEO & hreflang

When the site serves multiple languages or regions, misconfigured hreflang, cross-locale canonicals, or thin locale pages can suppress whole locale variants and drag down site-wide quality signals (Helpful Content is a site-wide signal). Render a sample of locale pages with browser/html to confirm hreflang reciprocity, lang, and canonical direction as actually served. The full checklist — hreflang placement & reciprocity, multilingual canonicalization, international sitemaps, locale URL structure, and content quality across locales — with evidence and source URLs is in references/international-seo.md. Load it whenever the site is multi-locale.

Common Issues by Site Type

Bias the audit toward the failure modes typical of the site type:

  • SaaS / product — thin feature pages; blog disconnected from product pages; missing comparison/alternative pages; no glossary/educational layer. (Confirm depth gaps with seo/competitors/relevant-pages.)
  • E-commerce — thin category pages; duplicated product descriptions; missing Product schema; faceted-nav duplicate URLs; mishandled out-of-stock pages.
  • Content / blog — stale unrefreshed content; keyword cannibalization (two pages targeting one query in seo/serp); no topical clustering; weak internal linking (browser/links); missing author pages (E-E-A-T).
  • Multilingual / multi-regional — hreflang return-tag/self-reference errors; canonical conflicting with hreflang; thin boilerplate-only locale pages; no x-default. See the international reference.
  • Local business — inconsistent NAP; missing LocalBusiness schema; no Google Business Profile optimization; missing location pages.

Output: SEO Audit Report

markdown
# SEO Audit — {domain} ({YYYY-MM-DD})

## Executive Summary

- Overall health: {1-line verdict}
- Top 3–5 priority issues: {…}
- Quick wins available: {n}
- Organic standing: {from seo/competitors/domain-rank-overview — traffic vs {competitor}}
- Authority standing: {from seo/backlinks/summary — domain rank, {n} referring domains, {n} toxic-flagged}

## Findings by Pillar

### 1. Crawlability & Indexation

| Issue                                   | Impact | Evidence (op + value, dated)                            | Fix                   | Priority |
| --------------------------------------- | ------ | ------------------------------------------------------- | --------------------- | -------- |
| No XML sitemap referenced in robots.txt | High   | browser/html 2026-06-04: robots.txt has no Sitemap line | Add sitemap directive | 1        |

### 2. Technical Foundations

### 3. On-Page Optimization

### 4. Content Quality

### 5. Authority & Links

| Issue                                                     | Impact | Evidence (op + value, dated)                          | Fix                              | Priority |
| --------------------------------------------------------- | ------ | ----------------------------------------------------- | -------------------------------- | -------- |
| 18% of referring domains spam-flagged                     | High   | seo/backlinks/bulk-spam-score 2026-06-04: 41/228 ≥ 60 | Disavow review; audit anchor mix | 2        |
| Link gap: 12 domains link to both competitors, none to us | Medium | seo/backlinks/domain-intersection 2026-06-04          | Outreach list (attached)         | 3        |

## Prioritized Action Plan

1. **Critical** — blocking indexation/ranking (fix now)
2. **High-impact** — material ranking lift, moderate effort
3. **Quick wins** — easy, immediate benefit (often striking-distance pages from seo/serp)
4. **Long-term** — content builds, authority/link campaigns, locale work

## Cost

UnifAPI records consumed: {from billing}, or best estimate.

Guardrails

  • Read-only ("eyes, not hands"): this skill diagnoses and recommends. It never edits the site, submits to Search Console, disavows links, or touches any account — the operator's own assistant executes every fix.
  • Confirmed vs inferred: label what was read off a live page/SERP/backlink profile (cite the op + value) versus what was deduced. Never report "no schema found" or "not ranking" from static HTML — render with browser/html/browser/markdown and check seo/serp first.
  • Dated snapshots: SERPs, vitals, and link profiles move. Stamp every reading with its run date and re-pull before a big remediation.
  • Don't promise rankings. A fix is a prioritized bet backed by evidence, not a guarantee.

References

  • keyword-research (SEO Agent): keyword and competitor-gap expansion from live SERP + volume data — run after scoping the audit to turn gaps into a target list.
  • schema (SEO Agent): implement the structured data this audit flags as missing or broken.
  • ai-seo (AI Visibility Agent): when the question is AI Overviews / ChatGPT citations rather than classic organic rank.
  • unifapi: the shared data skill — connect MCP and discover the SERP, browser, and backlink operations this audit reads.

© unifapi-agent, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 4 other files (references) in skills/seo-agent/seo-audit of unifapi-agent/agents.

  • SKILL.md
  • README.md
  • references/ai-writing-detection.md
  • references/international-seo.md
  • references/pillar-checklists.md

Open the folder on GitHubat commit fb53247

Compare with similar skills

SEO Audit next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

SEO Audit compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
SEO Audit this skillunifapi-agent/agents589—~3.4kAutomated safety check: PassMIT
Tech SEO Auditindranilbanerjee/digital-marketing-pro8591 repos~2.2kAutomated safety check: PassMIT
SEO Auditjosstei/maestro-orchestrate465—~218Automated safety check: PassApache-2.0
SEO Audittextura-agency/next16-claude-starter133—~2.2kAutomated safety check: NotesUnlicense
Site ArchitectureAvdLee/RocketSimApp80411 repos~3.3kAutomated safety check: PassCustom licence
SEO Optimizerailabs-393/ai-labs-claude-skills4541 repos~3.2kAutomated safety check: PassMIT

Similar skills

  • Tech SEO Audit

    indranilbanerjee/digital-marketing-pro

    Run a technical SEO audit of a site — crawlability, indexation, Core Web Vitals, redirects, structured data, mobile, security — and produce a severity-ranked report with specific fixes, effort…

    859 GitHub starsUsed in 1 repo~2.2k tokens
    Marketing & SEOAuto-check passed
  • SEO Audit

    josstei/maestro-orchestrate

    Run a Maestro-style SEO assessment for meta tags, structured data, crawlability, and Core Web Vitals

    465 GitHub stars~218 tokensUpdated 2 days ago
    Marketing & SEOAuto-check passed
  • SEO Audit

    textura-agency/next16-claude-starter

    Audit a page or the whole site for technical and on-page SEO — crawlability, metadata, heading outline, structured data, internal linking, Core Web Vitals, and the animation-specific crawlability…

    133 GitHub stars~2.2k tokensUpdated 2 days ago
    Marketing & SEOAuto-check: notes
  • Site Architecture

    AvdLee/RocketSimApp

    When the user wants to plan, map, or restructure their website's page hierarchy, navigation, URL structure, or internal linking.

    804 GitHub starsUsed in 11 repos~3.3k tokens
    Marketing & SEOAuto-check passed
  • SEO Optimizer

    ailabs-393/ai-labs-claude-skills

    This skill should be used when analyzing HTML/CSS websites for SEO optimization, fixing SEO issues, generating SEO reports, or implementing SEO best practices.

    454 GitHub starsUsed in 1 repo~3.2k tokens
    Marketing & SEOAuto-check passed
  • SEO

    AgriciDaniel/seo-os

    Comprehensive SEO analysis for any website or business type.

    135 GitHub starsUsed in 2 repos~3.5k tokens
    Marketing & SEOAuto-check passed

More from unifapi-agent/agents

All 47 skills in this repo
  • LLM Mention Tracking

    unifapi-agent/agents

    When the user wants to track how often their brand or domain gets mentioned across ChatGPT and AI search engines over a set of prompts, and how that share of voice compares to named competitors over…

    589 GitHub stars~1.8k tokensUpdated 1 mo ago
    Auto-check passed
  • Buying Signal Monitor

    unifapi-agent/agents

    When a seller or SDR wants to catch public buying intent on X/Twitter and LinkedIn — someone asking for a tool they sell, complaining about or switching off a competitor, or hiring for a role that…

    589 GitHub stars~2.4k tokensUpdated 1 mo ago
    Auto-check passed
  • Customer Research

    unifapi-agent/agents

    When the user wants to research customers from public communities, or synthesize customer language, pains, and objections.

    589 GitHub stars~2.1k tokensUpdated 1 mo ago
    Auto-check passed
  • Keyword Research

    unifapi-agent/agents

    When the user wants to research keywords, find keyword opportunities, run a keyword gap analysis, build topic clusters, or compare what competitors rank for.

    589 GitHub stars~2.7k tokensUpdated 1 mo ago
    Auto-check passed
  • Schema

    unifapi-agent/agents

    When the user wants to add, fix, or optimize schema markup and structured data on their site.

    589 GitHub stars~2.1k tokensUpdated 1 mo ago
    Auto-check passed
  • Unifapi

    unifapi-agent/agents

    A skill your agent uses when working with UnifAPI public-data APIs or the UnifAPI MCP server: connecting OAuth MCP clients, discovering operations, calling social/search/scrape/news APIs…

    589 GitHub stars~741 tokensUpdated 1 mo ago
    Auto-check passed

Categories

Questions about SEO Audit

What does SEO Audit do?

When the user wants to audit, review, or diagnose SEO issues on their site. SEO Audit is an agent skill from unifapi-agent/agents. When the user wants to audit, review, or diagnose SEO issues on their site.

When should I use SEO Audit?

SEO Audit fits situations like: diagnose SEO issues on their site; the user mentions SEO audit; why am I not ranking; meta tags review.

How do I install SEO Audit in Claude Code?

Run `npx skills add unifapi-agent/agents --skill seo-audit -a claude-code`. Or copy the skill folder (skills/seo-agent/seo-audit in unifapi-agent/agents) into .claude/skills/seo-audit in your project. Claude Code loads it when a task matches its description.

How do I install SEO Audit in Codex?

Run `npx skills add unifapi-agent/agents --skill seo-audit -a codex`. Or copy the skill folder (skills/seo-agent/seo-audit in unifapi-agent/agents) into .agents/skills/seo-audit in your project. Codex loads it when a task matches its description.

Can I use SEO Audit in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add unifapi-agent/agents --skill seo-audit -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/seo-audit, .gemini/skills/seo-audit, .github/skills/seo-audit and .opencode/skills/seo-audit in your project.

What does SEO Audit need to run?

SKILL.md names no scripts, command-line tools or credentials: SEO Audit is instructions for the agent only.

Does SEO Audit access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is SEO Audit safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does SEO Audit use?

SEO Audit is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does SEO Audit use?

About 3.4k tokens (SKILL.md is roughly 14k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 7.6k tokens, read only when the agent opens those files.

What are the alternatives to SEO Audit?

Skills that share tags, products or a category with SEO Audit: Tech SEO Audit (indranilbanerjee/digital-marketing-pro, 859 stars), SEO Audit (josstei/maestro-orchestrate, 465 stars), SEO Audit (textura-agency/next16-claude-starter, 133 stars) and Site Architecture (AvdLee/RocketSimApp, 804 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains SEO Audit?

unifapi-agent (a GitHub organization) maintains it in unifapi-agent/agents, which has 589 GitHub stars. The repository holds 47 skills in this directory. The repository was last updated on September 5, 2026.

Source: unifapi-agent/agents on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.