peekie-warnings

peekie-warnings is a skill for Claude Code from dodobrands/Peekie. It costs 147 tokens per session (1,261 once invoked), scanned A, original, Apache-2.0.

A command that reads build warnings from an Xcode result bundle. An Xcode result bundle is the saved report produced by an Apple project build or test run.

In plain words
What is it for?
Use it to inspect warnings in an .xcresult bundle, output them as JSON or a readable list, and filter the JSON with jq.
Why use it?
It turns a large build report into a sorted list of warnings with their file, location, type, and message, making issues easier to review or filter.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the peekie plugin — 6 skills shipped together

Good fit Use it to inspect warnings in an .xcresult bundle, output them as JSON or a readable list, and filter the JSON with jq.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/dodobrands/peekie/peekie-warnings
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.

Any agent
npx skills add dodobrands/Peekie --skill peekie-warnings
Clone the repo
git clone --depth 1 https://github.com/dodobrands/Peekie

Made for: Claude Code.

Or install peekie, the plugin that ships this one along with the rest of its 6 skills.

Wrote 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.

agentmods badge for peekie-warnings

README.md
[![agentmods](https://agentmods.dev/badge/skills/dodobrands/peekie/peekie-warnings/github.svg)](https://agentmods.dev/skills/dodobrands/peekie/peekie-warnings)
Your own site
<a href="https://agentmods.dev/skills/dodobrands/peekie/peekie-warnings"><img src="https://agentmods.dev/badge/skills/dodobrands/peekie/peekie-warnings/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.

agentmods 80×15 button for peekie-warnings

Your own site · 80×15
<a href="https://agentmods.dev/skills/dodobrands/peekie/peekie-warnings"><img src="https://agentmods.dev/badge/skills/dodobrands/peekie/peekie-warnings.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 147 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,261 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.1 $0.00147 $0.01261
Opus 5 $0.00073 $0.00630
Sonnet 5 $0.00029 $0.00252
Haiku 4.5 $0.00015 $0.00126

Measured 11d ago against content hash 1a3ae02ac3cb, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

peekie-warnings 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 11d 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.

agent/skills/peekie-warnings/SKILL.md · 106 lines

How it starts

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

peekie warnings

List every build warning in a .xcresult bundle as a flat sorted JSON array (or human-readable list).

Synopsis

peekie warnings <xcresult-path> [flags]

Flags

Flag Default Notes
<xcresult-path> Required positional. Path to the .xcresult bundle.
--format json|list json Output format.
-v, --verbose false Debug-level logging to stderr.

There is no --include flag on peekie warnings. Filter with jq.

Output shape

--format json (default)

Flat sorted array, one entry per warning:

[
  {"file": "Foo.swift", "line": 42, "column": 8, "type": "DeprecatedDeclaration", "message": "'oldFoo()' is deprecated: use bar()"},
  {"file": "Bar.swift", "line": 12, "column": 4, "type": "ActorIsolatedCall", "message": "Main actor-isolated initializer cannot be called from outside the actor"},
  {"file": "Calculator.swift", "line": 7, "column": 17, "type": "Swift Compiler Error", "message": "Some warning from Calculator"}
]
  • line / column are null when xcresult didn't emit them.
  • type values are the raw Apple issueType strings: Swift Compiler Warning, Swift Compiler Error, DeprecatedDeclaration, No-usage, ActorIsolatedCall, plus whatever new categories Apple adds.

--format list

One line per warning, grouped by file.

The #warning(...) quirk — important

Xcode mis-tags #warning("text") directives as type: "Swift Compiler Error" even though they're warnings and appear in peekie warnings output (not peekie errors).

The message for a #warning("Some text") directive is just the bare string passed to the directive — "Some text" — with no #warning wrapper, no quote marks, no syntactic giveaway. Don't try to detect them by grepping the message for #warning; the substring isn't there.

Default assumption: every entry with type == "Swift Compiler Error" in peekie warnings output is a #warning(...) developer marker, not a real defect. Real compiler errors land in peekie errors, not here. Treat the count of Swift Compiler Error entries as "TODO markers left in the source"; treat the other types as defects worth prioritizing.

Read the full file on GitHub · 106 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. 11d ago First seen · 106 lines · 147 tokens per session scan A 1a3ae02ac3cb

Subscribe to this mod's changes

peekie-warnings is a skill published in the GitHub repository dodobrands/Peekie (32 stars, last pushed 11d ago), licensed Apache-2.0. It adds 147 tokens to every session and 1,261 once invoked, about $0.0007 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-30.

Related

Other skills, from other repositories

swift-testing-expert

Expert guidance for Swift Testing: test structure, #expect/#require macros, traits and tags, parameterized tests, test plans, parallel execution, async waiting patterns, and XCTest migration. Use when writing new Swift tests, modernizing XCTest suites, debugging flaky tests, or improving test quality and…

AvdLee/Swift-Testing-Agent-Skill · 73 tokens

swift-testing

Expert guidance on Swift Testing best practices, patterns, and implementation. Use when developers mention: (1) Swift Testing, @Test, #expect, #require, or @Suite, (2) "use Swift Testing" or "modern testing patterns", (3) test doubles, mocks, stubs, spies, or fixtures, (4) unit tests, integration tests, or snapshot…

bocato/swift-testing-agent-skill · 124 tokens

Bun Test Runner

Fast test execution with Bun's built-in test runner including snapshot testing, mocking, code coverage, lifecycle hooks, DOM testing with happy-dom, and migration from Jest and Vitest to Bun test.

PramodDutta/qaskills · 44 tokens

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".

Terryc21/workflow-audit · 59 tokens

plan

Epic decomposition into trackable, right-sized tasks. Three modes — audit-aware (codebase-audit reports), workflow-audit-aware (handoff.yaml with pre-rated findings), standalone (from scratch). Light convention scanning for projects without CLAUDE.md.

Terryc21/workflow-audit · 53 tokens

swiftui-backports

Find SwiftUIBackports replacements for SwiftUI APIs unavailable on a project deployment target. Use for Swift/SwiftUI compiler availability errors, old iOS/tvOS/watchOS/macOS targets, or when implementing SwiftUI app features that may benefit from SwiftUIBackports.

shaps80/SwiftUIBackports · 60 tokens