analyzing-api-gateway-access-logs

analyzing-api-gateway-access-logs is a skill for Claude Code from plurigrid/asi. It costs 72 tokens per session (469 once invoked), scanned A, a copy of analyzing-api-gateway-access-logs, MIT.

An API-log analysis workflow for AWS API Gateway, Kong, and Nginx access logs. It looks for patterns such as BOLA, where a user accesses another user's object, rate-limit bypasses, credential scanning, and injection attempts.

In plain words
What is it for?
Use it to investigate attacks, detect suspicious resource-ID enumeration, analyze request behavior, and build API threat-detection rules.
Why use it?
It helps turn large request logs into evidence of API abuse and unusual access patterns.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the asi plugin — 56 skills shipped together

Good fit Use it to investigate attacks, detect suspicious resource-ID enumeration, analyze request behavior, and build API threat-detection rules.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/plurigrid/asi/analyzing-api-gateway-access-logs
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.

Any agent
npx skills add plurigrid/asi --skill analyzing-api-gateway-access-logs
Clone the repo
git clone --depth 1 https://github.com/plurigrid/asi

Made for: Claude Code.

Or install asi, the plugin that ships this one along with the rest of its 56 skills.

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 analyzing-api-gateway-access-logs

README.md
[![agentmods](https://agentmods.dev/badge/skills/plurigrid/asi/analyzing-api-gateway-access-logs/github.svg)](https://agentmods.dev/skills/plurigrid/asi/analyzing-api-gateway-access-logs)
Your own site
<a href="https://agentmods.dev/skills/plurigrid/asi/analyzing-api-gateway-access-logs"><img src="https://agentmods.dev/badge/skills/plurigrid/asi/analyzing-api-gateway-access-logs/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.

agentmods 80×15 button for analyzing-api-gateway-access-logs

Your own site · 80×15
<a href="https://agentmods.dev/skills/plurigrid/asi/analyzing-api-gateway-access-logs"><img src="https://agentmods.dev/badge/skills/plurigrid/asi/analyzing-api-gateway-access-logs.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 72 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 469 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 88% copy Near-identical to another mod 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.00072 $0.00469
Opus 5 $0.00036 $0.00234
Sonnet 5 $0.00014 $0.00094
Haiku 4.5 $0.00007 $0.00047

Measured 6d ago against content hash 8e0f18a1d214, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

analyzing-api-gateway-access-logs 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.

Origin

This is a copy

88% identical to analyzing-api-gateway-access-logs — 33 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

plugins/asi/skills/analyzing-api-gateway-access-logs/SKILL.md · 63 lines

What it actually says

Analyzing API Gateway Access Logs

When to Use

  • When investigating security incidents that require analyzing api gateway access logs
  • When building detection rules or threat hunting queries for this domain
  • When SOC analysts need structured procedures for this analysis type
  • When validating security monitoring coverage for related attack techniques

Prerequisites

  • Familiarity with security operations concepts and tools
  • Access to a test or lab environment for safe execution
  • Python 3.8+ with required dependencies installed
  • Appropriate authorization for any testing activities

Instructions

Parse API gateway access logs to identify attack patterns including broken object level authorization (BOLA), excessive data exposure, and injection attempts.

import pandas as pd

df = pd.read_json("api_gateway_logs.json", lines=True)
# Detect BOLA: same user accessing many different resource IDs
bola = df.groupby(["user_id", "endpoint"]).agg(
    unique_ids=("resource_id", "nunique")).reset_index()
suspicious = bola[bola["unique_ids"] > 50]

Key detection patterns:

  1. BOLA/IDOR: sequential resource ID enumeration
  2. Rate limit bypass via header manipulation
  3. Credential scanning (401 surges from single source)
  4. SQL/NoSQL injection in query parameters
  5. Unusual HTTP methods (DELETE, PATCH) on read-only endpoints

Examples

# Detect 401 surges indicating credential scanning
auth_failures = df[df["status_code"] == 401]
scanner_ips = auth_failures.groupby("source_ip").size()
scanners = scanner_ips[scanner_ips > 100]
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. 6d ago First seen · 63 lines · 72 tokens per session scan A 8e0f18a1d214

Subscribe to this mod's changes

analyzing-api-gateway-access-logs is a skill published in the GitHub repository plurigrid/asi (62 stars, last pushed 2mo ago), licensed MIT. It adds 72 tokens to every session and 469 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. It is 88% identical to analyzing-api-gateway-access-logs, differing in 33 lines, and is treated as a copy.

Related

Other skills, from other repositories

analyzing-api-gateway-access-logs

Parses API Gateway access logs (AWS API Gateway, Kong, Nginx) to detect BOLA/IDOR attacks, rate limit bypass, credential scanning, and injection attempts. Uses pandas for statistical analysis of request patterns and anomaly detection. Use when investigating API abuse or building API-specific threat detection rules.

pinkpixel-dev/skills-collection-1 · 72 tokens

analyzing-api-gateway-access-logs

Parses API Gateway access logs (AWS API Gateway, Kong, Nginx) to detect BOLA/IDOR attacks, rate limit bypass, credential scanning, and injection attempts. Uses pandas for statistical analysis of request patterns and anomaly detection. Use when investigating API abuse or building API-specific threat detection rules.

marysatasselshaped667/skills-collection-1 · 72 tokens

analyzing-api-gateway-access-logs

Use when parses API Gateway access logs (AWS API Gateway, Kong, Nginx) to detect BOLA/IDOR attacks, rate limit bypass, credential scanning, and injection attempts. Uses pandas for statistical analysis of request patterns and anomaly detection. Use when investigating API abuse or building API-specific threat detection…

oyi77/1ai-skills · 73 tokens

analyzing-api-gateway-access-logs

Parses API Gateway access logs (AWS API Gateway, Kong, Nginx) to detect BOLA/IDOR attacks, rate limit bypass, credential scanning, and injection attempts. Uses pandas for statistical analysis of request patterns and anomaly detection. Use when investigating API abuse or building API-specific threat detection rules.

autohandai/community-skills · 72 tokens

analyzing-api-gateway-access-logs

A log-analysis guide for API gateways such as AWS API Gateway, Kong, and Nginx. It uses request records to spot patterns linked to common API attacks.

killvxk/cybersecurity-skills-zh · 85 tokens

analyzing-api-gateway-access-logs

Parses API Gateway access logs (AWS API Gateway, Kong, Nginx) to detect BOLA/IDOR attacks, rate limit bypass, credential scanning, and injection attempts. Uses pandas for statistical analysis of request patterns and anomaly detection. Use when investigating API abuse or building API-specific threat detection rules.

Mikaru0Mystic/sectinel · 72 tokens