interface-definition

interface-definition is a skill for Claude Code, Codex from paruff/uFawkesAI. It costs 24 tokens per session (765 once invoked), scanned A, original, MIT.

A specification tool for defining how software components communicate through APIs, data models, events, and integrations.

In plain words
What is it for?
Use it to document HTTP endpoints, message or event formats, database-style data relationships, webhooks, and other integration contracts.
Why use it?
It removes ambiguity between components by recording requests, responses, data fields, errors, authentication, and event responsibilities.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/paruff/ufawkesai/interface-definition
Any agent
npx skills add paruff/uFawkesAI --skill interface-definition
Clone the repo
git clone --depth 1 https://github.com/paruff/uFawkesAI

Made for: Claude Code, Codex.

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 interface-definition

README.md
[![agentmods](https://agentmods.dev/badge/skills/paruff/ufawkesai/interface-definition.svg)](https://agentmods.dev/skills/paruff/ufawkesai/interface-definition)
Your own site
<a href="https://agentmods.dev/skills/paruff/ufawkesai/interface-definition"><img src="https://agentmods.dev/badge/skills/paruff/ufawkesai/interface-definition.svg" alt="Measured on agentmods" height="20"></a>
Per session 24 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 765 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found 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.00024 $0.00765
Opus 5 $0.00012 $0.00382
Sonnet 5 $0.00005 $0.00153
Haiku 4.5 $0.00002 $0.00076

Measured 5d ago against content hash 22274b46a14b, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-05, from the pricing page.

Security

Grade A, and why

interface-definition 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.

.agents/skills/design/interface-definition/SKILL.md · 136 lines

How it starts

The opening of the file, as written. The whole thing — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Skill: Interface Definition

Load trigger: "load interface-definition skill" > DORA: Cap 3 (AI-Accessible Internal Data) Token cost: Low

Purpose

Define interfaces between components.

Responsibilities

  • Define API endpoints
  • Define data models
  • Define event schemas
  • Define integration points

Inputs

  • component-map.json (from component-identification skill)
  • specification.md

Outputs

  • interfaces.json

Definition Rules

API Endpoints

  • HTTP method defined (GET, POST, PUT, DELETE, PATCH)
  • Path defined with versioning (e.g., /api/v1/resource)
  • Request body schema defined
  • Response body schema defined
  • Error responses defined (4xx, 5xx)
  • Authentication requirements specified

Data Models

  • All fields defined with types
  • Required vs optional fields marked
  • Default values specified
  • Validation rules specified
  • Relationships defined (has-many, belongs-to)

Event Schemas

  • Event type/name defined
  • Event payload defined
  • Producer identified
  • Consumer(s) identified
  • Delivery guarantees specified

Integration Points

  • External API contracts defined
  • Webhook formats defined
  • Message queue formats defined
  • File format contracts defined

API Design Standards

Standard Convention
Versioning URL path (/api/v1/)
Naming kebab-case for paths, camelCase for JSON
Pagination ?page=1&limit=20 or cursor-based
Errors { "error": { "code": "string", "message": "string" } }
Timestamps ISO 8601 format

Output Format

{
  "apis": [
    {
      "name": "User API",
      "base_url": "/api/v1/users",
      "endpoints": [
        {
          "method": "POST",
          "path": "/",
          "request": {
            "email": "string",
            "password": "string"  # pragma: allowlist secret
          },
          "response": {
            "id": "string",
            "email": "string",
            "created_at": "string"
          },
          "errors": [400, 409, 500],
          "auth": "none"
        }
      ]
    }
  ],
  "models": [
    {
      "name": "User",
      "fields": {
        "id": "string (uuid)",
        "email": "string (email)",
        "created_at": "string (iso8601)"
      }
    }
  ],
  "events": [
    {
      "type": "user.created",
      "producer": "User API",
      "consumers": ["Email Worker"],
      "payload": {
        "user_id": "string",
        "email": "string"
      }
    }
  ]
}

Read the full file on GitHub · 136 lines

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. 5d ago First seen · 136 lines · 24 tokens per session scan A 22274b46a14b

Subscribe to this mod's changes

interface-definition is a skill published in the GitHub repository paruff/uFawkesAI (2 stars, last pushed 13d ago), licensed MIT. It adds 24 tokens to every session and 765 once invoked, about $0.0001 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.

Related

Other skills, from other repositories

planning-with-files

Persistent file-based planning for multi-step AI-agent work. Keeps taskplan.md, findings.md, and progress.md on disk; lifecycle hooks inject selected project planning context. Automatic recovery reads project planning files only. Explicit session-catchup.py --metadata reads same-project local agent session records and…

mxyhi/ok-skills · 117 tokens

infrastructure-overview

Top-level skill for the research template infrastructure layer. Use in Cursor, Claude Code, or similar agents when editing or importing anything under infrastructure/, understanding the two-layer architecture, or wiring build/validation/rendering/publishing. Covers module discovery, import patterns, thin…

docxology/template · 80 tokens

infrastructure-validation

Skill for the validation infrastructure module providing PDF validation, markdown validation, output integrity checks, link verification, documentation audits, issue categorization, and repository scanning. Use when validating research outputs, checking document quality, running audits, or verifying cross-references.

docxology/template · 54 tokens

infrastructure-llm

Skill for the LLM infrastructure module providing local Large Language Model integration via Ollama. Covers client initialization, prompt templates, output validation, manuscript review generation, conversation context, and CLI usage. Use when querying LLMs, generating manuscript reviews, validating LLM outputs, or…

docxology/template · 66 tokens

research-workflow

Seven-stage research workflow (SCOPE→LITERATURE→REASON→DESIGN→COMPUTE→SYNTHESIZE→WRITE). Use for: structuring an AI agent's research process, generating literature review prompts, scoping methodology. Usage: from infrastructure.research import ResearchWorkflow; ResearchWorkflow.describe() Config: set stage overrides…

docxology/template · 91 tokens

infrastructure-search-literature

Paperclip-style multi-source literature search across arXiv, Crossref, local JSON corpora, and (opt-in) the Paperclip API. Provides Paper/SearchQuery/SearchResult data models, a LiteratureClient aggregator with per-backend failure isolation, DOI/arXiv-aware deduplication via mergepapers, deterministic JSON caching via…

docxology/template · 123 tokens