Borrowing it
Nothing to install: this file belongs to erraggy/oastools. 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/erraggy/oastools/main/AGENTS.mdgit clone --depth 1 https://github.com/erraggy/oastoolsWrote 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/instructions/erraggy/oastools/agents-md)<a href="https://agentmods.dev/instructions/erraggy/oastools/agents-md"><img src="https://agentmods.dev/badge/instructions/erraggy/oastools/agents-md/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/instructions/erraggy/oastools/agents-md"><img src="https://agentmods.dev/badge/instructions/erraggy/oastools/agents-md.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.02242 | $0.02242 |
| Opus 5.5 | $0.00897 | $0.00897 |
| Sonnet 5.5 | $0.00448 | $0.00448 |
| Haiku 4.5 | $0.00224 | $0.00224 |
Grade A, and why
oastools AGENTS.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 1mo 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 — 265 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
This file provides quick, actionable guidance for AI coding agents working on the oastools project. For comprehensive details, see CLAUDE.md.
⚠️ BRANCH PROTECTION: The
mainbranch has push protections. Before making ANY changes, verify you're on a feature branch (git branch --show-current). If on main, create a branch first:git checkout -b <type>/<description>
Project Overview
oastools is a Go-based CLI tool for working with OpenAPI Specification (OAS) files. It supports parsing, validating, fixing, joining, converting, and comparing OAS documents across versions 2.0, 3.0.x, 3.1.x, and 3.2.0.
Module: github.com/erraggy/oastools
Go Version: 1.25+
Dev Environment Setup
CRITICAL: Install the pinned golangci-lint before making code changes:
make lint-install
export PATH=$PATH:$(go env GOPATH)/bin
The version lives in one place, GOLANGCI_VERSION in the Makefile, and CI reads
it from there. make lint refuses to run against any other version, because
findings would not match CI.
Quick Commands
# Build and test workflow (run after every code change)
make check # Runs tidy, fmt, lint, test, and git status
# Individual commands
make build # Build binary to bin/oastools
make test # Run all tests with cross-package coverage
make test-coverage # Generate and view HTML coverage report
make fmt # Format all Go code
make lint # Run golangci-lint (the version the Makefile pins)
# Benchmarks
make bench # Run benchmarks
make bench-save # Save new benchmark baseline (only if changes affect performance)
Testing Requirements
ALL exported functionality MUST have comprehensive tests:
- Positive cases (valid inputs work)
- Negative cases (errors handled correctly)
- Edge cases (nil, empty, boundary conditions)
- Integration cases (components work together)
Benchmark tests MUST use Go 1.24+ pattern:
func BenchmarkOperation(b *testing.B) {
// Setup
source, _ := parser.ParseWithOptions(...)
for b.Loop() { // ✅ Use b.Loop(), NOT for i := 0; i < b.N; i++
_, err := Operation(source)
if err != nil {
b.Fatal(err)
}
}
}
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.
- 1mo ago First seen · 265 lines · 2,242 tokens per session scan A e033e7df24d1
oastools AGENTS.md is an instructions file published in the GitHub repository erraggy/oastools (6 stars, last pushed 9d ago), licensed MIT. It adds 2,242 tokens to every session, about $0.0090 per session on Opus 5.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
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.