Borrowing it
Nothing to install: this file belongs to JNZader/repoforge. 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/JNZader/repoforge/main/.claude/skills/backend/schemas/SKILL.mdgit clone --depth 1 https://github.com/JNZader/repoforgeWrote 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/jnzader/repoforge/schemas)<a href="https://agentmods.dev/skills/jnzader/repoforge/schemas"><img src="https://agentmods.dev/badge/skills/jnzader/repoforge/schemas/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/skills/jnzader/repoforge/schemas"><img src="https://agentmods.dev/badge/skills/jnzader/repoforge/schemas.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.00037 | $0.00451 |
| Opus 5 | $0.00018 | $0.00226 |
| Sonnet 5 | $0.00007 | $0.00090 |
| Haiku 4.5 | $0.00004 | $0.00045 |
Grade A, and why
define-request-response-schemas 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.
What it actually says
Define Request and Response Schemas
This skill covers the creation of Pydantic v2 request and response schemas.
Trigger: Load this skill when defining schemas for the RepoForge Web API.
Quick Reference
| Task | Pattern |
|---|---|
| Define user info schema | UserInfo |
| Create token response schema | TokenResponse |
Critical Patterns (Summary)
- User Info Schema: Defines the structure for user information.
- Token Response Schema: Specifies the format for token responses.
Critical Patterns (Detailed)
User Info Schema
Defines the structure for user information using Pydantic.
from apps.server.app.models.schemas import UserInfo
user_info = UserInfo(username="john_doe", email="[email protected]")
Token Response Schema
Specifies the format for token responses, ensuring proper validation.
from apps.server.app.models.schemas import TokenResponse
token_response = TokenResponse(access_token="abc123", token_type="bearer")
When to Use
- When creating API endpoints that require user information validation.
- When handling authentication responses in the RepoForge Web API.
Commands
docker-compose up
python repoforge/cli.py run
Anti-Patterns
Don't: Use Unvalidated Data
Using unvalidated data can lead to security vulnerabilities and data integrity issues.
# BAD
user_info = UserInfo(username="john_doe", email="not-an-email")
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 · 37 tokens per session scan A df48fdf26585
define-request-response-schemas is a skill published in the GitHub repository JNZader/repoforge (5 stars, last pushed 15d ago), licensed MIT. It adds 37 tokens to every session and 451 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-31.
Other skills, from other repositories
groq-inference
Ultra-fast LLM inference on custom LPU hardware. OpenAI-compatible API at api.groq.com. Lowest latency in the industry (500-1000+ tok/s). Supports chat completions, vision, audio (Whisper STT + TTS), tool calling, JSON mode, and streaming. Free tier available. Inference only — no training.
bun-file-io
Use this when you are working on file operations like reading, writing, scanning, or deleting files. It summarizes the preferred file APIs and patterns used in this repo. It also notes when to use filesystem helpers for directories.
protocolsio-integration
Integration with protocols.io API for managing scientific protocols. This skill should be used when working with protocols.io to search, create, update, or publish protocols; manage protocol steps and materials; handle discussions and comments; organize workspaces; upload and manage files; or integrate protocols.io…
opensrc
Fetch dependency source code to give AI agents deeper implementation context. Use when the agent needs to understand how a library works internally, read source code for a package, fetch implementation details for a dependency, or explore how an npm/PyPI/crates.io package is built. Triggers include "fetch source for"…
knowledge-shared-api-and-runtime-schemas
Shared request and response definitions for the server and web app, with runtime checks for incoming data and cleaned JSON schemas for tools. TypeBox is the library used to describe these data shapes.
arkcli-infer-endpoint
A manager for inference endpoints, the online addresses used to send requests to deployed AI models. It can work with endpoints created by the current SSO sub-user, which is a separately identified account user.