A guide for triaging and writing security bug reports. It covers report structure, severity, CVSS scoring, reproduction steps, evidence, impact, and remediation.

Use it after finding a vulnerability to document the affected endpoint, proof, risk, severity, and suggested fix.

It helps turn a discovered security problem into a complete report that reviewers can reproduce and assess.

reporting — Skill for Claude Code and Codex by sanjaysaini1952

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 sanjaysaini1952/BugBounty-Arsenal --skill reporting

Clone the repo

git clone --depth 1 https://github.com/sanjaysaini1952/BugBounty-Arsenal

Made for: Claude Code, Codex.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/sanjaysaini1952/bugbounty-arsenal/reporting/github.svg)](https://agentmods.dev/skills/sanjaysaini1952/bugbounty-arsenal/reporting)

Your own site

<a href="https://agentmods.dev/skills/sanjaysaini1952/bugbounty-arsenal/reporting"><img src="https://agentmods.dev/badge/skills/sanjaysaini1952/bugbounty-arsenal/reporting/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/sanjaysaini1952/bugbounty-arsenal/reporting"><img src="https://agentmods.dev/badge/skills/sanjaysaini1952/bugbounty-arsenal/reporting.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 0 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 670 The whole file, excluding the scripts and references it only reads on demand.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00000	$0.00670
Opus 5	$0.00000	$0.00335
Sonnet 5	$0.00000	$0.00134
Haiku 4.5	$0.00000	$0.00067

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

Security

Grade A, and why

reporting 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 11d 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.

Makes network callslowCapability

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

4. **Steps to Reproduce** — Numbered steps with curl commands

skills/reporting/SKILL.md · 81 lines

How it starts

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

Reporting & Triage Skill

Follow this after every finding. A good report = accepted report = bounty paid.

Report Structure (All Platforms)

Title Format

[Severity] [Vulnerability Type] in [Endpoint/Feature] allows [Impact]

Examples:

[Critical] SQL Injection in /api/login allows full database access
[High] IDOR in /api/users/{id}/profile exposes PII of all users
[Medium] Open Redirect in OAuth redirect_uri allows account takeover
[Low] Information Disclosure via exposed .git directory

Report Sections

Summary — 2-3 sentences explaining the bug and its impact
Severity — CVSS score with justification
Affected Endpoint — URL, parameters, method
Steps to Reproduce — Numbered steps with curl commands
Proof of Concept — Screenshots, curl commands, response excerpts
Impact — Who is affected, what data is at risk, business impact
Remediation — Specific fix recommendation

CVSS Scoring Guide

Severity	CVSS Range	Example
Critical	9.0-10.0	RCE, SQLi with data exfil, auth bypass
High	7.0-8.9	IDOR with PII, SSRF to cloud metadata
Medium	4.0-6.9	Open redirect, CORS misconfig, CSRF
Low	0.1-3.9	Info disclosure, missing headers

7-Question Gate (Mandatory)

Is the target explicitly in scope?
Is this on the accepted-impact list?
Does this affect real users?
Can you reproduce it with curl?
Is this not already disclosed?
Does the impact match severity claimed?
Would a triager agree?

Platform-Specific Requirements

HackerOne

Map to VRT (Vulnerability Rating Taxonomy)
Include CVSS vector string
Use curl for reproduction
Include response showing impact

Bugcrowd

Map to VRT
Include "Friendly Tester" language
Never include real PII in PoC
Use placeholder data

Intigriti

Include CVSS calculator link
Video PoC recommended
Write in clear, concise English

Common Rejection Reasons

Informational only without impact
Duplicate of known issue
Out of scope
Missing reproduction steps
Overclaiming severity
Theoretical vs demonstrated impact
No user impact (self-XSS, self-DoS)

Read the full file on GitHub · 81 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.

11d ago First seen · 81 lines · 0 tokens per session scan A b97fd086d611

Subscribe to this mod's changes

reporting is a skill published in the GitHub repository sanjaysaini1952/BugBounty-Arsenal (2 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 670 tokens. 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-31.

Security

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens

reporting