New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Sealos Deploy

by hashgraph-online in hashgraph-online/awesome-codex-plugins

Brain managed-mode deploy executor for Sealos Cloud. An agent skill from hashgraph-online/awesome-codex-plugins.

Apache-2.0Auto-check passedDevOps & Cloud

Install Sealos Deploy

skills CLI
$ npx skills add hashgraph-online/awesome-codex-plugins --skill sealos-deploy -a claude-code

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

GitHub CLI
$ gh skill install hashgraph-online/awesome-codex-plugins sealos-deploy --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/hashgraph-online/awesome-codex-plugins.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/labring/sealos-skills/plugins/sealos/skills/sealos-deploy .claude/skills/sealos-deploy && 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
sealos-deploy
GitHub stars
1.2k
Token cost
~2.8k tokens
SKILL.md length
1,125 words
Files
1
Skills in repo
686
Repo updated
First seen
Licence
Apache-2.0

At a glance

Brain managed-mode deploy executor for Sealos Cloud. An agent skill from hashgraph-online/awesome-codex-plugins.

  • Works in 6 steps: Classify → Build (source path only) → Template at the fixed path → …
  • SEALAIDEPLOYMODE=managed (a Brain Devbox sandbox)
  • SKILL.md covers Mode gate, Environment, Pipeline and Routing
  • Calls python3, kubectl and bash; needs GITHUB_TOKEN and SEALAI_DEPLOY_MCP_TOKEN

What it does

Sealos Deploy is an agent skill from hashgraph-online/awesome-codex-plugins. Brain managed-mode deploy executor for Sealos Cloud. Use when SEALAIDEPLOYMODE=managed (a Brain Devbox sandbox) or when the task says to run /sealos-deploy: deploy the workspace repository to Sealos through the MCP-gated managed pipeline — classify, build via Kaniko if needed, generate the canonical template, hand off through templateready / deploymentcompleted, and verify. Outside managed mode, use the use-sealos skill instead.

Its SKILL.md is about 2.8k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in DevOps & Cloud, covering Deployment. It works with Model Context Protocol. The repository describes itself as: A curated list of awesome OpenAI Codex / ChatGPT plugins, skills, and resources. The 1 Codex Marketplace. See live plugins at: https://hol.org/plugins/best-codex-plugins. The licence is Apache-2.0.

When your agent uses it

  • SEALAIDEPLOYMODE=managed (a Brain Devbox sandbox)
  • The task says to run /sealos-deploy: deploy the workspace repository to Sealos through the MCP-gated managed pipeline — classify
  • Build via Kaniko if needed
  • Generate the canonical template

Example prompts

  • “/sealos-deploy”

Requirements

  • Python 3
  • Docker
  • A credential in GITHUB_TOKEN
  • A credential in SEALAI_DEPLOY_MCP_TOKEN
  • Pre-approved tools (allowed-tools): Bash(kubectl:*), Bash(python3:*), Bash(curl:*), Bash(bash:*), Bash(git:*), Bash(tar:*), Bash(sha256sum:*), Bash(command:*)

Workflow steps

6 steps, taken from the step headings in SKILL.md.

  1. Classify
  2. Build (source path only)
  3. Template at the fixed path
  4. Handshake: template_ready
  5. Deploy
  6. Verify, then deployment_completed

What it can do on your machine

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

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Bash(kubectl:*)
    • Bash(python3:*)
    • Bash(curl:*)
    • Bash(bash:*)
    • Bash(git:*)
    • Bash(tar:*)
    • Bash(sha256sum:*)
    • Bash(command:*)

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • python3
    • kubectl
    • bash

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

  • Network

    No URLs in SKILL.md. Its commands use kubectl, which can reach the network depending on how they are called.

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

  • Credentials

    Names these keys or tokens, usually read from environment variables:

    • GITHUB_TOKEN
    • SEALAI_DEPLOY_MCP_TOKEN

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

Context cost

Sealos Deploy loads about 2.8k tokens when it runs. Until then it costs about 113 tokens; SKILL.md has 1,125 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~113
When it runs · the whole SKILL.md, loaded when a task matches
~2.8k

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 hashgraph-online/awesome-codex-plugins at commit 78497e5, republished under its Apache-2.0 licence (© hashgraph-online). 1,125 words, ~2,797 tokens.

