OpenBot is a local template for AI coworkers that operate an assigned browser, files, and approved tools, while previewing and recording their actions. Developers clone and customize it to run AG-UI agents as supervised coworkers on their own machines. The catalogue contains two skills for working with the project.
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.
npx skills add CopilotKit/OpenBot --skill tauri-signinggit clone --depth 1 https://github.com/CopilotKit/OpenBotWrote 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/copilotkit/openbot/tauri-signing)<a href="https://agentmods.dev/skills/copilotkit/openbot/tauri-signing"><img src="https://agentmods.dev/badge/skills/copilotkit/openbot/tauri-signing/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/copilotkit/openbot/tauri-signing"><img src="https://agentmods.dev/badge/skills/copilotkit/openbot/tauri-signing.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.00202 | $0.03254 |
| Opus 5 | $0.00101 | $0.01627 |
| Sonnet 5 | $0.00040 | $0.00651 |
| Haiku 4.5 | $0.00020 | $0.00325 |
Grade A, and why
agui-tauri-windows-signing 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 yesterday.
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.
How it starts
The opening of the file, as written. The whole thing — 287 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tauri Windows Signing with Azure Key Vault
Context: what signs what
The org's signing infrastructure has three independent mechanisms. Never conflate them — they use different keys, different tools, and different verification paths:
| Mechanism | Key | Tool | Applies to |
|---|---|---|---|
| NuGet author signature | DigiCert cert, CN=Tawkit, Inc. — private key in Azure Key Vault (non-exportable, RSA-HSM) | NuGetKeyVaultSignTool |
*.nupkg only |
| Authenticode (this skill) | Same DigiCert cert, same vault | AzureSignTool |
Windows PE binaries: .exe, .dll, .msi (incl. Tauri builds) |
| Assembly strong-naming | AGUI.snk |
MSBuild | .NET assemblies; unrelated to either signature |
| Tauri updater signature | Tauri minisign key pair (NOT the vault cert) | tauri signer |
Update manifests for tauri-plugin-updater |
Additional facts that agents routinely get wrong:
- nuget.org applies its own repository signature automatically on push. The author signature is what flips a package to "signed" on the gallery; it is not needed for Authenticode at all.
- Symbol packages (
*.snupkg) are intentionally not author-signed. - The vault certificate: DigiCert Trusted G4 Code Signing RSA4096 SHA384 2021 CA1 issuer chain, OV validation. Because it is OV (not EV), Windows SmartScreen reputation builds per-publisher over signed releases rather than being granted instantly — an unsigned-looking warning on a brand-new app is expected until reputation accrues, and is not a signing failure.
- The private key never leaves the HSM. Every signature — NuGet or
Authenticode — is a
keys/signoperation executed inside the vault. Never attempt to export the key or generate a.pfx.
Reference implementation for the NuGet lane (the pattern this skill mirrors):
.github/workflows/publish-release.yml (signing step) and
sdks/dotnet/docs/signing.md (design doc).
Task: wire signing into a Tauri build
1. Point signCommand at a wrapper script
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.
- yesterday First seen · 287 lines · 202 tokens per session scan A c17a9b6c9943
agui-tauri-windows-signing is a skill published in the GitHub repository CopilotKit/OpenBot (5,014 stars, last pushed today), licensed MIT. It adds 202 tokens to every session and 3,254 once invoked, about $0.0010 per session on Opus 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-09-16.
Other skills, from other repositories
atmos-hooks
Atmos hooks: lifecycle events, hook kinds, command/store/git/security hooks, step/steps hooks, when: conditions, scoping and overrides, toolchain integration, --skip-hooks, and Atmos Pro/local output.
atmos-modernization
Atmos Modernization: migrate deprecated or legacy Atmos patterns to current names, Native CI, Atmos Pro drift detection, dependencies.components, nametemplate, and declared secrets.
atmos-pro
Atmos Pro setup and workflows: settings.pro, GitHub OIDC, affected and inventory uploads, stack locks, pro commit, workflow dispatch, merge queues, and drift detection.
atmos-sbom
Atmos SBOM provenance: CycloneDX and SPDX generation from vendor and Terraform evidence, coverage diagnostics, NTIA validation, and native CI workflow-artifact publication.
atmos-version
Atmos Version Tracker: version tracks, lock files, managed external dependency versions, atmos version track commands, !version, file managers, update policy, pinning, and CI verification.
atmos-cache
Atmos caching: CI cache configuration and commands, GitHub Actions cache integration, Terraform registry cache mirror/list/prune/stats/trust, and cache modernization guidance.