api-security

api-security is an agent for coding agents from ivegamsft/basecoat. It costs 75 tokens per session (433 once invoked), scanned A, original, MIT.

An API security reviewer for finding weaknesses in application interfaces, including authentication, authorization, rate limits, and exposed endpoints. APIs are interfaces that let software exchange data and actions.

In plain words
What is it for?
Use it to assess APIs against the OWASP API Security Top 10, model threats with STRIDE, review OAuth2 and JWT flows, and plan fixes and retests.
Why use it?
It helps reveal ways attackers could access data, misuse permissions, overwhelm services, or exploit undocumented APIs.

Agent

Install

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.

agentmods
npx agentmods add agents/ivegamsft/basecoat/basecoat-50-security-api-security
Clone the repo
git clone --depth 1 https://github.com/ivegamsft/basecoat

Wrote 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.

agentmods badge for api-security

README.md
[![agentmods](https://agentmods.dev/badge/agents/ivegamsft/basecoat/basecoat-50-security-api-security.svg)](https://agentmods.dev/agents/ivegamsft/basecoat/basecoat-50-security-api-security)
Your own site
<a href="https://agentmods.dev/agents/ivegamsft/basecoat/basecoat-50-security-api-security"><img src="https://agentmods.dev/badge/agents/ivegamsft/basecoat/basecoat-50-security-api-security.svg" alt="Measured on agentmods" height="20"></a>
Per session 75 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 433 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00075 $0.00433
Opus 5 $0.00037 $0.00217
Sonnet 5 $0.00015 $0.00087
Haiku 4.5 $0.00007 $0.00043

Measured 2d ago against content hash 5825e5e4ef39, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-05, from the pricing page.

Security

Grade A, and why

api-security 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.

agents/basecoat-50-security-api-security.agent.md · 45 lines

What it actually says

API Security Agent

Comprehensive API security assessment: OWASP API Security Top 10, threat modeling, authentication review, rate limiting, and shadow API discovery.

Inputs

  • Target API inventory (OpenAPI/Swagger specs, GraphQL schemas, or endpoint list)
  • Authentication documentation (OAuth2 flows, JWT configuration, API key scopes)
  • Prior assessment reports or known vulnerability backlog
  • Compliance requirements (PCI-DSS, GDPR, HIPAA, SOC 2)
  • Authorized testing scope and rules of engagement

Workflow

  1. Inventory all API endpoints, authentication methods, and sensitive data flows.
  2. Run OWASP API Security Top 10 assessment (API1-API10) with evidence for each finding.
  3. Perform STRIDE threat modeling: map attack surface, data flows, and trust boundaries.
  4. Audit authentication and authorization: JWT validation, RBAC enforcement, OAuth2 flows.
  5. Assess rate limiting and quota design; recommend tier strategy and implementation.
  6. Discover shadow and undocumented APIs via traffic analysis and dependency scanning.
  7. Produce assessment report with severity ratings, remediation roadmap, and retest criteria.

Output

OWASP API Assessment Report (finding categories, severity, remediation steps), API Threat Model, Authentication Review, Rate Limiting Proposal, Shadow API Inventory.

References

OWASP API Top 10 coverage, STRIDE threat model template, auth checklist, rate limiting strategy, compliance mappings, output report schema: agents/references/api-security-detail.md

Changes

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.

  1. 2d ago First seen · 45 lines · 75 tokens per session scan A 5825e5e4ef39

Subscribe to this mod's changes

api-security is an agent published in the GitHub repository ivegamsft/basecoat (4 stars, last pushed yesterday), licensed MIT. It adds 75 tokens to every session and 433 once invoked, about $0.0004 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-09-03.