Privacy Policy
thedaviddias/Front-End-Checklist
A skill your agent uses when reviewing whether a website has a visible, accessible privacy policy link, particularly in the footer navigation.
Choose the first OpenMed workflow skill for an intake, privacy, extraction, exchange, or verification request using deterministic local routing.
Apache-2.0Auto-check passed
Install Ask Openmed
$ npx skills add maziyarpanahi/openmed --skill ask-openmed -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install maziyarpanahi/openmed ask-openmed --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/maziyarpanahi/openmed.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/ask-openmed .claude/skills/ask-openmed && 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 "ask-openmed" agent skill from https://github.com/maziyarpanahi/openmed/tree/master/skills/ask-openmed into .claude/skills/ask-openmed/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ask-openmed", 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/maziyarpanahi/openmed/tree/master/skills/ask-openmedType 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 maziyarpanahi/openmed --skill ask-openmed -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install maziyarpanahi/openmed ask-openmed --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/maziyarpanahi/openmed.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/ask-openmed .agents/skills/ask-openmed && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "ask-openmed" agent skill from https://github.com/maziyarpanahi/openmed/tree/master/skills/ask-openmed into .agents/skills/ask-openmed/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ask-openmed", 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 maziyarpanahi/openmed --skill ask-openmed -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install maziyarpanahi/openmed ask-openmed --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/maziyarpanahi/openmed.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/ask-openmed .cursor/skills/ask-openmed && 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 "ask-openmed" agent skill from https://github.com/maziyarpanahi/openmed/tree/master/skills/ask-openmed into .cursor/skills/ask-openmed/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ask-openmed", 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/maziyarpanahi/openmed.git --path skills/ask-openmed--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 maziyarpanahi/openmed --skill ask-openmed -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install maziyarpanahi/openmed ask-openmed --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/maziyarpanahi/openmed.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/ask-openmed .gemini/skills/ask-openmed && 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 "ask-openmed" agent skill from https://github.com/maziyarpanahi/openmed/tree/master/skills/ask-openmed into .gemini/skills/ask-openmed/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ask-openmed", 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 maziyarpanahi/openmed ask-openmedInstalls 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 maziyarpanahi/openmed --skill ask-openmed -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/maziyarpanahi/openmed.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/ask-openmed .github/skills/ask-openmed && 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 "ask-openmed" agent skill from https://github.com/maziyarpanahi/openmed/tree/master/skills/ask-openmed into .github/skills/ask-openmed/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ask-openmed", 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 maziyarpanahi/openmed --skill ask-openmed -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install maziyarpanahi/openmed ask-openmed --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/maziyarpanahi/openmed.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/ask-openmed .opencode/skills/ask-openmed && 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 "ask-openmed" agent skill from https://github.com/maziyarpanahi/openmed/tree/master/skills/ask-openmed into .opencode/skills/ask-openmed/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ask-openmed", 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
ask-openmed- GitHub stars
- 5.5k
- Token cost
- ~2.5k tokens
- SKILL.md length
- 956 words
- Files
- 1
- Skills in repo
- 74
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Choose the first OpenMed workflow skill for an intake, privacy, extraction, exchange, or verification request using deterministic local routing.
- Works in 5 steps: Normalize only the stated goal:… → Apply the intake boundary. If the goal… → For a goal with no intake cue, apply the… → …
- A goal is broad
- SKILL.md covers Deterministic routing contract, Intake, Privacy and Extraction, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Ask Openmed is an agent skill from maziyarpanahi/openmed. Choose the first OpenMed workflow skill for an intake, privacy, extraction, exchange, or verification request using deterministic local routing. Use when a goal is broad, spans several clinical-data stages, or leaves the data-sensitivity status unclear; the privacy gate is selected before downstream work when raw clinical or personal content may be present.
Its SKILL.md is about 2.5k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
The repository describes itself as: Local-first healthcare AI: clinical NER and HIPAA PII de-identification on hardware you control. 2,200+ medical models, 35 model-backed PII languages, and Python, MLX, Android… The licence is Apache-2.0.
When your agent uses it
- A goal is broad
- Spans several clinical-data stages
- Leaves the data-sensitivity status unclear
- The privacy gate is selected before downstream work when raw clinical
Example prompts
- “/ask-openmed”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Normalize only the stated goal: lowercase it, trim surrounding whitespace,
- Apply the intake boundary. If the goal matches an Intake row, select the
- For a goal with no intake cue, apply the privacy override. If it asks to
- Otherwise inspect the remaining tables in the fixed handoff order shown
- If no row matches, use building-with-openmed
What it can do on your machine
Read from SKILL.md and the folder at commit 9dca507. 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
Ask Openmed loads about 2.5k tokens when it runs. Until then it costs about 93 tokens; SKILL.md has 956 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 maziyarpanahi/openmed at commit 9dca507, republished under its Apache-2.0 licence (© maziyarpanahi). 956 words, ~2,512 tokens.
Download SKILL.mdSave it as
.claude/skills/ask-openmed/SKILL.md (or your agent's skills folder).- name
- ask-openmed
- description
- Choose the first OpenMed workflow skill for an intake, privacy, extraction, exchange, or verification request using deterministic local routing. Use when a goal is broad, spans several clinical-data stages, or leaves the data-sensitivity status unclear; the privacy gate is selected before downstream work when raw clinical or personal content may be present.
- license
- Apache-2.0
- metadata.project
- OpenMed
- metadata.category
- openmed-core
- metadata.pairs
- adjacent
- metadata.version
- 1.0
Ask OpenMed
Use this skill as the first pass when a request does not name a focused OpenMed workflow. It selects an existing skill identifier; it does not process input, download a model, call a service, or make a clinical decision. No mandatory network call is part of this route.
Deterministic routing contract
Apply these rules in order:
- Normalize only the stated goal: lowercase it, trim surrounding whitespace, and collapse repeated whitespace. Do not inspect or copy the data payload.
- Apply the intake boundary. If the goal matches an Intake row, select the first matching intake skill even when the goal also names a later stage. If sensitivity is unclear, its next handoff is the privacy gate: deidentifying-clinical-text, before extraction, exchange, or verification sees the parsed content.
- For a goal with no intake cue, apply the privacy override. If it asks to
analyze, extract, exchange, share, upload, or verify clinical or personal
content and is not explicitly marked safe, start at the privacy gate. The
only safe markers are
synthetic input,synthetic note,synthetic record,synthetic dataset,input is synthetic,data is synthetic,already de-identified, andalready deidentified. A marker does not count whenno,not,never,unknown, oruncertainoccurs in the four normalized words before it. Treat every ambiguous safety statement as sensitive. - Otherwise inspect the remaining tables in the fixed handoff order shown below. Treat each comma-separated cue as a case-insensitive substring of the normalized goal, and select the first matching row. Every cue cell is a comma-separated list of alternatives; conjunctions have no special meaning. Do not add synonyms or infer cues from the payload. This stage order and row order break every tie.
- If no row matches, use building-with-openmed as the orientation fallback.
Route output should contain only the selected category, skill identifier, matched rule index, and next handoff. Never echo the request, input values, exception text, or detected spans into a log or report.
For a multi-stage request, route one stage at a time in this fixed handoff order: intake → privacy → extraction → exchange → verification. A later stage does not bypass the privacy gate merely because it was named first.
Intake
Choose the first skill for turning an external document or record format into local, processable input.
| Goal cues | First skill | Continue with |
|---|---|---|
| laboratory table, lab table | extracting-lab-tables | privacy, then verification |
| scan, fax, image, PDF, CSV, table, document OCR | ingesting-clinical-documents | privacy, then extraction |
| C-CDA, CCD, CDA XML | parsing-ccda-documents | privacy, then extraction |
| HL7 v2, ADT, ORU, MDM, OBX, pipe-delimited feed | parsing-hl7v2-messages | privacy, then extraction |
| DICOM header, DICOM-SR metadata | extracting-dicom-metadata | privacy, then extraction |
| pull FHIR records, page FHIR records, FHIR server | fetching-fhir-resources | privacy, then extraction |
Privacy
Use the privacy table both for an explicit privacy goal and for the privacy override. The first row is the default gate for unspecified sensitive input.
| Goal cues | First skill | Continue with |
|---|---|---|
| remove clinical identifiers, mask clinical identifiers, redact clinical text, anonymize clinical text, de-identify clinical text | deidentifying-clinical-text | extraction or exchange |
| find identifiers, detect identifiers, PII entities | extracting-pii-entities | de-identification or review |
| privacy policy, privacy profile | configuring-privacy-policies | de-identification |
| PHI in logs, PHI in errors, PHI in telemetry, no-PHI logging | enforcing-nophi-logging | verification |
| de-identify non-English text, multilingual de-identification | deidentifying-multilingual-text | extraction |
| stable pseudonyms, approved linkage pseudonyms | pseudonymizing-for-gdpr | verification |
Show full SKILL.md (418 more words)Show less
Extraction
Choose the focused skill after intake and privacy handling when the request is about finding or structuring clinical meaning.
| Goal cues | First skill | Continue with |
|---|---|---|
| diseases, drugs, anatomy, genes, clinical NER | extracting-clinical-entities | exchange or verification |
| custom entity labels, zero-shot extraction | running-zeroshot-ner | exchange or verification |
| housing, food, work, transport, SDOH | extracting-sdoh | verification |
| lab values, units, reference ranges, abnormal flags | parsing-lab-values | terminology or exchange |
| radiology findings, radiology measurements, radiology impression | structuring-radiology-reports | exchange or verification |
| note sections, clinical sections, section segmentation | segmenting-clinical-sections | extraction |
Exchange
Choose an exchange skill only after the source is safe to handle. These skills may use a user-supplied endpoint or terminology service; this router itself performs no network call.
| Goal cues | First skill | Continue with |
|---|---|---|
| FHIR R4 resources, export to FHIR | exporting-to-fhir | bundle or conformance verification |
| FHIR transaction Bundle, FHIR batch Bundle | assembling-fhir-bundles | conformance verification |
| FHIR Bulk Data export, bulk FHIR | exporting-bulk-fhir | privacy, then extraction |
| SMART-on-FHIR app, SMART-on-FHIR launch | scaffolding-smart-on-fhir | conformance verification |
| terminology validation, terminology expansion, terminology translation, terminology server | querying-terminology-service | exchange or verification |
Verification
Use verification routes for a stated release, safety, leakage, audit, risk, or conformance check. If the source is not explicitly safe, the privacy override still wins first.
| Goal cues | First skill | Decision or handoff |
|---|---|---|
| residual identifiers, de-identification leakage | auditing-deid-leakage | block release on a finding |
| de-identification audit trail, no-PHI audit trail | auditing-deidentification-runs | retain offsets, hashes, and provenance |
| leakage gate, release leakage | evaluating-with-leakage-gates | fail closed on leakage |
| re-identification risk, k-anonymity, quasi-identifiers | reviewing-reidentification-risk | review residual risk |
| Safe Harbor | auditing-safe-harbor-checklist | review the no-PHI report |
| FHIR US Core, USCDI conformance | validating-us-core | correct the resource before exchange |
| HIPAA privacy checklist, HIPAA security checklist | checking-hipaa-compliance | address gaps before release |
Ambiguous goals and escalation examples
Use the privacy override and the fixed handoff order for ambiguous requests:
- “Turn this clinical note into FHIR.” The sensitivity is unstated, so start at deidentifying-clinical-text, then hand off to extracting-clinical-entities and exporting-to-fhir.
- “Extract medications from a synthetic note.” The input is explicitly synthetic, so route directly to extracting-clinical-entities.
- “OCR this image and extract findings.” Route to ingesting-clinical-documents, then apply the privacy gate before extraction.
- “Is this dataset safe to share?” If de-identification is not stated, start with deidentifying-clinical-text and then use auditing-deid-leakage.
- “Verify this clinical dataset; it is not de-identified.” The negated safety statement does not count as a safe marker, so start at deidentifying-clinical-text.
- “Which OpenMed workflow fits?” Use the orientation fallback building-with-openmed, then re-route once the goal and sensitivity status are explicit.
These are routing examples only. Keep all demonstrations synthetic or placeholder-based, and keep route diagnostics free of source content.
© maziyarpanahi, 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 skills/ask-openmed of maziyarpanahi/openmed.
Open the folder on GitHubat commit 9dca507
Compare with similar skills
Ask Openmed 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 |
|---|---|---|---|---|---|---|
| Ask Openmed this skillmaziyarpanahi/openmed | 5.5k | — | ~2.5k | Automated safety check: Pass | Apache-2.0 | |
| Privacy Policythedaviddias/Front-End-Checklist | 74k | — | ~617 | Automated safety check: Pass | MIT | |
| Extractalirezarezvani/claude-skills | 28k | — | ~1.4k | Automated safety check: Pass | MIT | |
| Privacy Policyphuryn/pm-skills | 27k | — | ~2.7k | Automated safety check: Pass | MIT | |
| Data Privacy Controlssickn33/agentic-awesome-skills | 47k | 1 repos | ~3.4k | Automated safety check: Pass | MIT | |
| Performing Privacy Impact Assessmentmukul975/Anthropic-Cybersecurity-Skills | 34k | — | ~2.6k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Extract
alirezarezvani/claude-skills
Turn a proven pattern or debugging solution into a standalone reusable skill with SKILL.md, reference docs, and examples.
Privacy Policy
phuryn/pm-skills
Draft a detailed privacy policy covering data types, jurisdiction, GDPR and compliance considerations, and clauses needing legal review.
Data Privacy Controls
sickn33/agentic-awesome-skills
Data privacy control register: data category, lawful basis, retention period, access roles, encryption and consent requirement per module.
Performing Privacy Impact Assessment
mukul975/Anthropic-Cybersecurity-Skills
Automates the Privacy Impact Assessment (PIA) workflow including data flow mapping, privacy risk scoring matrices, GDPR Article 35 DPIA and CCPA/CPRA alignment checks, data inventory cataloging, and…
Brand Extract
nexu-io/open-design
Extract a complete Brand Kit from a live website by driving the in-app browser.
More from maziyarpanahi/openmed
All 74 skills in this repoHIPAA Safe Harbor Coverage Audit
maziyarpanahi/openmed
Checks OpenMed de-identified clinical text against the 18 HIPAA Safe Harbor identifier categories and reports gaps and residual re-identification risk.
OpenMed Model Card Writer
maziyarpanahi/openmed
Fills in a model card for an OpenMed clinical NER or de-identification model from its evaluation reports: intended use, metrics, subgroups and limitations.
HIPAA Pre-Deployment Compliance Check
maziyarpanahi/openmed
Walks a data pipeline against the HIPAA Privacy and Security Rule checklist and produces a gap report before it processes patient data.
ICD-10 Coding Assistant
maziyarpanahi/openmed
Suggests candidate ICD-10-CM diagnosis and ICD-10-PCS procedure codes for clinical text extracted by OpenMed, with rationale for a certified coder to review.
OpenMed ETL to OMOP CDM
maziyarpanahi/openmed
Maps OpenMed-extracted, terminology-coded conditions, drugs and measurements into OMOP CDM v5.4 tables for OHDSI and ATLAS analytics.
Extracting SDOH and Z-Codes
maziyarpanahi/openmed
Finds social risks such as housing instability or food insecurity in clinical notes and proposes matching ICD-10-CM Z-codes for a coder to confirm.
Questions about Ask Openmed
What does Ask Openmed do?
Choose the first OpenMed workflow skill for an intake, privacy, extraction, exchange, or verification request using deterministic local routing. Ask Openmed is an agent skill from maziyarpanahi/openmed. Choose the first OpenMed workflow skill for an intake, privacy, extraction, exchange, or verification request using deterministic local routing.
When should I use Ask Openmed?
Ask Openmed fits situations like: A goal is broad; spans several clinical-data stages; leaves the data-sensitivity status unclear; the privacy gate is selected before downstream work when raw clinical.
How do I install Ask Openmed in Claude Code?
Run `npx skills add maziyarpanahi/openmed --skill ask-openmed -a claude-code`. Or copy the skill folder (skills/ask-openmed in maziyarpanahi/openmed) into .claude/skills/ask-openmed in your project. Claude Code loads it when a task matches its description.
How do I install Ask Openmed in Codex?
Run `npx skills add maziyarpanahi/openmed --skill ask-openmed -a codex`. Or copy the skill folder (skills/ask-openmed in maziyarpanahi/openmed) into .agents/skills/ask-openmed in your project. Codex loads it when a task matches its description.
Can I use Ask Openmed 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 maziyarpanahi/openmed --skill ask-openmed -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/ask-openmed, .gemini/skills/ask-openmed, .github/skills/ask-openmed and .opencode/skills/ask-openmed in your project.
What does Ask Openmed need to run?
SKILL.md names no scripts, command-line tools or credentials: Ask Openmed is instructions for the agent only.
Does Ask Openmed 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 Ask Openmed 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 Ask Openmed use?
Ask Openmed 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 Ask Openmed use?
About 2.5k tokens (SKILL.md is roughly 10k 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 Ask Openmed?
Skills that share tags, products or a category with Ask Openmed: Privacy Policy (thedaviddias/Front-End-Checklist, 74k stars), Extract (alirezarezvani/claude-skills, 28k stars), Privacy Policy (phuryn/pm-skills, 27k stars) and Data Privacy Controls (sickn33/agentic-awesome-skills, 47k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Ask Openmed?
maziyarpanahi (a GitHub user) maintains it in maziyarpanahi/openmed, which has 5,500 GitHub stars. The repository holds 74 skills in this directory. The repository was last updated on October 9, 2026.
Source: maziyarpanahi/openmed on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.