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/groupzer0/vs-code-agents/cross-repo-contractnpx skills add groupzer0/vs-code-agents --skill cross-repo-contractgit clone --depth 1 https://github.com/groupzer0/vs-code-agentsWrote 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/groupzer0/vs-code-agents/cross-repo-contract)<a href="https://agentmods.dev/skills/groupzer0/vs-code-agents/cross-repo-contract"><img src="https://agentmods.dev/badge/skills/groupzer0/vs-code-agents/cross-repo-contract.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.1 | $0.00000 | $0.00568 |
| Opus 5 | $0.00000 | $0.00284 |
| Sonnet 5 | $0.00000 | $0.00114 |
| Haiku 4.5 | $0.00000 | $0.00057 |
Grade A, and why
cross-repo-contract 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 6d 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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cross-Repository API Contract Skill
Purpose
When implementing or consuming APIs that span multiple repositories, ensure type safety and contract adherence by working with locally available contract definitions.
Contract Discovery
Before implementing any API endpoint or client, check for contract definitions in these locations (in order of precedence):
api-contract/— This repo is the source of truth for the contract.contracts/— Synced copy from an external source repo (typically via CI)
If neither exists and you are implementing API endpoints, propose creating an api-contract/ directory following the standard structure.
Standard Contract Structure
api-contract/ (or .contracts/)
├── README.md # Purpose, sync instructions, change process
├── version.ts # Contract version and changelog
├── types.ts # TypeScript interfaces for all request/response/error shapes
└── endpoints.md # Human-readable endpoint documentation
Implementation Guidelines
When Implementing API Endpoints (Backend)
- Read
.contracts/types.ts(orapi-contract/types.ts) before writing handler code - Import or reference the types directly — do not redefine them
- Validate that Lambda/function request and response shapes match the contract exactly
- If the contract is missing fields you need, document as an OPEN QUESTION — do not add fields unilaterally
When Implementing API Clients (Extension/Frontend)
- Read
api-contract/types.tsbefore writing client code - Import types directly from the contract location
- Handle all error codes defined in the contract
- If the API behaves differently than the contract specifies, flag this as a bug
When Proposing Contract Changes
- Additive changes (new optional fields, new endpoints): Safe to propose inline
- Breaking changes (removing fields, changing types): Document as OPEN QUESTION with migration notes
- Always bump the version in
version.tswhen modifyingtypes.ts - Note that breaking changes require coordinated releases across repos
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.
- 6d ago First seen · 65 lines · 0 tokens per session scan A aa3d81551f95
cross-repo-contract is a skill published in the GitHub repository groupzer0/vs-code-agents (284 stars, last pushed 7mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 568 tokens. 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…