agentleFS
zyphr-labszyphr-labs/bounty-harness/.claude/skills/oob-infra/SKILL.md

oob-infra

Skill1 starsChanged 3 months agoMITView on GitHub

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Start: start-client to launch an interactsh session.

    line 14
  2. Very specific:

    After testing: poll-interactions and correlate to map callbacks to tests.

    line 16

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

OOB Infrastructure

Overview

Manage out-of-band callback infrastructure for detecting blind vulnerabilities. Generate canaries, poll for interactions, correlate callbacks to specific tests, and produce evidence-grade OOB proof.

Quick Reference

  • Skill: oob-infra
  • Version: 1.0.0
  • Bounded Context: OobContext
  • Required tools: python3, curl, jq, interactsh-client
  • Risk tier: active-safe (passive callbacks)

Workflow Selection

  • Start: start-client to launch an interactsh session.
  • During testing: generate-canary to get unique payload URLs.
  • After testing: poll-interactions and correlate to map callbacks to tests.
  • Cleanup: stop-client when done.
  • Evidence: evidence-export for confirmed OOB findings.

Available Workflows

WorkflowPurpose
start-clientLaunch interactsh client and extract callback URL.
generate-canaryCreate a unique canary payload for a specific test.
poll-interactionsQuery the server for received callbacks.
correlateMap interactions back to specific tests and requests.
stop-clientCleanly shut down the callback client.
self-host-checkVerify self-hosted interactsh server health.
evidence-exportPackage OOB evidence for reporting.

Evidence Required

  • Canary payload ID and purpose.
  • Interaction timestamps, protocols, remote addresses.
  • Correlation between payload and originating test.
  • Raw callback data (request headers, body for HTTP callbacks).

References

  • ProjectDiscovery Interactsh documentation
  • OWASP WSTG-INPV-11 (SSRF Testing)
  • OWASP WSTG-INPV-07 (Blind XSS)
  • PortSwigger OAST (Out-of-band Application Security Testing)

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.