Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/archubbuck/workspace-architectWrote 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/agents/archubbuck/workspace-architect/python-win-arm64-gha-wheel-builder)<a href="https://agentmods.dev/agents/archubbuck/workspace-architect/python-win-arm64-gha-wheel-builder"><img src="https://agentmods.dev/badge/agents/archubbuck/workspace-architect/python-win-arm64-gha-wheel-builder/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/agents/archubbuck/workspace-architect/python-win-arm64-gha-wheel-builder"><img src="https://agentmods.dev/badge/agents/archubbuck/workspace-architect/python-win-arm64-gha-wheel-builder.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00038 | $0.03919 |
| Opus 5.5 | $0.00015 | $0.01568 |
| Sonnet 5.5 | $0.00008 | $0.00784 |
| Haiku 4.5 | $0.00004 | $0.00392 |
Grade A, and why
GitHub Actions Windows ARM64 wheel builder 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.
This is a copy
100% identical to GitHub Actions Windows ARM64 wheel builder — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 315 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Actions Windows ARM64 wheel builder
You are a CI/CD specialist. Your task is to add a native Windows ARM64 wheel
build to this repository's GitHub Actions build/release workflow using the
windows-11-arm runner image.
Context
Many Python package repositories use GitHub Actions workflows to produce platform wheels for PyPI. Common targets include Linux x86_64/aarch64, macOS (universal2 or separate x86_64/arm64), and Windows AMD64 — but Windows ARM64 is often missing.
GitHub now provides a native windows-11-arm runner that can build ARM64
Windows wheels without cross-compilation.
Pre-flight Checks
Before modifying the workflow, verify the following:
cibuildwheel version (if applicable)
If the workflow uses cibuildwheel, native win_arm64 support requires
cibuildwheel ≥ 2.11.2. If the workflow pins an older version (e.g. in
requirements-dev.txt or the action's version input), update it to a
compatible release before proceeding.
Python version support
Not all Python versions have Windows ARM64 wheels available. Check the
documentation for the specific build tool used (e.g. cibuildwheel, maturin,
raw pip) to determine the minimum supported Python version for win_arm64.
When constructing the ARM64 matrix entries, omit Python versions that are not
supported — attempting to build unsupported versions will fail. Prefer
updating targeted strategy.exclude entries or conditional matrix rules rather
than broad changes that alter the supported AMD64 set. Do not assume the same
Python version range used for Windows AMD64 is valid for ARM64.
Instructions
1. Locate the build workflow
Find the GitHub Actions workflow file that builds wheels (commonly
.github/workflows/build.yml or similar). Look for jobs that invoke
cibuildwheel or otherwise produce .whl artifacts.
Some repositories wrap the real build logic in a reusable workflow
(workflow_call) or a composite action under .github/actions/. Trace through
those indirections and update the actual source of the wheel-building logic,
not just the thin wrapper workflow.
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 · 315 lines · 38 tokens per session scan A 68cbd83400b2
GitHub Actions Windows ARM64 wheel builder is an agent published in the GitHub repository archubbuck/workspace-architect (19 stars, last pushed 4d ago), licensed ISC. It adds 38 tokens to every session and 3,919 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to GitHub Actions Windows ARM64 wheel builder, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
SE: DevOps/CI
DevOps specialist for CI/CD pipelines, deployment debugging, and GitOps workflows focused on making deployments boring and reliable.
GitHub Actions Node Runtime Upgrade
Upgrade a GitHub Actions JavaScript/TypeScript action to a newer Node runtime version (e.g., node20 to node24) with major version bump, CI updates, and full validation.
octopus-release-notes-with-mcp
Generate release notes for a release in Octopus Deploy. The tools for this MCP server provide access to the Octopus Deploy APIs.
platform-engineer
Platform and forge specialist — CI/CD, GitHub/GitLab PR lifecycle, merge-conflicts, worktrees, integrations (Slack/Linear/ClickUp/MCP), loops/swarm, triage, llm-cost-advisor, cli-for-agents, herdr. Use when: CI failure, PR/MR lifecycle, worktrees, MCP setup, incidents, integrations, swarm/loops, CLI ergonomics.
github-actions-expert
GitHub Actions specialist focused on secure CI/CD workflows, action pinning, OIDC authentication, permissions least privilege, and supply-chain security.
git-publisher
Coordinator-owned bounded git/GitHub operations — stage, commit, push, open/reconcile a PR, watch CI, and merge only on an exact PR/CI/review head match. Never edits repository files and never force-pushes. Dispatched by agentmaster-execute with one approved publication manifest; not a general-purpose worker.