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/usefulsoftwareco/executor/wrdn-effect-schema-inferred-typesnpx skills add UsefulSoftwareCo/executor --skill wrdn-effect-schema-inferred-typesgit clone --depth 1 https://github.com/UsefulSoftwareCo/executorWrote 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/usefulsoftwareco/executor/wrdn-effect-schema-inferred-types)<a href="https://agentmods.dev/skills/usefulsoftwareco/executor/wrdn-effect-schema-inferred-types"><img src="https://agentmods.dev/badge/skills/usefulsoftwareco/executor/wrdn-effect-schema-inferred-types.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 | $0.00061 | $0.00868 |
| Opus 5 | $0.00030 | $0.00434 |
| Sonnet 5 | $0.00012 | $0.00174 |
| Haiku 4.5 | $0.00006 | $0.00087 |
Grade A, and why
wrdn-effect-schema-inferred-types 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 3d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- wrdn-effect-schema-inferred-types — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You fix one pattern: a runtime Schema and a manual TypeScript type describe the same shape.
The preferred boundary is schema-first. Define the schema once, export type X = typeof XSchema.Type or type X = Schema.Schema.Type<typeof XSchema>, and make domain code consume the inferred type. This prevents drift between parsing and static types.
Trace before changing
- Find the runtime schema. Look for
Schema.Struct,Schema.Union,Schema.TaggedStruct,Schema.Record,Schema.Array, orSchema.decodeTo. - Find the duplicate static shape. A nearby
interface Xortype X = { ... }repeats the same fields, nullability, optionality, or literals. - Check export consumers. If callers import the type, keep the exported type name stable and change only its definition.
- Confirm the schema is the source of truth. If the manual type is wider/narrower than runtime parsing, decide whether the schema or consumers are wrong before replacing it.
- Handle recursion narrowly. Recursive schemas may need one private recursive helper type to annotate
Schema.suspend; keep exported domain types inferred from the schema.
Fix shape
- Move the schema before the exported type alias when needed.
- Replace duplicated exported interfaces with aliases derived from the schema:
export const SourceSchema = Schema.Struct({
id: SourceId,
name: Schema.String,
enabled: Schema.Boolean,
});
export type Source = typeof SourceSchema.Type;
- Use
Schema.Schema.Type<typeof XSchema>when it reads better for non-exported or generic schemas:
type IntrospectionResult = Schema.Schema.Type<typeof IntrospectionResultModel>;
- If using
Schema.decodeTo, infer the domain type from the decoded/domain schema, not from the raw transport schema. - Do not keep a manual interface solely for documentation. Add schema annotations or comments only when they clarify behavior the schema cannot express.
Bad
export interface StoredSource {
readonly id: string;
readonly url: string;
readonly headers: readonly Header[];
}
export const StoredSourceSchema = Schema.Struct({
id: Schema.String,
url: Schema.String,
headers: Schema.Array(HeaderSchema),
});
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.
- 3d ago First seen · 108 lines · 61 tokens per session scan A fb16c0db29b0
wrdn-effect-schema-inferred-types is a skill published in the GitHub repository UsefulSoftwareCo/executor (3,494 stars, last pushed yesterday), licensed MIT. It adds 61 tokens to every session and 868 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
client-setup
Create a vanilla tRPC client with createTRPCClient (), configure link chain with httpBatchLink/httpLink, dynamic headers for auth, transformer on links (not client constructor). Infer types with inferRouterInputs and inferRouterOutputs. AbortController signal support. TRPCClientError typing.
custom-features
Author a TanStack Table v9 feature plugin across every FeatureMap and API installation surface: state, options, column definitions, table, column, row, cell, header, row-model functions/caches, defaults, prototypes, and table/row/column instance data lifecycles. Load for initTableInstanceData, resetTableInstanceData…
effect-and-errors
Composing Effect programs, domain errors, HttpError, repository error types, or error propagation at HTTP boundaries.
migrate-better-result-3
Migrate a TypeScript codebase from better-result 2.x to 3.0. Use when upgrading better-result across the TaggedError syntax, removed Result serialization helpers, recovery inference, matching, or retry APIs.
fast-typescript-check
Keep www-sacred's TypeScript fast to type-check and fast to run. Use when touching the ASCII/canvas animation components (the only real per-frame code here), tightening type-check wall-clock, or auditing a change for runtime or compiler regressions. Scoped to this repo — a React 19 / Next.js 16 component library plus…
typescript-magician
Designs complex generic types, refactors any types to strict alternatives, creates type guards and utility types, and resolves TypeScript compiler errors. Use when the user asks about TypeScript (TS) types, generics, type inference, type guards, removing any types, strict typing, type errors, infer, extends…