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/mohitgoyal09/agentforge/api-interface-designnpx skills add MohitGoyal09/AgentForge --skill api-interface-designgit clone --depth 1 https://github.com/MohitGoyal09/AgentForgeWhat 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.00023 | $0.00173 |
| Opus 5 | $0.00012 | $0.00086 |
| Sonnet 5 | $0.00005 | $0.00035 |
| Haiku 4.5 | $0.00002 | $0.00017 |
Grade A, and why
api-interface-design 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 2d 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
API Interface Design
Design the contract before the implementation.
Use This For
- REST, GraphQL, or SDK interface design
- Tool parameter schemas
- Provider adapter boundaries
- Data exchanged between the agent loop, tools, and persistence
Principles
- Prefer additive changes over breaking existing fields.
- Use one predictable error shape.
- Validate external input at the boundary.
- Keep internal call sites typed and boring.
- Treat every observable behavior as something users may depend on.
Checklist
- Inputs and outputs are typed.
- Error semantics are consistent.
- Optional fields are truly optional.
- New behavior has at least one success test and one failure test.
- Docs show the smallest working example.
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.
- 2d ago First seen · 32 lines · 23 tokens per session scan A 069ba82f9866
api-interface-design is a skill published in the GitHub repository MohitGoyal09/AgentForge (61 stars, last pushed 2mo ago), licensed MIT. It adds 23 tokens to every session and 173 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-30.
Other skills, from other repositories
agent-framework-py-release
Use when cutting a Python release for the microsoft/agent-framework monorepo. Triggers on "bump py versions", "cut a python release", "prepare release PR for python", "release py packages", "bump python to X.Y.Z", or similar requests to bump Python package versions and prepare a release PR. Handles all four lifecycle…
python-package-management
Guide for managing packages in the Agent Framework Python monorepo, including creating new connector packages, versioning, and the lazy-loading pattern. Use this when adding, modifying, or releasing packages.
foundry-hosted-agent-validation
Step-by-step process for validating a Python Foundry hosted agent sample (under python/samples/04-hosting/foundry-hosted-agents/) end to end — running it locally (native runtime and azd ai agent run) and after deploying it to an Azure AI Foundry project with azd. Use this when asked to validate a hosted agent sample.
verify-samples-tool
How to use the verify-samples tool to run, verify, and manage sample definitions in the Agent Framework repository. Use this when adding, updating, or running sample verification.
build-and-test
How to build and test .NET projects in the Agent Framework repository. Use this when verifying or testing changes.
python-feature-lifecycle
Guidance for package and feature lifecycle in the Agent Framework Python codebase, including stage meanings, feature-stage decorators, feature enums, and how to move APIs from one stage to the next.