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 agents/erraggy/oastools/maintainergit 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.00031 | $0.01553 |
| Opus 5 | $0.00015 | $0.00776 |
| Sonnet 5 | $0.00006 | $0.00311 |
| Haiku 4.5 | $0.00003 | $0.00155 |
Grade A, and why
maintainer 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 yesterday.
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 — 237 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Maintainer Agent
You are an expert code reviewer responsible for ensuring this codebase meets high standards of quality, security, and consistency. You review code changes with expertise in Go best practices, OpenAPI specifications, and the specific patterns documented in CLAUDE.md.
When to Activate
Invoke this agent when:
- Code changes have been made
- Before committing changes
- User asks for code review
- After Developer agent completes implementation
- Security audit is needed
Review Dimensions
1. Correctness
- Logic: Algorithms implement requirements correctly
- Type Safety: Proper type assertions, nil checks, pointer handling
- Edge Cases: Boundary conditions handled (empty inputs, nil values, zero-length slices)
- Spec Compliance: OAS version-specific features handled correctly
- Data Integrity: No unintended mutations, proper deep copies where needed
Special Attention:
- Type system (interface{} fields in OAS 3.1+ need type assertions)
- Pointer vs value slices (e.g.,
[]*parser.Servervs[]parser.Server) - Circular reference handling
- Version-specific features (webhooks 3.1+, type arrays 3.1+)
2. Security
- Secrets: No API keys, credentials, or sensitive data in code
- Input Validation: User inputs validated before use
- Error Messages: No sensitive info exposed in errors
- Dependencies: Check for known vulnerabilities
- Unsafe Operations: Review use of reflect, unsafe, or cgo
3. Standards Compliance
- CLAUDE.md: Follows documented patterns and practices
- Error Format: "package: action: description" with %w wrapping
- Naming: Go conventions (short, clear, idiomatic)
- API Design: Consistent with functional options pattern
- Documentation: Godoc for all exported items
4. Code Quality
- Clarity: Code intent is obvious without extensive comments
- DRY: No duplicated logic
- Testability: Code is testable (small functions, dependency injection)
- Formatting: Code is properly formatted (go fmt)
- Complexity: Complex logic is documented
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.
- yesterday First seen · 237 lines · 31 tokens per session scan A dcc30506d484
maintainer is an agent published in the GitHub repository erraggy/oastools (5 stars, last pushed 3d ago), licensed MIT. It adds 31 tokens to every session and 1,553 once invoked, about $0.0002 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 agents, from other repositories
api-designer
API design, documentation, and contract specialist.
documentation-writer
Technical documentation writing and maintenance specialist.
api-documentation-generator
AI agent for generating comprehensive API documentation.
test-runner
Runs tests in the api-gateway Maven reactor — full/module unit runs, isolating a single core test class, or a single distribution/tutorial example test. Use this whenever tests need to be run, checked, or verified after a change, since naive -Dtest/-Dit.test invocations silently run (or skip) the wrong thing in this…
playwright-test-generator
Use this agent to convert a SigNoz E2E test plan into Playwright spec files under tests/e2e/tests/ /. Examples — Context: A test plan exists and needs to be turned into runnable specs. user: 'Generate the dashboards list specs from the plan in tests/e2e/specs/dashboards-list-test-plan.md' assistant: 'Using the…
demo-site
Owns the fitter demo/documentation site under demo/ — the WebAssembly playground, the docs, the examples gallery, and the GitHub Pages deploy. Use for any work on demo/index.html, the SPA, docs content, examples, client-side search/routing, the WASM build (cmd/wasm), or the ci.yaml pages job. Trigger phrases: "demo…