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 agentmods add skills/getsentry/xcodebuildmcp/wardennpx skills add getsentry/XcodeBuildMCP --skill wardengit clone --depth 1 https://github.com/getsentry/XcodeBuildMCPWhat 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 | $0.00060 | $0.00609 |
| Opus 5 | $0.00030 | $0.00304 |
| Sonnet 5 | $0.00012 | $0.00122 |
| Haiku 4.5 | $0.00006 | $0.00061 |
Grade A, and why
warden 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.
How it starts
The opening of the file, as written. The whole thing — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Run Warden to analyze code changes before committing.
References
Read the relevant reference when the task requires deeper detail:
| Document | Read When |
|---|---|
${CLAUDE_SKILL_ROOT}/references/cli-reference.md |
Full option details, per-command flags, examples |
${CLAUDE_SKILL_ROOT}/references/configuration.md |
Editing warden.toml, triggers, patterns, troubleshooting |
${CLAUDE_SKILL_ROOT}/references/config-schema.md |
Exact field names, types, and defaults |
${CLAUDE_SKILL_ROOT}/references/creating-skills.md |
Writing custom skills, remote skills, skill discovery |
Running Warden
# Analyze uncommitted changes (uses warden.toml triggers)
warden
# Run a specific skill
warden --skill <skill-name>
# Analyze specific files
warden src/auth.ts src/database.ts
# Analyze changes from a git ref
warden main..HEAD
warden HEAD~3
# Auto-apply suggested fixes
warden --fix
# Fail on high-severity findings
warden --fail-on high
Set WARDEN_ANTHROPIC_API_KEY or log in via claude login before running.
Pre-Commit Workflow
After making code changes and before committing:
- Run
wardento analyze uncommitted changes - Review the findings
- Fix issues Warden reports (or use
warden --fixto auto-apply) - Commit the changes
Run Warden once to validate work. Do not loop re-running Warden on the same changes.
Reading Output
Severity levels:
high- Must fix before mergemedium- Worth reviewinglow- Minor improvement
Exit codes: 0 = no findings at or above fail threshold. 1 = findings at or above fail threshold.
Verbosity: -v shows real-time findings. -vv shows debug info (tokens, latency). -q shows errors and summary only.
Commands
| Command | Description |
|---|---|
warden |
Run analysis (default) |
warden init |
Initialize warden.toml and GitHub workflow |
warden add [skill] |
Add skill trigger to warden.toml |
warden sync [remote] |
Update cached remote skills |
warden setup-app |
Create GitHub App via manifest flow |
What ships with it
4 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.
- 2d ago First seen · 77 lines · 60 tokens per session scan A f521ff421145
warden is a skill published in the GitHub repository getsentry/XcodeBuildMCP (6,316 stars, last pushed yesterday), licensed MIT. It adds 60 tokens to every session and 609 once invoked, about $0.0003 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.
Other skills, from other repositories
opik-diagnose
Surface the Opik traces worth a developer's attention, ranked by signal — errors, failed tool calls, latency, regressions, and low online-eval scores — plus Diagnostics issues. Reads live/production traces via the SDK (searchtraces and agentinsights) and works with no MCP; uses the MCP issue entity when connected.…
client-scripts
Write ServiceNow client scripts (onLoad/onChange/onSubmit/onCellEdit) using gform, guser, GlideAjax, field visibility/mandatory toggles, and validation with debounced server calls.
agoragentic-transaction-assurance
Prepare, evaluate, and reconcile autonomous agent transactions without self-granting payment or owner authority. Use when an agent must bind principal authority, seller terms, payment evidence, execution, delivered outcome, and reconciliation; handle paid retries safely; or prepare an authority request for owner…
linkding
Manage bookmarks with Linkding. Use when the user asks to "save a bookmark", "add link", "search bookmarks", "list my bookmarks", "find saved links", "tag a bookmark", "archive bookmark", "check if URL is saved", "list tags", "create bundle", or mentions Linkding bookmark management.
maya-shot-export
Pipeline stage — shot-level export: frame ranges, cameras, FBX / Alembic packaging for editorial. Use when packaging shot data for downstream departments. Not for full pipeline publish (maya-pipeline) or scene assembly (maya-scene-assembly).
daily-task-prep
Morning preparation. Calendar lookahead, meeting context loading, open threads from yesterday, active task review. Extends briefing with actionable prep.