traffic-corpus
Skill1 starsChanged 3 months agoMITView on GitHub
In this repository50 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .claude/CLAUDE.mdCLAUDE.md
- CLAUDE.mdCLAUDE.md
- agent-safetySkill
- ai-llmSkill
- apiSkill
- asset-graphSkill
- authSkill
- auto-researchSkill
- binary-analysisSkill
- business-logicSkill
- campaignSkill
- cicd-securitySkill
- cloudSkill
- cors-csrfSkill
- coverageSkill
- cross-accountSkill
- domain-modelSkill
- enrichmentSkill
- evaluation-harnessSkill
- file-uploadSkill
- graphql-auditSkill
- http-protocolSkill
- identity-domainSkill
- impact-verifierSkill
- meme-coin-auditSkill
- mobileSkill
- modern-browserSkill
- nuclei-scannerSkill
- oob-infraSkill
- osintSkill
- personaSkill
- plannerSkill
- privescSkill
- program-memorySkill
- race-conditionSkill
- rceSkill
- reconSkill
- reportingSkill
- sastSkill
- scope-managerSkill
- skill-scientistSkill
- sqliSkill
- ssrfSkill
- standard-catalogSkill
- technique-kbSkill
- triage-validationSkill
- vuln-intelSkill
- web3-auditSkill
- xssSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 4
Import real application traffic (HAR, Burp, mitmproxy, proxify, browser logs) and normalize it into a deduplicated, route-aware, …
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Traffic Corpus
Overview
Import real application traffic (HAR, Burp, mitmproxy, proxify, browser logs) and normalize it into a deduplicated, route-aware, object-aware corpus for replay-based security testing.
Quick Reference
- Skill: traffic-corpus
- Version: 1.0.0
- Bounded Context: TrafficCorpusContext
- Required tools:
python3,jq,curl - Risk tier: active-safe (imports, does not replay)
Workflow Selection
- Starting fresh:
import-trafficwith one or more source files, thennormalize-corpus. - Analyzing structure:
extract-routesthenextract-objectsandsummarize-corpus. - GraphQL targets:
extract-graphqlafter normalization. - WebSocket targets:
extract-websocketsafter normalization.
Available Workflows
| Workflow | Purpose |
import-traffic | Import one or more traffic sources (HAR, Burp XML, mitmproxy, proxify, raw curl). |
normalize-corpus | Deduplicate and normalize all samples into canonical route signatures. |
extract-routes | Produce route catalog with HTTP method, path shape, auth indicators, and tags. |
extract-objects | Extract object references (user IDs, file IDs, workspace IDs, etc.) from samples. |
extract-graphql | Extract GraphQL queries, mutations, subscriptions, and operation variables. |
extract-websockets | Extract WebSocket message patterns from captured traffic. |
summarize-corpus | Produce human-readable summary of corpus size, routes, objects, and coverage. |
Redaction and Secrets Handling
Imported traffic (HAR exports, captured cookies, Authorization / bearer tokens, session IDs, and API keys) is treated as sensitive and kept local-only under $OUTDIR/traffic-corpus/; these raw captures are never committed and the directory is covered by .gitignore. Before any corpus is shared or exported, secrets in headers and bodies are redacted/sanitized so cookies and bearer tokens never leave the local engagement workspace.
Evidence Required
- Source traffic files (raw) stored under
$OUTDIR/traffic-corpus/raw/. - Normalized corpus in JSONL format.
- Route signatures preserve original request/response pairs for evidence.
References
- OWASP WSTG-INFO-05 (Fingerprint Web Application)
- OWASP WSTG-INFO-06 (Application Entry Points)
- OWASP API Top 10 2023
- PortSwigger API Testing Academy Topic
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

