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/adarshp14/relay/wrdn-effect-schema-boundariesnpx skills add adarshp14/relay --skill wrdn-effect-schema-boundariesgit clone --depth 1 https://github.com/adarshp14/relayWrote 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/adarshp14/relay/wrdn-effect-schema-boundaries)<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="Measured on agentmods" 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.00051 | $0.00355 |
| Opus 5 | $0.00026 | $0.00178 |
| Sonnet 5 | $0.00010 | $0.00071 |
| Haiku 4.5 | $0.00005 | $0.00036 |
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 5d 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.
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.
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)orSchema.decodeUnknownOption(Schema.parseJson())(text)for JSON strings. - Keep domain code typed after the decode; do not keep
unknownand probe it repeatedly. - Replace
JSON.parse,value as string,as unknown as X,as Record<string, unknown>, inline object assertions,"field" in value, andReflect.getwith 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;
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.
- 5d ago First seen · 45 lines · 51 tokens per session scan A aae568a8b337
wrdn-effect-schema-boundaries is a skill published in the GitHub repository adarshp14/relay (0 stars, last pushed 2mo ago), licensed MIT. It adds 51 tokens to every session and 355 once invoked, about $0.0003 per session on Opus 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.
Other skills, from other repositories
typescript
Write clear, predictable TypeScript and Vue TypeScript code with strong typing, maintainability, and consistent documentation conventions.
refactor
Refactor Java code in this repo without changing behavior. Not for bug fixes or new features.
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.
skmtc-lang-typescript
The TypeScript target-language layer for Skmtc generators (@skmtc/lang-typescript): projection base factories, TsSnippet, the three register shapes, identifier kinds and the type-only import machinery, composition helpers, sanitization, TsFile render rules. Use ALONGSIDE skmtc-generator whenever a generator emits…
golang
Rules and best practices when writing and editing Go (Golang) code.
gram-pubsub-python
How to build and run GCP Pub/Sub stream subscribers in Python under pystreams/ — the multi command (start at pystreams/src/pystreams/cmd/multi.py), the graminfra.pubsub publisher/subscriber library, and the anyio runtime mirroring the Go gram streams process. Activate for ANY Python Pub/Sub work in Gram: adding or…