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 instructions/erraggy/oastools/copilot-instructionsgit clone --depth 1 https://github.com/erraggy/oastoolsWhat 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.04046 | $0.04046 |
| Opus 5 | $0.02023 | $0.02023 |
| Sonnet 5 | $0.00809 | $0.00809 |
| Haiku 4.5 | $0.00405 | $0.00405 |
Grade A, and why
oastools copilot-instructions.md 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.
How it starts
The opening of the file, as written. The whole thing — 442 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Copilot Instructions for oastools
This file provides guidance to GitHub Copilot when working with code in this repository.
How to Use This File
GitHub Copilot uses these instructions to:
- Understand the project structure, conventions, and best practices
- Make informed decisions when generating or modifying code
- Follow the same standards that human developers follow
- Avoid common pitfalls specific to this codebase
Read through all sections before making changes. Pay special attention to:
- Development Environment Setup - Install golangci-lint v2 before running
make check - Acceptance Criteria - Know when a task is truly complete
- Boundaries and Exclusions - Files and directories you should never modify
- Testing Requirements - All exported functionality must have comprehensive tests
- Benchmark Test Requirements - Use Go 1.24+
for b.Loop()pattern
Project Overview
oastools is a Go-based command-line tool for working with OpenAPI Specification (OAS) files. The primary goals are:
- Validating OpenAPI specification files
- Parsing and analyzing OAS documents
- Joining multiple OpenAPI specification documents
- Converting between OAS versions
- Comparing OAS documents and detecting breaking changes
Specification References
This tool supports the following OpenAPI Specification versions:
- OAS 2.0 (Swagger): https://spec.openapis.org/oas/v2.0.html
- OAS 3.0.x: https://spec.openapis.org/oas/v3.0.0.html through v3.0.4
- OAS 3.1.x: https://spec.openapis.org/oas/v3.1.0.html through v3.1.2
- OAS 3.2.0: https://spec.openapis.org/oas/v3.2.0.html
All OAS versions utilize the JSON Schema Specification Draft 2020-12: https://www.ietf.org/archive/id/draft-bhutton-json-schema-01.html
Key OpenAPI Specification Concepts
OAS Version Evolution
OAS 2.0 (Swagger) → OAS 3.0:
- Servers:
host,basePath, andschemes→ unifiedserversarray with URL templates - Components:
definitions,parameters,responses,securityDefinitions→components.* - Request Bodies:
consumes+ body parameter →requestBody.contentwith media types - Response Bodies:
produces+ schema →responses.*.contentwith media types - Security:
securityDefinitions→components.securitySchemeswith flows restructuring - New Features: Links, callbacks, and more flexible parameter serialization
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 · 442 lines · 4,046 tokens per session scan A 65aa34c8cee7
oastools copilot-instructions.md is an instructions file published in the GitHub repository erraggy/oastools (5 stars, last pushed 4d ago), licensed MIT. It adds 4,046 tokens to every session, about $0.0202 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 instructions, from other repositories
scalar AGENTS.md
Instructions for scalar/scalar, covering agents.md - ai agent guide for scalar, project overview, prerequisites, first-time setup and commands.
orval AGENTS.md
AGENTS.md instructions for orval-labs/orval, covering using vite+, the unified toolchain for the web, built-in commands vs scripts, tool versions and review checklist.
jentic-public-apis AGENTS.md
Instructions for jentic/jentic-public-apis, covering agents.md, repository structure, for ai coding agents, contributing and related standards.
lathe CLAUDE.md
Instructions for lathe-cli/lathe, covering claude.md, project intent, product positioning, source of truth and project structure.
apifable AGENTS.md
Instructions for ycs77/apifable, covering agents.md, keep this file strict, constraints, commands and rules.
scalar CLAUDE.md
Instructions for scalar/scalar, a project described as: Scalar is an open-source API platform: 🌐 Modern REST API Client 📖 Beautiful API References ✨ 1st-Class OpenAPI/Swagger Support.