Burp-AI-Analyzer: Instructions file for Codex

AGENTS.md

Burp-AI-Analyzer AGENTS.md is an instructions file for Codex, OpenCode from gtasb/Burp-AI-Analyzer. It costs 2,357 tokens per session, scanned A, original, MIT.

Project instructions for Burp-AI-Analyzer, a Java 21 extension for Burp Suite that uses AI to analyze web-application traffic. They document the build and tests, main components, dependencies, and known quirks.

In plain words
What is it for?
Use them when building or testing the extension, changing its AI runtime, clients, panels, filesystem or command-line access, or fixing documented bugs.
Why use it?
They show developers where the extension's large user interface and two similar API clients live, and which settings affect its tools. This reduces the chance of changing one duplicated client or UI path while missing the other.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md. Also seen: mentions subagents; mentions AGENTS.md.

This is gtasb/Burp-AI-Analyzer's own configuration. It tells Codex and OpenCode how to work on Burp-AI-Analyzer itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything Burp-AI-Analyzer configures →

Reuse

Borrowing it

Nothing to install: this file belongs to gtasb/Burp-AI-Analyzer. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/gtasb/Burp-AI-Analyzer/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/gtasb/Burp-AI-Analyzer

Made for: Codex, OpenCode.

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 Burp-AI-Analyzer AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/gtasb/burp-ai-analyzer/agents-md/github.svg)](https://agentmods.dev/instructions/gtasb/burp-ai-analyzer/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/gtasb/burp-ai-analyzer/agents-md"><img src="https://agentmods.dev/badge/instructions/gtasb/burp-ai-analyzer/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.

agentmods 80×15 button for Burp-AI-Analyzer AGENTS.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/gtasb/burp-ai-analyzer/agents-md"><img src="https://agentmods.dev/badge/instructions/gtasb/burp-ai-analyzer/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 2,357 This file is loaded in full into every session.
When invoked 2,357 The same file — it is already loaded in full.
Security scan A 1 finding. A grade says what 26 rules found in the file — not that it is safe.
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.02357 $0.02357
Opus 5.5 $0.00943 $0.00943
Sonnet 5.5 $0.00471 $0.00471
Haiku 4.5 $0.00236 $0.00236

Measured today against content hash 990b6b3e14e8, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

Burp-AI-Analyzer AGENTS.md scanned grade A with 1 finding 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 today.

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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

`py`, `where`, `curl` all disappear. Two separate paths need it: the Harness spec
AGENTS.md · 126 lines

How it starts

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

AGENTS.md

Build & test

mvn clean package           # full build + tests
mvn test                    # 412 tests, ~2 min

Requires JDK 21 + --enable-preview (Maven config handles this).

Architecture

  • Entrypoint: src/com/ai/analyzer/core/AIExtension.java — implements BurpExtension
  • Agent runtime: AgentScopeAgentRuntime wraps AgentScope 2.0 HarnessAgent via streamEvents()
  • Two parallel clients: AgentApiClient (active/chat) and PassiveScanApiClient (batch). They have ~90% duplicated code — editing one likely needs the same change in the other
  • UI: AIAnalyzerTab (3475 lines) is the main JPanel tab; ChatPanel is the side panel

Key dependencies

io.agentscope:agentscope-harness:2.0.3 (via ${agentscope.version}) — HarnessAgent provides native tools:

  • execute (native shell tool; the actual ShellExecuteTool.NAME constant is execute, not execute_shell_command — controlled by enableCliTool checkbox)
  • agent_spawn/agent_send/agent_list (sub-agents, always enabled)
  • read_file/write_file/edit_file/grep/glob (filesystem, controlled by enableFileSystemAccess)
  • Tool results >16KB auto-evicted to disk, readable via read_file

Sandbox vs permission mode (two independent layers)

  • File sandbox (LocalFilesystemSpec.mode, set in AgentScopeAgentRuntime): constrains which paths file tools may touch. UNRESTRICTED (default, sandbox off) = any path; ROOTED = workspace/project roots only. Toggled by enableFileSystemSandbox in the CLI tab.
  • Permission mode (PermissionContextState.mode, hardcoded BYPASS): constrains whether a tool call is allowed to execute at all, for every tool. AgentScope offers 5 (DEFAULT, ACCEPT_EDITS, EXPLORE, BYPASS, DONT_ASK) but only non-interactive ones would be safe here: the confirm handler is auto-approve (-> true), so DEFAULT/ACCEPT_EDITS would ask-then-auto-yes and risk re-triggering the historical ASKING stall. Do not add a UI for them without a real dialog.

Read the full file on GitHub · 126 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. today Changed · +23 lines · +493 tokens per session 990b6b3e14e8
  2. 4d ago Changed · +8 lines · +213 tokens per session da3e4aa15e9d
  3. 7d ago Changed · +6 lines · +114 tokens per session 22e2d27f48d5
  4. 26d ago Changed · +2 lines · +143 tokens per session 6183b8e655a0
  5. 27d ago Changed · +26 lines · +449 tokens per session fd044abeb344
  6. 1mo ago First seen · 61 lines · 945 tokens per session scan A eaa5c06b565a

Subscribe to this mod's changes

Burp-AI-Analyzer AGENTS.md is an instructions file published in the GitHub repository gtasb/Burp-AI-Analyzer (25 stars, last pushed yesterday), licensed MIT. It adds 2,357 tokens to every session, about $0.0094 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

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

microsoft/vscode · 9,715 tokens

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.

vercel/next.js · 7,786 tokens

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

microsoft/vscode · 5,262 tokens

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.

langchain-ai/langchain · 4,680 tokens

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

microsoft/vscode · 2,731 tokens

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.

denoland/deno · 3,077 tokens