check

A repository health-check skill that runs the same broad verification script used by CI. CI is the automated system that checks changes, and this project requires a Mac for its full Swift and app checks.

In plain words
What is it for?
It checks tests, coverage, builds, formatting, linting, dependency and site integrity, shell scripts, Python code, evaluation tests, and release checks.
Why use it?
It provides one reference for whether the repository is ready and avoids claiming that Mac-only tests passed on another system. A portable subset is available for non-Mac environments.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/assemblyai/blurt/check
Any agent
npx skills add AssemblyAI/blurt --skill check
Clone the repo
git clone --depth 1 https://github.com/AssemblyAI/blurt

Made for: Claude Code, Codex.

Per session 164 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,876 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00164 $0.01876
Opus 5 $0.00082 $0.00938
Sonnet 5 $0.00033 $0.00375
Haiku 4.5 $0.00016 $0.00188

Measured 2d ago against content hash 16ca1507a565, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

check 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 2d 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.

.claude/skills/check/SKILL.md · 129 lines

How it starts

The opening of the file, as written. The whole thing — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.

check — is this green?

scripts/check.sh is the single source of truth for "is this green?" It is exactly what CI (.github/workflows/check.yml, macos-26) runs, so a clean local check.sh matches CI by construction.

Before you run: the macOS-only guard

Blurt is macOS-only (platforms: [.macOS(.v15)], AppKit + AVFoundation). The engine imports AVFoundation, so even the SPM package won't compile off-Mac.

If swift/xcodebuild/xcodegen are unavailable (Linux or web sandbox): do not run the full check.sh (it fails fast anyway), and never claim a build/test passed. Say plainly: "Verification must happen on a Mac — CI runs the full check.sh on macos-26 and is the authority on green." You may still read/edit Swift, reason about the pipeline, and write tests for later verification — just don't assert they pass.

What you CAN run there is the portable subset:

scripts/check.sh --portable

It runs the repo-integrity guards — dependencies, sound catalog, site, shell portability, and settled decisions — then actionlint, zizmor, prettier, xmllint, markdownlint, shellcheck, shfmt, ruff (lint + format check), pytest over evals/, and release.test.sh. swift-format lint and swiftlint lint join them when Linux builds are on PATH; under the default web network policy they are not.

That fully verifies docs, site, scripts, eval, and workflow changes. It is not "green" in the CI sense: the entire Swift side is skipped, and the closing line says so. For Swift changes, push and watch check.yml instead — its compile job reports a broken test build in ~2 minutes, and format-patch publishes the exact swift-format reflow as an artifact so you don't have to reproduce it by hand. In Claude Code on the web, the SessionStart hook installs the portable linters automatically.

Quick preflight:

command -v swift xcodebuild xcodegen >/dev/null 2>&1 \
  && echo "macOS toolchain present — safe to run check.sh" \
  || echo "NO toolchain — only check.sh --portable works; Swift verification happens on a Mac/CI"

Read the full file on GitHub · 129 lines

Changes

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.

  1. 2d ago First seen · 129 lines · 164 tokens per session scan A 16ca1507a565

Subscribe to this mod's changes

check is a skill published in the GitHub repository AssemblyAI/blurt (5 stars, last pushed 4d ago), licensed MIT. It adds 164 tokens to every session and 1,876 once invoked, about $0.0008 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-08-31.

Related

Other skills, from other repositories

scarf-template-author

Scaffold a new Scarf project OR enrich an existing one after a Scarf "Upgrade Project" — dashboard, optional configuration schema, optional cron job, AGENTS.md, and (via the scarf-miniapp-author skill) a starter mini-app — from a short conversational interview. Output is immediately usable locally and cleanly…

awizemann/scarf · 79 tokens

scarf-miniapp-author

Author a Scarf mini-app — a small sandboxed web surface (HTML/CSS/JS) that renders inside a project's cockpit and talks to the bound Hermes session + project data through the versioned window.scarf bridge. Use to build a bespoke panel (a task board, an approval queue, a chart, a data table) for a project.

awizemann/scarf · 78 tokens

awesome-swift-macos-apps-docs

Use when adding, updating, or validating app entries in the awesome-swift-macos-apps repository, especially when maintaining both README.md and README.zh.md with concise one-sentence descriptions, correct category placement, and consistent bilingual formatting.

jaywcjlove/awesome-swift-macos-apps · 57 tokens

macos-harness

Control a whole Mac from one persistent Python session with screenshots, PID-targeted input, an animated virtual pointer, targeted Apple Accessibility, Apple Events, Browser Harness CDP, and filesystem access. Use for native, Electron, browser, dialog, file, or cross-app tasks without moving the physical cursor or…

browser-use/macos-harness · 71 tokens

repo-build-pr

End-to-end implementation loop for the os-clovy repo: study the prompt, ask the clarifying questions that change what gets built, plan and architect on the session model while delegating bulk implementation and review to cheaper strong models, isolate work in git worktrees, validate with deterministic checks plus…

open-software-network/os-clovy · 177 tokens

os-accounts-integration

Integrate consumer apps, Tauri desktop clients, or backend services with OS Accounts, the Open Software identity and credit-billing platform. Use when adding Login with Open Software, PKCE callback handling, /me, access-token verification with JWKS/ES256, auth middleware for Hono/Fastify/Express/Rust, top-up links…

open-software-network/os-clovy · 156 tokens