Download SKILL.mdSave it as .claude/skills/sealos-deploy/SKILL.md (or your agent's skills folder).
name
sealos-deploy
description
Brain managed-mode deploy executor for Sealos Cloud. Use when SEALAI_DEPLOY_MODE=managed (a Brain Devbox sandbox) or when the task says to run /sealos-deploy: deploy the workspace repository to Sealos through the MCP-gated managed pipeline — classify, build via Kaniko if needed, generate the canonical template, hand off through template_ready / deployment_completed, and verify. Outside managed mode, use the use-sealos skill instead.
allowed-tools
Bash(kubectl:*), Bash(python3:*), Bash(curl:*), Bash(bash:*), Bash(git:*), Bash(tar:*), Bash(sha256sum:*), Bash(command:*)

Sealos Deploy (Brain Managed Mode)

Executor half of a two-party contract: this agent analyzes, builds, deploys, verifies, and repairs inside the sandbox; Brain (the control plane) renders input forms and gates completion through exactly two MCP tools. Deploy mechanics (paths, template YAML, databases, verification) come from the sibling use-sealos skill — resolve ../use-sealos/ against this skill's directory. This file owns only the managed-mode differences.

Mode gate

Run this flow only when SEALAI_DEPLOY_MODE is exactly managed. Otherwise follow ../use-sealos/SKILL.md (interactive local path) and ignore the rest of this file.

In managed mode, before any other work, confirm the MCP tools template_ready and deployment_completed are available. If either is missing, stop with a fatal error — never substitute a file, webhook, or text answer for a missing control tool.

Environment

Brain injects (read these; never enumerate the whole environment):

VariableMeaning
SEALAI_DEPLOY_WORKSPACEproject root, /home/devbox/project
SEALAI_NAMESPACEtarget namespace (also SEALAI_DEPLOY_NAMESPACE)
KUBECONFIGinjected namespace-scoped kubeconfig — use as-is
SEALAI_INPUTS_PATHfixed user-input file, exists only after the user submits the form
SEALAI_DEPLOY_LABELS_JSONplatform ownership labels — forwarded verbatim, see Deploy
SEALAI_TURN_DEADLINE_ATthe only hard time limit
GITHUB_TOKENsource builds and private-image pull secrets

Hard rules (they override the use-sealos execution rules where they differ):

  1. Never run sealos-api.py login, OAuth, or switch. The injected kubeconfig is the only credential; sealos-api.py and wait-app.sh pick it up from KUBECONFIG automatically.
  2. Fully non-interactive. Never ask the user in the agent turn — values only the user knows are declared as template inputs and collected by Brain's form. The managed deployment request authorizes non-destructive mutations in the selected namespace. Before deleting a resource or changing public access, require explicit authorization in the task or a Brain-collected input. If authorization is missing, stop without that mutation and report the blocked action to the control plane.
  3. Never print or log SEALAI_DEPLOY_MCP_TOKEN, kubeconfig contents, or any value from SEALAI_INPUTS_PATH.
  4. No file-based RPC: never create control.json, inputs-required.json, turn-report.json, verify-report.json, or anything under .sealos/brain/.
  5. Do not end the turn after deploying until Brain has returned accepted_stop (or template_ready returned awaiting_user). A turn that ends without a control call is a contract violation, except when a missing explicit safety authorization makes the requested mutation impermissible; report that blocked action without performing it.

Pipeline

1. Classify

Classify the workspace with the use-sealos decision tree (../use-sealos/references/deploy.md, recipes.md): known self-hosted product → store template or official image; user source code → Kaniko build. Skip the preflight/login part of that skill entirely.

2. Build (source path only)

No Docker daemon exists here. Build with the sibling executor:

bash
python3 ../k8s-kaniko-job/scripts/kaniko-build.py \
  --image "ghcr.io/<token-login>/<repo>:deploy-<git-short-sha>"

(paths relative to this skill; run it from $SEALAI_DEPLOY_WORKSPACE). Read ../k8s-kaniko-job/SKILL.md first. Use the returned digest-pinned image_ref in the template. If pull is private, create the <app>-pull secret now (command in that SKILL.md) and reference it from the workload with the fixed literal name.

3. Template at the fixed path

The canonical artifact is exactly $SEALAI_DEPLOY_WORKSPACE/.sealos/template/index.yaml. Brain reads this path byte-for-byte — no other location counts.

  • Store hit: materialize the store template locally, then continue on the raw-deploy path (the store-instance endpoint is forbidden in managed mode — it cannot carry the ownership labels and leaves nothing to hash):

    bash
    python3 ../use-sealos/scripts/sealos-api.py store-export <template> \
  --out "$SEALAI_DEPLOY_WORKSPACE/.sealos/template/index.yaml"

  • Official image / built image: write the template per ../use-sealos/references/platform.md (and databases.md for KubeBlocks blocks).

Managed-mode template requirements on top of the platform contract:

  • The file must start with the apiVersion: app.sealos.io/v1 / kind: Template header, have a non-empty metadata.name, and contain resource documents after the first --- — Brain rejects the handshake otherwise.
  • Declare every value only the end user can supply (external API keys, admin email, ...) in spec.inputs with required: true and no default. Brain renders its form from exactly these. Everything else belongs in spec.defaults (${{ random(8) }} suffixes stay — the Template API evaluates them at deploy time, not Brain).
  • Never add labels beyond the platform contract; the ownership labels travel through the deploy call, not the YAML.
Show full SKILL.md (497 more words)Show less
4. Handshake: template_ready
bash
sha256sum "$SEALAI_DEPLOY_WORKSPACE/.sealos/template/index.yaml"

Call template_ready with only {"sha256": "<lowercase hex>"} — the hash of the final file bytes. Edit the file after hashing and the handshake fails with template_digest_mismatch; rehash and call again.

  • awaiting_user → stop the turn immediately. No Template API call, no kubectl apply, nothing. Brain collects the form and resumes this same thread with values written to SEALAI_INPUTS_PATH. After resuming, do not change spec.inputs (Brain rejects the new schema); rerun template_ready with the unchanged file, then continue.
  • continue → deploy the same file.
  • Tool error → diagnose, fix, retry the same call. Control errors are recoverable; missing tools are fatal.
5. Deploy
bash
cd "$SEALAI_DEPLOY_WORKSPACE"
python3 <this-skill>/../use-sealos/scripts/sealos-api.py deploy \
  .sealos/template/index.yaml \
  $(test -f "$SEALAI_INPUTS_PATH" && echo --args-file "$SEALAI_INPUTS_PATH")
  • User values flow only through --args-file "$SEALAI_INPUTS_PATH" — never into prompt text, logs, or tool arguments.
  • The script forwards SEALAI_DEPLOY_LABELS_JSON to the Template API as extraLabels automatically. Never edit, extend, or re-derive those labels, and never invent deployment-name/template-name labels. The Instance name comes from the deploy response (response.name) — Brain does not supply one.
  • Do not call sealos-api.py adopt (and do not POST adopt-template-instance). Managed deploys already stamp brain.io/* via extraLabels; a second claim returns 409. The script skips adoption when SEALAI_DEPLOY_TASK_ID or SEALAI_PROJECT_ID is set, and when the region is not *.sealos.io.
  • Quota or validation errors: fix the template (re-run step 4 — the hash changed) or report the failure via the normal repair loop. Never shrink resources silently.
6. Verify, then deployment_completed

Verify for real before reporting (../use-sealos/references/deploy.md §Verify; triage failures with operate.md):

bash
HOST=$(kubectl get ingress -l "cloud.sealos.io/deploy-on-sealos=<instance>" \
  -o jsonpath='{.items[0].spec.rules[0].host}')
bash ../use-sealos/scripts/wait-app.sh -t 600 ${HOST:+-u "https://$HOST"} \
  -l "cloud.sealos.io/deploy-on-sealos=<instance>"

Only after your own checks pass, collect the real references:

bash
kubectl get deployments,statefulsets -l "cloud.sealos.io/deploy-on-sealos=<instance>" \
  -o jsonpath='{range .items[*]}{.apiVersion}{" "}{.kind}{" "}{.metadata.name}{"\n"}{end}'

Call deployment_completed with:

  • workloads: 1–32 refs, each exactly {apiVersion, kind, name, namespace: $SEALAI_NAMESPACE} — no extra fields (the schema is strict). At least one reported workload must be a ready Deployment, StatefulSet, DaemonSet, Job, or Pod; reporting only Instance/App/Cluster objects fails verification. Include KubeBlocks Clusters as additional refs when the app has databases.
  • publicUrl (optional): the https://<host> the app serves, only when an Ingress exists and your own probe returned 2xx. Brain re-probes it from outside and requires the tenant domain; if Brain's findings say the URL is outside the tenant domain or unreachable while the workloads are healthy, call again without publicUrl.

Responses and errors:

  • accepted_stop → done; end the turn with a normal summary.
  • repair → the findings are evidence, not commands. Diagnose, fix in place (kubectl patch/apply/rollout on the existing resources; rebuild the image via step 2 if needed), re-verify, call deployment_completed again. Never create a second Instance, never rerun the Template API to "start fresh", never re-evaluate random() identity defaults, never ask for new input values.
  • deployment_completed_throttled → wait ≥5s, call again.
  • deployment_completed_before_template_ready → run step 4 first.

There is no repair-count limit; the only limit is SEALAI_TURN_DEADLINE_AT.

Routing

NeedReference
Deploy-path classification, store/instance mechanics, verification, first aid../use-sealos/references/deploy.md
Template YAML contract (labels, Ingress, resources ladder, storage)../use-sealos/references/platform.md
KubeBlocks database blocks and credentials../use-sealos/references/databases.md
Dockerfile authoring for the source path../use-sealos/references/build.md §1 only
In-cluster image build../k8s-kaniko-job/SKILL.md
Debugging failed workloads../use-sealos/references/operate.md

Load only what the step needs. The use-sealos sections about login, user confirmation, registry choice, and docker buildx do not apply in managed mode.

© hashgraph-online, 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 plugins/labring/sealos-skills/plugins/sealos/skills/sealos-deploy of hashgraph-online/awesome-codex-plugins.

Open the folder on GitHubat commit 78497e5

Compare with similar skills

Sealos Deploy 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.

Sealos Deploy compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Sealos Deploy this skillhashgraph-online/awesome-codex-plugins1.2k—~2.8kAutomated safety check: PassApache-2.0
AWS Cdk Developmentzxkane/aws-skills3672 repos~2.5kAutomated safety check: PassMIT
Prepare Cloudflare Production DeploymentLubomirGeorgiev/cloudflare-workers-nextjs-saas-template786—~5.9kAutomated safety check: NotesMIT
Deploy Observabilityaliyun/alibabacloud-observability-mcp-server166—~2.6kAutomated safety check: NotesNone
Release Allpaperboytm/spool592—~1.1kAutomated safety check: PassCustom licence
Deploynoskillish/bankmcp276—~744Automated safety check: PassMIT

Similar skills

  • AWS Cdk Development

    zxkane/aws-skills

    AWS Cloud Development Kit (CDK) expert for building cloud infrastructure with TypeScript/Python.

    367 GitHub starsUsed in 2 repos~2.5k tokens
    DevOps & CloudAuto-check passed

  • Prepare Cloudflare Production Deployment

    LubomirGeorgiev/cloudflare-workers-nextjs-saas-template

    Source-of-truth runbook for preparing this Vinext Cloudflare Workers SaaS template for production deployment.

    786 GitHub stars~5.9k tokensUpdated yesterday
    DevOps & CloudAuto-check: notes

  • Deploy Observability

    aliyun/alibabacloud-observability-mcp-server

    Deploy, start, and update the Alibaba Cloud Observability MCP Server (阿里云可观测 MCP Server).

    166 GitHub stars~2.6k tokensUpdated 1 mo ago
    DevOps & CloudAuto-check: notes

  • Release All

    paperboytm/spool

    Publish the complete Spool CLI release train: synchronized versions, npm packages, the GitHub release, and the matching production web deployment.

    592 GitHub stars~1.1k tokensUpdated 2 mo ago
    DevOps & CloudAuto-check passed

  • Deploy

    noskillish/bankmcp

    Deploy BankMCP™ to a small server so it works in claude.ai and on the phone: Railway or Fly.io, volume, domain, setup page, connector.

    276 GitHub stars~744 tokensUpdated 10 days ago
    DevOps & CloudAuto-check passed

  • Hcls Deploy Agent

    aws-samples/amazon-bedrock-agents-healthcare-lifesciences

    Official

    A skill your agent uses when a developer wants to deploy an HCLS agent to Amazon Bedrock AgentCore, configure Gateway tools as MCP endpoints, set up authentication with Cognito, configure memory, or…

    274 GitHub stars~813 tokensUpdated 7 days ago
    DevOps & CloudAuto-check passed

More from hashgraph-online/awesome-codex-plugins

All 686 skills in this repo

  • Anime Reaction Gif

    hashgraph-online/awesome-codex-plugins

    Create original anime-style reaction stickers as looping GIFs and MP4 previews, using generated character pose sheets and timed key poses.

    1.2k GitHub stars~922 tokensUpdated today
    Auto-check passed

  • Calibredb

    hashgraph-online/awesome-codex-plugins

    Manage and query Calibre libraries with the calibredb CLI (local paths or Calibre Content server URLs).

    1.2k GitHub stars~1k tokensUpdated today
    Auto-check passed

  • Rust API Test Harness

    hashgraph-online/awesome-codex-plugins

    A skill your agent uses when adding, changing, testing, or debugging Rust HTTP APIs and services, especially when Codex needs black-box integration tests, random-port app startup, real database test…

    1.2k GitHub stars~1.7k tokensUpdated today
    Auto-check passed

  • Art

    hashgraph-online/awesome-codex-plugins

    Make a studio's game look like something at build time — a cover from a real frame of the game (free), painted covers, backdrops, textures and character plates from image models through the…

    1.2k GitHub stars~2.4k tokensUpdated today
    Auto-check passed

  • Game Balance Economy

    hashgraph-online/awesome-codex-plugins

    Balance game difficulty, resources, rewards, probability, progression, economies, and dominant strategies.

    1.2k GitHub stars~618 tokensUpdated today
    Auto-check passed

  • Manuscript Engagement Analytics

    hashgraph-online/awesome-codex-plugins

    Analyze nonfiction manuscripts for reader engagement signals, including heading-level word counts, slow starts, long slogs, weak takeaway titles, value pacing, beta-reader comment dropoff, and…

    1.2k GitHub stars~875 tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Sealos Deploy

What does Sealos Deploy do?

Brain managed-mode deploy executor for Sealos Cloud. An agent skill from hashgraph-online/awesome-codex-plugins. Sealos Deploy is an agent skill from hashgraph-online/awesome-codex-plugins. Brain managed-mode deploy executor for Sealos Cloud.

When should I use Sealos Deploy?

Sealos Deploy fits situations like: SEALAIDEPLOYMODE=managed (a Brain Devbox sandbox); the task says to run /sealos-deploy: deploy the workspace repository to Sealos through the MCP-gated managed pipeline — classify; build via Kaniko if needed; generate the canonical template.

How do I install Sealos Deploy in Claude Code?

Run `npx skills add hashgraph-online/awesome-codex-plugins --skill sealos-deploy -a claude-code`. Or copy the skill folder (plugins/labring/sealos-skills/plugins/sealos/skills/sealos-deploy in hashgraph-online/awesome-codex-plugins) into .claude/skills/sealos-deploy in your project. Claude Code loads it when a task matches its description.

How do I install Sealos Deploy in Codex?

Run `npx skills add hashgraph-online/awesome-codex-plugins --skill sealos-deploy -a codex`. Or copy the skill folder (plugins/labring/sealos-skills/plugins/sealos/skills/sealos-deploy in hashgraph-online/awesome-codex-plugins) into .agents/skills/sealos-deploy in your project. Codex loads it when a task matches its description.

Can I use Sealos Deploy 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 hashgraph-online/awesome-codex-plugins --skill sealos-deploy -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/sealos-deploy, .gemini/skills/sealos-deploy, .github/skills/sealos-deploy and .opencode/skills/sealos-deploy in your project.

What does Sealos Deploy need to run?

Going by SKILL.md and its folder, Sealos Deploy needs the command-line tools its instructions call (python3, kubectl and bash) and credentials named GITHUB_TOKEN and SEALAI_DEPLOY_MCP_TOKEN. Our summary lists: Python 3; Docker; A credential in GITHUB_TOKEN; A credential in SEALAI_DEPLOY_MCP_TOKEN. Its frontmatter pre-approves these tools: Bash(kubectl:*), Bash(python3:*), Bash(curl:*), Bash(bash:*), Bash(git:*), Bash(tar:*), Bash(sha256sum:*), Bash(command:*).

Does Sealos Deploy 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 Sealos Deploy 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 Sealos Deploy use?

Sealos Deploy is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Sealos Deploy use?

About 2.8k tokens (SKILL.md is roughly 11k 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 Sealos Deploy?

Skills that share tags, products or a category with Sealos Deploy: AWS Cdk Development (zxkane/aws-skills, 367 stars), Prepare Cloudflare Production Deployment (LubomirGeorgiev/cloudflare-workers-nextjs-saas-template, 786 stars), Deploy Observability (aliyun/alibabacloud-observability-mcp-server, 166 stars) and Release All (paperboytm/spool, 592 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Sealos Deploy?

hashgraph-online (a GitHub organization) maintains it in hashgraph-online/awesome-codex-plugins, which has 1,242 GitHub stars. The repository holds 686 skills in this directory. The repository was last updated on October 8, 2026.

Source: hashgraph-online/awesome-codex-plugins on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.