analyzing-api-gateway-access-logs

analyzing-api-gateway-access-logs is a skill for Claude Code from oyi77/1ai-skills. It costs 73 tokens per session (900 once invoked), scanned A, original, MIT.

A security analysis guide for examining API gateway access logs from services such as AWS API Gateway, Kong, or Nginx. It uses request patterns to find signs of attacks against APIs.

In plain words
What is it for?
It helps investigate API abuse, detect suspicious request patterns, and support threat-detection or monitoring work.
Why use it?
Large volumes of API requests can hide broken access controls, credential scanning, rate-limit bypasses, or injection attempts.

Skill for Claude Code

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

Part of the 1ai-skills plugin — 209 skills, 4 commands shipped together

Good fit It helps investigate API abuse, detect suspicious request patterns, and support threat-detection or monitoring work.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/oyi77/1ai-skills/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 oyi77/1ai-skills --skill analyzing-api-gateway-access-logs
Clone the repo
git clone --depth 1 https://github.com/oyi77/1ai-skills

Made for: Claude Code.

Or install 1ai-skills, the plugin that ships this one along with the rest of its 209 skills, 4 commands.

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/oyi77/1ai-skills/analyzing-api-gateway-access-logs/github.svg)](https://agentmods.dev/skills/oyi77/1ai-skills/analyzing-api-gateway-access-logs)
Your own site
<a href="https://agentmods.dev/skills/oyi77/1ai-skills/analyzing-api-gateway-access-logs"><img src="https://agentmods.dev/badge/skills/oyi77/1ai-skills/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/oyi77/1ai-skills/analyzing-api-gateway-access-logs"><img src="https://agentmods.dev/badge/skills/oyi77/1ai-skills/analyzing-api-gateway-access-logs.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 73 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 900 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. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.00073 $0.00900
Opus 5 $0.00036 $0.00450
Sonnet 5 $0.00015 $0.00180
Haiku 4.5 $0.00007 $0.00090

Measured 8d ago against content hash 9e8a196a09d8, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, 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 8d 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.

cybersecurity/analyzing-api-gateway-access-logs/SKILL.md · 113 lines

How it starts

The opening of the file, as written. The whole thing — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Analyzing Api Gateway Access Logs

Overview

Cybersecurity skill for analyzing api gateway access logs. Follows industry best practices and security standards.

When to Use

Trigger phrases:

  • "analyzing api gateway access logs"

  • "When investigating security incidents that require analyzing api gateway access"

  • "When building detection rules or threat hunting queries for this domain"

  • "When SOC analysts need structured procedures for this analysis type"

  • 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

When NOT to Use

  • When you lack proper authorization for testing
  • For production systems without change management
  • When the task requires legal or compliance expertise beyond technical scope

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

Workflow

# Example: IOC detection
import re

IOC_PATTERNS = {
    "ip": r"\b(?:\d{1,3}\.){3}\d{1,3}\b",
    "domain": r"\b[a-z0-9-]+\.[a-z]{2,}\b",
    "hash_md5": r"\b[a-f0-9]{32}\b",
    "hash_sha256": r"\b[a-f0-9]{64}\b",
}

def extract_iocs(text: str) -> dict:
    return {k: re.findall(v, text) for k, v in IOC_PATTERNS.items()}
  1. Scope the Analysis — Define what api gateway access logs artifacts or data sources to examine and the investigation timeline.
  2. Preserve Evidence — Create forensic copies of relevant data. Maintain chain of custody documentation.
  3. Extract Key Indicators — Parse and extract relevant api gateway access logs data points from collected artifacts.
  4. Correlate Findings — Cross-reference extracted data with other sources (threat intel, logs, timelines).
  5. Build Timeline — Construct a chronological sequence of events related to api gateway access logs.
  6. Document Analysis — Write findings report with evidence, conclusions, and recommendations.

Read the full file on GitHub · 113 lines

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. 8d ago First seen · 113 lines · 73 tokens per session scan A 9e8a196a09d8

Subscribe to this mod's changes

analyzing-api-gateway-access-logs is a skill published in the GitHub repository oyi77/1ai-skills (12 stars, last pushed today), licensed MIT. It adds 73 tokens to every session and 900 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-04.

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.

Mikaru0Mystic/sectinel · 72 tokens

analyzing-cloud-storage-access-patterns

Detect abnormal access patterns in AWS S3, GCS, and Azure Blob Storage by analyzing CloudTrail Data Events, GCS audit logs, and Azure Storage Analytics. Identifies after-hours bulk downloads, access from new IP addresses, unusual API calls (GetObject spikes), and potential data exfiltration using statistical baselines…

xalgorix/xalgorix · 79 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.

plurigrid/asi · 72 tokens