Agent Browser CLI
vercel-labs/agent-browser
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking…
Format and deliver network alerts, health warnings, and critical notifications via Slack with rich formatting, reactions, and file attachments.
Apache-2.0Auto-check passed
Install Slack Network Alerts
$ npx skills add automateyournetwork/netclaw --skill slack-network-alerts -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install automateyournetwork/netclaw slack-network-alerts --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/automateyournetwork/netclaw.git skills-src && mkdir -p .claude/skills && cp -r skills-src/workspace/skills/slack-network-alerts .claude/skills/slack-network-alerts && rm -rf skills-srcUse ~/.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/
Install the "slack-network-alerts" agent skill from https://github.com/automateyournetwork/netclaw/tree/main/workspace/skills/slack-network-alerts into .claude/skills/slack-network-alerts/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "slack-network-alerts", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/automateyournetwork/netclaw/tree/main/workspace/skills/slack-network-alertsType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add automateyournetwork/netclaw --skill slack-network-alerts -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install automateyournetwork/netclaw slack-network-alerts --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/automateyournetwork/netclaw.git skills-src && mkdir -p .agents/skills && cp -r skills-src/workspace/skills/slack-network-alerts .agents/skills/slack-network-alerts && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "slack-network-alerts" agent skill from https://github.com/automateyournetwork/netclaw/tree/main/workspace/skills/slack-network-alerts into .agents/skills/slack-network-alerts/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "slack-network-alerts", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add automateyournetwork/netclaw --skill slack-network-alerts -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install automateyournetwork/netclaw slack-network-alerts --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/automateyournetwork/netclaw.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/workspace/skills/slack-network-alerts .cursor/skills/slack-network-alerts && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "slack-network-alerts" agent skill from https://github.com/automateyournetwork/netclaw/tree/main/workspace/skills/slack-network-alerts into .cursor/skills/slack-network-alerts/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "slack-network-alerts", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/automateyournetwork/netclaw.git --path workspace/skills/slack-network-alerts--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add automateyournetwork/netclaw --skill slack-network-alerts -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install automateyournetwork/netclaw slack-network-alerts --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/automateyournetwork/netclaw.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/workspace/skills/slack-network-alerts .gemini/skills/slack-network-alerts && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "slack-network-alerts" agent skill from https://github.com/automateyournetwork/netclaw/tree/main/workspace/skills/slack-network-alerts into .gemini/skills/slack-network-alerts/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "slack-network-alerts", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install automateyournetwork/netclaw slack-network-alertsInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add automateyournetwork/netclaw --skill slack-network-alerts -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/automateyournetwork/netclaw.git skills-src && mkdir -p .github/skills && cp -r skills-src/workspace/skills/slack-network-alerts .github/skills/slack-network-alerts && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "slack-network-alerts" agent skill from https://github.com/automateyournetwork/netclaw/tree/main/workspace/skills/slack-network-alerts into .github/skills/slack-network-alerts/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "slack-network-alerts", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add automateyournetwork/netclaw --skill slack-network-alerts -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install automateyournetwork/netclaw slack-network-alerts --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/automateyournetwork/netclaw.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/workspace/skills/slack-network-alerts .opencode/skills/slack-network-alerts && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "slack-network-alerts" agent skill from https://github.com/automateyournetwork/netclaw/tree/main/workspace/skills/slack-network-alerts into .opencode/skills/slack-network-alerts/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "slack-network-alerts", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
slack-network-alerts- GitHub stars
- 676
- Token cost
- ~1.8k tokens
- SKILL.md length
- 491 words
- Files
- 1
- Skills in repo
- 120
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Format and deliver network alerts, health warnings, and critical notifications via Slack with rich formatting, reactions, and file attachments.
- Works in 6 steps: Run the full health check procedure → Determine overall severity (CRITICAL >… → Format the alert using the appropriate… → …
- Sending alerts to Slack
- SKILL.md covers Slack OAuth Scopes Used, Alert Severity Formatting, Alert Workflows and Reaction-Based Acknowledgment, plus 5 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Slack Network Alerts is an agent skill from automateyournetwork/netclaw. Format and deliver network alerts, health warnings, and critical notifications via Slack with rich formatting, reactions, and file attachments. Use when sending alerts to Slack, posting health check results, notifying the team about a device issue, or formatting network status updates for a channel.
Its SKILL.md is about 1.8k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It works with Slack. The repository describes itself as: An AI agent that claws through your network. The licence is Apache-2.0.
When your agent uses it
- Sending alerts to Slack
- Posting health check results
- Notifying the team about a device issue
- Formatting network status updates for a channel
Example prompts
- “/slack-network-alerts”
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- Run the full health check procedure
- Determine overall severity (CRITICAL > HIGH > WARNING > HEALTHY)
- Format the alert using the appropriate severity template above
- Post to the network operations channel
- If CRITICAL or HIGH, add :rotating_light: or :warning: reaction to the message
- If CRITICAL, start a thread with detailed diagnostics
What it can do on your machine
Read from SKILL.md and the folder at commit aa90e7d. 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.
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
Slack Network Alerts loads about 1.8k tokens when it runs. Until then it costs about 80 tokens; SKILL.md has 491 words of instructions outside code blocks.
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 automateyournetwork/netclaw at commit aa90e7d, republished under its Apache-2.0 licence (© automateyournetwork). 491 words, ~1,756 tokens.
Download SKILL.mdSave it as
.claude/skills/slack-network-alerts/SKILL.md (or your agent's skills folder).- name
- slack-network-alerts
- description
- Format and deliver network alerts, health warnings, and critical notifications via Slack with rich formatting, reactions, and file attachments. Use when sending alerts to Slack, posting health check results, notifying the team about a device issue, or formatting network status updates for a channel.
- license
- Apache-2.0
- user-invocable
- true
Slack Network Alerts
Slack OAuth Scopes Used
| Scope | Purpose |
|---|---|
chat:write | Post alert messages to channels |
chat:write.customize | Post with custom username/avatar per alert severity |
reactions:write | Add emoji reactions to acknowledge/track alerts |
files:write | Attach diagrams, reports, and log excerpts |
app_mentions:read | Respond when users @mention NetClaw |
channels:join | Join alert channels automatically |
Alert Severity Formatting
Use Slack Block Kit formatting to visually distinguish severity levels.
CRITICAL Alert Format
:rotating_light: *CRITICAL — Device Unreachable*
*Device:* R1 (10.1.1.1)
*Detected:* 2024-02-21 14:32 UTC
*Impact:* 47 downstream routes affected, 3 OSPF adjacencies lost
*Symptoms:*
• Ping 0% success (was 100%)
• OSPF neighbor state: DOWN
• BGP peer 10.1.1.2: IDLE
*Recommended Action:*
1. Check physical connectivity / power
2. Verify interface status on upstream device
3. Check for reload reason if device recovers
_Thread for investigation updates →_HIGH Alert Format
:warning: *HIGH — Interface Flapping*
*Device:* SW1 | *Interface:* Gi1/0/24
*Flap Count:* 12 in last 30 minutes
*Connected To:* R2:Gi0/0/1 (discovered via CDP)
*Action Required:* Investigate physical layer — CRC errors detected (47 in 5 min)WARNING Alert Format
:large_yellow_circle: *WARNING — Memory Pressure*
*Device:* R2 | *Memory:* 82% used (2.1G / 2.6G)
*Trend:* Increased from 71% over 24h
*Top Consumer:* BGP Router (843 MB)
_Monitor — no immediate action required_INFORMATIONAL Alert Format
:information_source: *INFO — Configuration Change Detected*
*Device:* R1 | *User:* admin (10.0.0.50)
*Time:* 2024-02-21 09:15 UTC
*Change:* 3 lines modified in running-config
_Captured in GAIT session abc123_Alert Workflows
Health Check Alert Flow
After running a health check (pyats-health-check skill), post results to the designated channel:
- Run the full health check procedure
- Determine overall severity (CRITICAL > HIGH > WARNING > HEALTHY)
- Format the alert using the appropriate severity template above
- Post to the network operations channel
- If CRITICAL or HIGH, add :rotating_light: or :warning: reaction to the message
- If CRITICAL, start a thread with detailed diagnostics
Threshold-Triggered Alerts
When any health check metric exceeds thresholds:
| Metric | WARNING | HIGH | CRITICAL |
|---|---|---|---|
| CPU 5min avg | > 50% | > 75% | > 90% |
| Memory used | > 70% | > 85% | > 95% |
| Interface errors | > 0 CRC | > 100/min | Resets incrementing |
| Packet loss | > 0% | > 5% | > 20% |
| NTP offset | > 100ms | > 500ms | > 1s or unsync |
| BGP peer | Flapping | 1 peer down | Multiple peers down |
| OSPF adjacency | Flapping | 1 adj lost | Area partition |
Multi-Device Fleet Alert Summary
After a fleet-wide health check, post a single summary:
:bar_chart: *Fleet Health Summary — 2024-02-21 14:00 UTC*
*Devices Checked:* 8 | :red_circle: 1 CRITICAL | :warning: 2 HIGH | :large_yellow_circle: 3 WARNING | :white_check_mark: 2 HEALTHY
┌──────────┬──────────┬──────┬────────┬──────────┬─────────────┐
│ Device │ CPU │ Mem │ Intf │ NTP │ Overall │
├──────────┼──────────┼──────┼────────┼──────────┼─────────────┤
│ R1 │ :white_check_mark: 12% │ :warning: 78%│ :white_check_mark: │ :white_check_mark: │ :warning: WARNING │
│ R2 │ :white_check_mark: 8% │ :white_check_mark: 45%│ :red_circle: Gi2 │ :white_check_mark: │ :red_circle: CRITICAL │
│ SW1 │ :warning: 67% │ :white_check_mark: 52%│ :white_check_mark: │ :red_circle: unsync │ :red_circle: HIGH │
└──────────┴──────────┴──────┴────────┴──────────┴─────────────┘
_Details in thread →_Security Alert Flow
After a security audit (pyats-security skill), post findings:
:shield: *Security Audit — R1*
*Findings:* 2 CRITICAL | 2 HIGH | 3 MEDIUM | 1 LOW
:red_circle: *CRITICAL:*
• [C-001] SSHv1 enabled — MITM vulnerability
• [C-002] No VTY access-class — management plane exposed
:warning: *HIGH:*
• [H-001] No OSPF authentication on Gi1
• [H-002] SNMP community 'public' with no ACL
_Full report attached as file →_Reaction-Based Acknowledgment
Use emoji reactions to track alert status:
| Reaction | Meaning |
|---|---|
| :eyes: | Alert acknowledged — someone is looking |
| :wrench: | Fix in progress |
| :white_check_mark: | Resolved |
| :no_entry: | False positive / suppressed |
| :hourglass: | Waiting on change window |
| :busts_in_silhouette: | Escalated to team |
When a user reacts with :eyes: on an alert, NetClaw can respond in the thread:
Acknowledged by @engineer1 at 14:35 UTC. Tracking in thread.Show full SKILL.md (210 more words)Show less
File Attachments
Attach supporting data as Slack files:
- Topology diagrams — Draw.io PNG/SVG after topology discovery
- Health reports — Full text report as .txt attachment
- Config diffs — Pre/post change diffs
- Log excerpts — Relevant log sections for investigation
- Markmap mind maps — Protocol hierarchy visualizations
Channel Strategy
| Channel | Purpose | Alert Types |
|---|---|---|
| #netclaw-alerts | Critical/High alerts only | Device down, security critical |
| #netclaw-reports | Scheduled reports | Health checks, audits, reconciliation |
| #netclaw-changes | Change notifications | Config changes, CR updates |
| #netclaw-general | General interaction | Ad-hoc queries, help |
Message Threading
- Always thread follow-up investigation steps under the original alert
- Post the initial alert as a top-level message
- Post diagnostics, show command outputs, and resolution steps as thread replies
- Post final resolution summary as both a thread reply and a top-level message
Integration with GAIT
Every alert should reference the GAIT session:
:information_source: _Tracked in GAIT session `abc123` — commit `def456`_Failure Behavior
- On a tool error (timeout, unreachable host, malformed response), report the failure and its error message directly to the user rather than fabricating or guessing at results.
- For a confirmed read-only call, check connectivity and retry once if appropriate. For any call that changes state or sends a message, a timeout does not prove the action failed: inspect current state or delivery status before retrying, preserve the required approval/change gates, and do not repeat an action whose outcome is unknown.
© automateyournetwork, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in workspace/skills/slack-network-alerts of automateyournetwork/netclaw.
Open the folder on GitHubat commit aa90e7d
Compare with similar skills
Slack Network Alerts 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Slack Network Alerts this skillautomateyournetwork/netclaw | 676 | — | ~1.8k | Automated safety check: Pass | Apache-2.0 | |
| Agent Browser CLIvercel-labs/agent-browser | 44k | 24 repos | ~864 | Automated safety check: Pass | Apache-2.0 | |
| Slack GIF Creatoranthropics/skills | 180k | 29 repos | ~2k | Automated safety check: Pass | Apache-2.0 | |
| Code Design Rationale Investigatorcursor/plugins | 11k | 9 repos | ~2.6k | Automated safety check: Pass | None | |
| Electron App Automationvercel-labs/agent-browser | 44k | 5 repos | ~1.7k | Automated safety check: Pass | Apache-2.0 | |
| Slack Browser Automationvercel-labs/agent-browser | 44k | 1 repos | ~2.1k | Automated safety check: Pass | Apache-2.0 |
Similar skills
- Official
- Official
Slack GIF Creator
anthropics/skills
Provides Slack size and frame limits, Python animation helpers and validators for building animated GIFs sized for emoji and messages.
- Official
Code Design Rationale Investigator
cursor/plugins
Digs into why code is shaped the way it is by checking git history, pull requests and connected tools in parallel, then reporting a cited read on the tradeoffs.
- Official
Electron App Automation
vercel-labs/agent-browser
Automates Electron desktop apps such as VS Code, Slack or Discord by connecting agent-browser to their Chrome DevTools Protocol port.
- Official
Slack Browser Automation
vercel-labs/agent-browser
Drives the Slack web app with the agent-browser CLI to check unread channels, search, read channel details and extract information, with screenshots as evidence.
Composio
ComposioHQ/composio
Route and complete Composio work across Composio For You and Composio Platform.
More from automateyournetwork/netclaw
All 120 skills in this repoEVE-NG Lab Topology Design
automateyournetwork/netclaw
Entry point for designing EVE-NG network labs: classifies the request, gathers missing requirements, proposes options and validates the resulting topology.
ACI Policy Change Deployment
automateyournetwork/netclaw
Deploys Cisco ACI policy changes only behind an approved ServiceNow Change Request, capturing pre and post-change fault baselines and rolling back automatically on a fault delta.
Cisco ACI Fabric Health Audit
automateyournetwork/netclaw
Runs a phased health audit of a Cisco ACI fabric through MCP tools: node status, links, tenant and policy review, faults and endpoint learning.
Anta Validation
automateyournetwork/netclaw
Validate Arista EOS network state against ANTA's pre-built 208-test catalogue, with structured pass/fail verdicts.
Arista Cvp
automateyournetwork/netclaw
Arista CloudVision Portal (CVP) automation via REST API — device inventory, events, connectivity monitoring, tag management (4 tools).
AWS Cloud Monitoring
automateyournetwork/netclaw
AWS CloudWatch monitoring — metrics, alarms, log queries, VPC flow log analysis, network performance.
Related
Works with
Questions about Slack Network Alerts
What does Slack Network Alerts do?
Format and deliver network alerts, health warnings, and critical notifications via Slack with rich formatting, reactions, and file attachments. Slack Network Alerts is an agent skill from automateyournetwork/netclaw. Format and deliver network alerts, health warnings, and critical notifications via Slack with rich formatting, reactions, and file attachments.
When should I use Slack Network Alerts?
Slack Network Alerts fits situations like: sending alerts to Slack; posting health check results; notifying the team about a device issue; formatting network status updates for a channel.
How do I install Slack Network Alerts in Claude Code?
Run `npx skills add automateyournetwork/netclaw --skill slack-network-alerts -a claude-code`. Or copy the skill folder (workspace/skills/slack-network-alerts in automateyournetwork/netclaw) into .claude/skills/slack-network-alerts in your project. Claude Code loads it when a task matches its description.
How do I install Slack Network Alerts in Codex?
Run `npx skills add automateyournetwork/netclaw --skill slack-network-alerts -a codex`. Or copy the skill folder (workspace/skills/slack-network-alerts in automateyournetwork/netclaw) into .agents/skills/slack-network-alerts in your project. Codex loads it when a task matches its description.
Can I use Slack Network Alerts 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 automateyournetwork/netclaw --skill slack-network-alerts -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/slack-network-alerts, .gemini/skills/slack-network-alerts, .github/skills/slack-network-alerts and .opencode/skills/slack-network-alerts in your project.
What does Slack Network Alerts need to run?
SKILL.md names no scripts, command-line tools or credentials: Slack Network Alerts is instructions for the agent only.
Does Slack Network Alerts 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 Slack Network Alerts 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 Slack Network Alerts use?
Slack Network Alerts is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Slack Network Alerts use?
About 1.8k tokens (SKILL.md is roughly 7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Slack Network Alerts?
Skills that share tags, products or a category with Slack Network Alerts: Agent Browser CLI (vercel-labs/agent-browser, 44k stars), Slack GIF Creator (anthropics/skills, 180k stars), Code Design Rationale Investigator (cursor/plugins, 11k stars) and Electron App Automation (vercel-labs/agent-browser, 44k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Slack Network Alerts?
automateyournetwork (a GitHub user) maintains it in automateyournetwork/netclaw, which has 676 GitHub stars. The repository holds 120 skills in this directory. The repository was last updated on October 9, 2026.
Source: automateyournetwork/netclaw on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.