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 karad/seiro-mcp --skill seiro-mcp-visionos-build-operatorgit clone --depth 1 https://github.com/karad/seiro-mcpWrote 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/karad/seiro-mcp/seiro-mcp-visionos-build-operator)<a href="https://agentmods.dev/skills/karad/seiro-mcp/seiro-mcp-visionos-build-operator"><img src="https://agentmods.dev/badge/skills/karad/seiro-mcp/seiro-mcp-visionos-build-operator/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/karad/seiro-mcp/seiro-mcp-visionos-build-operator"><img src="https://agentmods.dev/badge/skills/karad/seiro-mcp/seiro-mcp-visionos-build-operator.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.00086 | $0.01408 |
| Opus 5 | $0.00043 | $0.00704 |
| Sonnet 5 | $0.00017 | $0.00282 |
| Haiku 4.5 | $0.00009 | $0.00141 |
Grade B, and why
seiro-mcp-visionos-build-operator scanned grade B with 1 finding 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 12d 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
| `xcode_unlicensed` | validate | Ask user to accept license (`sudo xcodebuild -license`), then rerun from step 1 | How it starts
The opening of the file, as written. The whole thing — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
seiro-mcp-visionos-build-operator
Display label: Seiro MCP VisionOS Build Operator
Listing summary: Build and diagnose visionOS projects with Seiro MCP
Purpose
This skill standardizes the operational flow for visionOS builds on Seiro MCP.
It does not replace MCP tools. It orchestrates them in a predictable order.
Its identifier follows the bundled skill prefix policy: seiro-mcp-.
When to Use / When Not to Use
Use this skill when:
- The task involves an Xcode project or a visionOS project and requires build, scheme discovery, failure diagnosis, or artifact retrieval.
- Seiro MCP tools are available and can cover the requested operation.
- The user explicitly asks to use
seiro-mcp-visionos-build-operator.
Do not use this skill when:
- The task is unrelated to visionOS build operations.
- The user explicitly asks to run raw shell commands such as
xcodebuildorswiftc. - Seiro MCP is unavailable or cannot satisfy the requested operation.
Required Inputs
Collect and confirm these inputs before running the flow:
project_path(absolute path, allowed by server policy)scheme- Optional
workspace - Optional
destination(defaults to Apple Vision Pro simulator destination) - Optional
configuration - Optional
extra_args - Optional
include_logsfor artifact fetch
Canonical Flow
- Optional project/scheme discovery:
- If
project_pathorschemeis missing/unknown, callinspect_xcode_schemesfirst to discover candidate schemes. - Treat
.xcodeprojand.xcworkspaceas directory packages, not regular files. - Do not conclude that the project is missing based only on file-only searches such as
rg --filesor*.xcodeprojfile globs. - If local inspection is needed before the MCP call, use directory-aware discovery (for example,
find . -maxdepth 1 -type d \\( -name "*.xcodeproj" -o -name "*.xcworkspace" \\)). - If
project_pathis omitted forinspect_xcode_schemes, resolution order is:.xcodeprojdiscovered in current working directoryvisionos.default_project_pathfromconfig.toml
- If
What ships with it
3 files 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.
- 12d ago First seen · 107 lines · 86 tokens per session scan B 38a40f2c7f5d
seiro-mcp-visionos-build-operator is a skill published in the GitHub repository karad/seiro-mcp (16 stars, last pushed 2mo ago), licensed MIT. It adds 86 tokens to every session and 1,408 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it B with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
workflow-audit
Systematic UI workflow auditing for SwiftUI applications. Discovers entry points, traces user flows, detects dead ends and broken promises, audits data wiring, evaluates from user perspective. Triggers: "workflow audit", "audit flows", "find dead ends", "check navigation".
ttb-skill-bugfix
Systematic bug fixing workflow for TTBaseUIKit apps: root cause analysis, fix strategy, xcodebuild verify, zero regression.
bug-repro-plan
Create a minimal, repeatable reproduction plan for a bug. Use when a junior developer needs clear steps to reproduce and capture evidence.
debugging-checklist
Provide a systematic debugging checklist. Use when a junior developer is stuck and needs a structured approach.
error-message-explainer
Explain compiler/runtime errors in plain language. Use when a junior developer needs help understanding an error message.
linter-fix-guide
Explain lint errors and propose fixes. Use when a junior developer needs help resolving common lint or format warnings.