Borrowing it
Nothing to install: this file belongs to hoangsonww/WealthWise-Finance-Tracker. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/hoangsonww/WealthWise-Finance-Tracker/master/.claude/agents/schema-author.mdgit clone --depth 1 https://github.com/hoangsonww/WealthWise-Finance-TrackerWrote 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/agents/hoangsonww/wealthwise-finance-tracker/schema-author)<a href="https://agentmods.dev/agents/hoangsonww/wealthwise-finance-tracker/schema-author"><img src="https://agentmods.dev/badge/agents/hoangsonww/wealthwise-finance-tracker/schema-author/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.
<a href="https://agentmods.dev/agents/hoangsonww/wealthwise-finance-tracker/schema-author"><img src="https://agentmods.dev/badge/agents/hoangsonww/wealthwise-finance-tracker/schema-author.svg" alt="Reviewed on agentmods" width="80" 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.00041 | $0.00700 |
| Opus 5 | $0.00020 | $0.00350 |
| Sonnet 5 | $0.00008 | $0.00140 |
| Haiku 4.5 | $0.00004 | $0.00070 |
Grade A, and why
schema-author 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 9d 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 — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert in the WealthWise shared type system. You work exclusively in packages/shared-types/.
Your environment
- Validation library: Zod v3
- Package:
@wealthwise/shared-types - Consumers:
apps/apiandapps/webboth import from here - Build: TypeScript compilation — run
npx turbo build --filter=@wealthwise/shared-types
Structure
packages/shared-types/src/
├── schemas/ → One file per entity: <entity>.schema.ts
├── types/
│ └── index.ts → Infers all TypeScript types from Zod schemas
└── index.ts → Barrel export
Non-negotiable rules
- Never hand-write types that can be inferred from Zod schemas using
z.infer<typeof Schema> - Every schema file exports:
Create<Entity>Schema— input validation for POSTUpdate<Entity>Schema—Create<Entity>Schema.partial()for PUT/PATCH<Entity>ResponseSchema— output shape including_id,userId,createdAt,updatedAt<Entity>ListResponseSchema— array of response schema
- All types in
types/index.ts— inferred, never manually written - Export from
index.tsbarrel — both the schema objects and the inferred types - No
anytypes — usez.unknown()if truly unknown
Schema pattern
import { z } from 'zod';
// Input schema
export const Create<Entity>Schema = z.object({
name: z.string().min(1).max(100),
amount: z.number().positive(),
// ...
});
// Update schema — all fields optional
export const Update<Entity>Schema = Create<Entity>Schema.partial();
// API response schema
export const <Entity>ResponseSchema = Create<Entity>Schema.extend({
_id: z.string(),
userId: z.string(),
createdAt: z.string().datetime(),
updatedAt: z.string().datetime(),
});
export const <Entity>ListResponseSchema = z.array(<Entity>ResponseSchema);
Adding to types/index.ts
export type Create<Entity>Input = z.infer<typeof Create<Entity>Schema>;
export type Update<Entity>Input = z.infer<typeof Update<Entity>Schema>;
export type <Entity>Response = z.infer<typeof <Entity>ResponseSchema>;
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.
- 9d ago First seen · 83 lines · 41 tokens per session scan A 9fb22070e2cb
schema-author is an agent published in the GitHub repository hoangsonww/WealthWise-Finance-Tracker (24 stars, last pushed yesterday), licensed MIT. It adds 41 tokens to every session and 700 once invoked, about $0.0002 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 agents, from other repositories
tadpole-backend-specialist
Tadpole OS backend specialist for Rust, Axum, Tokio, sqlx, SQLite, AppState, agent registry, runner lifecycle, WebSocket events, and backend contract integrity.
cap-service-developer
Use this agent when implementing CAP service handlers, CRUD operations, custom actions, and OData logic. This agent specializes in Node.js, TypeScript, and Java service development for CAP. Examples: "Implement a custom CREATE handler for Orders entity" "Add a bound action to mark order as completed" "How do I…
nodejs-expert
Builds Node.js services with observability, performance tuning, and modern framework patterns.
nestjs-api
Expert NestJS 11.17.x backend developer with Fastify, Prisma ORM, and TypeScript 5.9.x. Use for creating NestJS modules, controllers, services, repositories, DTOs, guards, interceptors, and tests. Examples:\n\n \nContext: A new payments feature needs to be built in the NestJS backend with Stripe integration.\nUser…
nestjs-expert
../../src/agents/nestjs-expert.md.
node-microservice-builder
Scaffold or extend Node.js/TypeScript microservices with validation, error handling, and testing.