relay: Skill for Claude Code

.agents/skills/wrdn-effect-schema-boundaries/SKILL.md

wrdn-effect-schema-boundaries is a skill for Claude Code from adarshp14/relay. It costs 51 tokens per session (355 once invoked), scanned A, a copy of wrdn-effect-schema-boundaries, MIT.

A data-validation rule for converting unknown input into a known TypeScript shape with Effect Schema, named checks, or typed adapters. It focuses on validating data once where it enters an application.

In plain words
What is it for?
Validating API responses, configuration, JSON strings, and other untrusted or loosely typed values before domain code uses them.
Why use it?
It replaces repeated guesses, unsafe casts, and unvalidated JSON parsing with a clear check at the boundary. Code after that check can use reliable types.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: installed under .agents/ (shared by several agents).

This is adarshp14/relay's own configuration. It tells Claude Code how to work on relay itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything relay configures →

Reuse

Borrowing it

Nothing to install: this file belongs to adarshp14/relay. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/adarshp14/relay/main/.agents/skills/wrdn-effect-schema-boundaries/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/adarshp14/relay

Made for: Claude Code.

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 wrdn-effect-schema-boundaries

README.md
[![agentmods](https://agentmods.dev/badge/skills/adarshp14/relay/wrdn-effect-schema-boundaries/github.svg)](https://agentmods.dev/skills/adarshp14/relay/wrdn-effect-schema-boundaries)
Your own site
<a href="https://agentmods.dev/skills/adarshp14/relay/wrdn-effect-schema-boundaries"><img src="https://agentmods.dev/badge/skills/adarshp14/relay/wrdn-effect-schema-boundaries/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 wrdn-effect-schema-boundaries

Your own site · 80×15
<a href="https://agentmods.dev/skills/adarshp14/relay/wrdn-effect-schema-boundaries"><img src="https://agentmods.dev/badge/skills/adarshp14/relay/wrdn-effect-schema-boundaries.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 51 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 355 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.
Origin 100% copy Near-identical to another mod 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.00051 $0.00355
Opus 5.5 $0.00020 $0.00142
Sonnet 5.5 $0.00010 $0.00071
Haiku 4.5 $0.00005 $0.00036

Measured 1mo ago against content hash aae568a8b337, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

wrdn-effect-schema-boundaries 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 1mo 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.

Origin

This is a copy

100% identical to wrdn-effect-schema-boundaries — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.agents/skills/wrdn-effect-schema-boundaries/SKILL.md · 45 lines

What it actually says

You fix one pattern: domain code is asserting or probing an unknown shape instead of parsing it once at the boundary.

Fix Shape

  • Prefer Schema.decodeUnknownEffect(MySchema)(value) for untrusted input.
  • Prefer Schema.decodeUnknownEffect(Schema.fromJsonString(MySchema))(text) or Schema.decodeUnknownOption(Schema.parseJson())(text) for JSON strings.
  • Keep domain code typed after the decode; do not keep unknown and probe it repeatedly.
  • Replace JSON.parse, value as string, as unknown as X, as Record<string, unknown>, inline object assertions, "field" in value, and Reflect.get with a schema, typed adapter, or named guard.
  • A named guard is acceptable only when parsing is not the right abstraction and the guard has a precise return type.

Good

const ParsedConfig = Schema.Struct({
  endpoint: Schema.String,
});

const config = yield * Schema.decodeUnknownEffect(ParsedConfig)(raw);
const config = yield * Schema.decodeUnknownEffect(Schema.fromJsonString(ParsedConfig))(rawText);

Bad

const config = raw as unknown as { endpoint: string };
const config = JSON.parse(rawText) as { endpoint: string };
const pattern = updated.pattern as string;
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. 1mo ago First seen · 45 lines · 51 tokens per session scan A aae568a8b337

Subscribe to this mod's changes

wrdn-effect-schema-boundaries is a skill published in the GitHub repository adarshp14/relay (0 stars, last pushed 4mo ago), licensed MIT. It adds 51 tokens to every session and 355 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to wrdn-effect-schema-boundaries, differing in 0 lines, and is treated as a copy.

Related

Other skills, from other repositories

webiny-api-cms-custom-field-type

How to implement a custom CMS field type that integrates with the model builder's fluent API. Covers extending DataFieldBuilder, composing validator interfaces, creating a FieldTypeFactory, registering via DI, and module augmentation for TypeScript autocomplete on the fields() registry.

webiny/webiny-js · 60 tokens

nodejs-sdk

Type-safe Node.js API client SDK with validation, mocking, retry, and logging. Use when building API clients for Node.js applications.

pontjs/pontx · 31 tokens

graphql-api-development

Comprehensive guide for building GraphQL APIs including schema design, queries, mutations, subscriptions, resolvers, type system, error handling, authentication, authorization, caching strategies, and production best practices.

manutej/luxor-claude-marketplace · 42 tokens

node

Provides domain-specific best practices for Node.js development with TypeScript, covering type stripping, async patterns, error handling, streams, modules, testing, performance, caching, logging, and more. Use when setting up Node.js projects with native TypeScript support, configuring type stripping…

ushibo/brigade · 162 tokens

fastify-best-practices

Guides development of Fastify Node.js backend servers and REST APIs using TypeScript or JavaScript. Use when building, configuring, or debugging a Fastify application — including defining routes, implementing plugins, setting up JSON Schema validation, handling errors, optimising performance, managing authentication…

ushibo/brigade · 137 tokens

fastapi

FastAPI best practices and conventions. Use when working with FastAPI APIs, Pydantic models, dependencies, streaming responses including Server-Sent Events (SSE), and serving frontend apps. Keeps FastAPI code clean and up to date with the latest features and patterns.

fastapi/fastapi · 57 tokens