uv is a Rust-written tool for managing Python packages, projects, environments, versions, scripts, and command-line tools. Python developers use it as a single workflow for dependency management and project tasks, including projects organized into Cargo-style workspaces; the catalogue entries assist with its use or development.
Borrowing it
Nothing to install: this file belongs to astral-sh/uv. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/astral-sh/uv/main/.codex/skills/load-github-action-thread/SKILL.mdgit clone --depth 1 https://github.com/astral-sh/uvWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/astral-sh/uv/load-github-action-thread)<a href="https://agentmods.dev/skills/astral-sh/uv/load-github-action-thread"><img src="https://agentmods.dev/badge/skills/astral-sh/uv/load-github-action-thread/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/astral-sh/uv/load-github-action-thread"><img src="https://agentmods.dev/badge/skills/astral-sh/uv/load-github-action-thread.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Snyk warn
- NVIDIA SkillSpector pass
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00062 | $0.00954 |
| Opus 5.5 | $0.00025 | $0.00382 |
| Sonnet 5.5 | $0.00012 | $0.00191 |
| Haiku 4.5 | $0.00006 | $0.00095 |
Grade A, and why
load-github-action-thread scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
Load GitHub Action Thread
When given an issue instead of a run, find the related issue-triage run first. Resolve the issue title and number, then match the run display title:
repository=astral-sh/uv
issue=20477
issue_title="$(gh issue view "$issue" --repo "$repository" --json title --jq '.title')"
issue_number="$(gh issue view "$issue" --repo "$repository" --json number --jq '.number')"
gh run list --repo "$repository" --workflow issue-triage.yml --limit 500 \
--json databaseId,displayTitle,event,status,conclusion,createdAt,url \
| jq -c --arg title "$issue_title" '.[] | select(.displayTitle == $title)'
Use the newest matching run. An issue-triage run can contain both the triage and bug-reproduction threads. Also check for directly dispatched bug-reproduction runs; their display title does not include the issue title. If the issue title changed or a run was manually dispatched, list recent candidates and confirm them from their logs:
gh run list --repo "$repository" --workflow reproduce-bug.yml --limit 100 \
--json databaseId,event,status,conclusion,createdAt,url
gh run view <run-id> --repo "$repository" --log | rg -m 2 "ISSUE: $issue_number|issue: $issue_number"
When given a pull request, find its security-review run from the pull request checks. The check link contains the Actions run URL and can be passed directly to the loader:
pull_request=20482
gh pr checks "$pull_request" --repo "$repository" --json name,workflow,state,link \
--jq '.[] | select(.name | test("review"; "i"))'
The security-review job only runs for eligible same-repository pull requests; a skipped review has no thread artifact to load.
Run the repository utility with the GitHub Actions run URL:
./agents/scripts/load-github-action-thread.sh https://github.com/astral-sh/uv/actions/runs/123456789
The utility downloads every matching codex-thread-* artifact, finds the root codex exec rollout
for each step, and forks it into an interactive local Codex thread. Subagent rollouts are ignored;
they inherit the root prompt and would otherwise produce duplicate-looking tasks. The first line of
the root preview becomes the task title, including the step, source number, and issue or pull
request title. Forking is required because codex-action uses codex exec; copying an exec
rollout into ~/.codex/sessions alone does not make it visible in the Codex app.
For a numeric run ID, pass the repository when it cannot be inferred from the current checkout:
./agents/scripts/load-github-action-thread.sh 123456789 --repo astral-sh/uv
Use --artifact PATTERN to select a particular retained thread and --cwd PATH to attach the
imported history to a different local checkout:
./agents/scripts/load-github-action-thread.sh 123456789 \
--repo astral-sh/uv \
--artifact 'codex-thread-reproduce-bug-*' \
--cwd /path/to/uv
The utility requires gh, jq, and codex, plus zstd for compressed rollouts. It prints the
resolved title and a codex://threads/<id> link for every imported task and automatically opens the
Codex app when exactly one task is imported on macOS. For multiple steps, return a Markdown list
with a clickable link labeled by the corresponding task title without repeatedly switching the app:
- [Issue triage for #20477: Example issue](codex://threads/<id>)
- [Bug reproduction for #20477: Example issue](codex://threads/<id>)
Use the matching step title for codex-thread-pull-request-security-review-* and
codex-thread-release-prepare-*.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 89 lines · 62 tokens per session scan A 05f1f63e72e7
load-github-action-thread is a skill published in the GitHub repository astral-sh/uv (91,321 stars, last pushed today), licensed Apache-2.0. It adds 62 tokens to every session and 954 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
docs-decisions
Work on Composio documentation content, Fumadocs configuration, changelogs, docs automation prompts, docs decisions, ADR-style records, and docs review guidance. Use for files under docs/, documentation workflows, or requests to record or update a docs decision. Do not use for SDK runtime changes unless docs are the…
python
Use when the task is Python itself, in any framework or none: PEP 695 generics, mypy --strict typing, dataclass/Protocol/TypedDict/Enum choices, asyncio.TaskGroup, stdlib idioms, src/ layout + pyproject.toml with uv, ruff+mypy+pytest gate. NOT a FastAPI/ASGI service (that is fastapi), NOT a deep pytest suite (that is…
uv-workflow
Use when a coding agent needs to run Python code, modules, one-liners, tools, tests, or standalone scripts through uv, or create and maintain PEP 723 scripts with uv init/add/remove --script. Avoid direct python/python3 shell entrypoints.
review-test-stubs
Review the test stubs for coverage, scope, vacuous-assertion freedom, finding-grounded scope, and happy-path completeness against the interview and the modeled schema — not for code quality.
consolidate-interview
End of session — replace running notes with the full synthesis across all three funnel levels and author the glossary of ubiquitous language.
review-implementation
Gate the implementation against its contract for correctness, quality, drift, and green tests.