campaign
Skill1 starsChanged 3 months agoMITView on GitHub
This is the entry point for "here's a URL — go find everything you can." The deterministic engine is scripts/campaign_runner.py (invoked by bin/bb-hunt or bin/bb-run campaign hunt). The judgement parts — understanding the target, triage, and impact verification — are driven by the agent following the loop below. Safety ceiling defaults to intrusive but is auto-capped to active-safe unless a non-empty --scope-file is supplied — intrusive blackbox testing only runs against targets you have authorization for. Credentials, cookies, tokens, and…
9 other projects use a version of this.
Adopted by
Most recently taken up by
- netherportal3/claude-campaigntheir own version, first seen Nov 16, 2026
- nodealchemy/powernode-platformtheir own version, first seen Oct 25, 2026
- a-lottes/aSPARKtheir own version, first seen Oct 13, 2026
- akachandan1/proofstacktheir own version, first seen Oct 11, 2026
- RubyEyedReaper/Odin-Skillstheir own version, first seen Aug 15, 2026
- inkwell-finance/claude-skillstheir own version, first seen Aug 13, 2026
Other versions9 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 9
- a-lottes/aSPARK★ 25same name
- GTMify/aigtm★ 25same name
- nodealchemy/powernode-platform★ 4same name
- inkwell-finance/claude-skills★ 2same name
- netherportal3/claude-campaign★ 1same name
- akachandan1/proofstack★ 0same name
- phoenixvn/claude-code-agency★ 0same name
- RubyEyedReaper/Odin-Skills★ 0same name
- victordelrosal/chairman★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
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
- 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
- traffic-corpusSkill
- triage-validationSkill
- vuln-intelSkill
- web3-auditSkill
- xssSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 0 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 8 edited versions we read keep these.
0
Distinctive
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
- Very specific: line 30
Launch: Run bin/bb-hunt <url> with the agreed --max-tier and --time-budget.
- Very specific: line 46
Keep all of the above local-only.
“Common” is measured: kept by at least 6 in 10 of the 8 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Campaign — Autonomous End-to-End Bug Bounty Run
Overview
The campaign skill turns a single target into a full, hands-off engagement. From one URL it runs context init, recon, domain modeling, technique matching, planning, then executes every applicable skill workflow in priority order (filtered by a safety ceiling), and finishes with reporting and readiness checks. The run is bounded by a wall-clock time budget, is resumable, and never aborts the whole campaign because one workflow failed.
This is the entry point for "here's a URL — go find everything you can." The deterministic engine is scripts/campaign_runner.py (invoked by bin/bb-hunt or bin/bb-run campaign hunt). The judgement parts — understanding the target, triage, and impact verification — are driven by the agent following the loop below.
Quick Reference
| Goal | Command |
| Hunt a brand-new URL (cold start, does its own init) | bin/bb-hunt <url> --time-budget 2h |
| Hunt with intrusive blackbox testing (requires authorization) | bin/bb-hunt <url> --scope-file <auth> --max-tier intrusive --time-budget 3h |
| Hunt using an already-initialized context | bin/bb-run campaign hunt |
| Check progress | bin/bb-run campaign status |
| Resume an interrupted run | bin/bb-hunt <url> --no-init --resume <campaign-id> |
| Preview the full plan without executing | bin/bb-hunt <url> --dry-run |
Safety ceiling defaults to intrusive but is auto-capped to active-safe unless a non-empty --scope-file is supplied — intrusive blackbox testing only runs against targets you have authorization for. Credentials, cookies, tokens, and target responses are kept local-only, are never committed (the .bb/ and output/ trees are gitignored), and must be redacted/sanitized before any report leaves the machine.
Workflow Selection
- New target, no prior recon, "find all vulns", "run for a while", a bare URL → start here with
bin/bb-hunt. - Authorization confirmed / scope file in hand and you want active+intrusive blackbox coverage →
--scope-file <auth> --max-tier intrusive. - Context already initialized for the target →
bin/bb-run campaign hunt(orhunt-intrusive). - A previous campaign was interrupted →
resumewith its campaign id. - You only want recon/triage, not full execution → run the individual
recon,domain-model,plannerskills instead.
Agent Loop (how the agent drives a campaign)
- Authorization. Confirm the user is authorized to test the target. If they have a scope/authorization file, pass it with
--scope-fileto unlock intrusive testing; without it the run stays atactive-safe. - Understand the target (web search). Before or alongside launch, use web search and the
vuln-intelandosintskills to learn what the target is: the company, its tech stack and frameworks, login/SSO providers, known CVEs for detected technologies, and any public bug bounty program scope and exclusions. Feed this into scope and into which skills to prioritize. - Launch. Run
bin/bb-hunt <url>with the agreed--max-tierand--time-budget. The engine handles init → recon → domain model → plan → priority-ordered execution → reporting on its own. - Monitor. Poll
bin/bb-run campaign status(or read.bb/campaigns/<id>/status.jsonandcampaign.log). The run continues past individual workflow failures. - Triage. As findings land under
$OUTDIR, do not treat scanner output as a finding. For each candidate, run the matching vulnerability skill's verify workflow and theimpact-verifierskill to rule out false positives and classify impact. - Report. For confirmed, impact-verified findings, use the
reportingskill (includingplatform-export) to produce platform-ready writeups with full evidence.
Available Workflows
hunt— full autonomous campaign using the already-initialized context (active-safe ceiling by default).hunt-intrusive— full campaign at the intrusive ceiling; requiresSCOPE_FILEauthorization.status— print the latest or named campaign status.resume— resume an interrupted campaign by id, skipping completed workflows.
The engine's safety ceiling, time budget, skill subset, and rate limit are all configurable; see python3 scripts/campaign_runner.py hunt --help.
Evidence Required
- Campaign state lives under
.bb/campaigns/<campaign-id>/:campaign.log(timestamped, redacted run log),results.jsonl(per-workflow exit codes and timing), andstatus.json(live phase and counts). - Per-workflow findings and evidence land under
$OUTDIRas defined by each individual skill. - Keep all of the above local-only; redact or sanitize any auth headers, cookies, bearer tokens, and PII before a report leaves the machine. Nothing in
.bb/oroutput/is committed. - A finding is only reportable after the
impact-verifiergate confirms impact and rules out false positives.
References
- Engine:
scripts/campaign_runner.py(hunt,status;--helpfor all flags) - CLI wrapper:
bin/bb-hunt - Backbone skills:
recon,domain-model,technique-kb,planner - Triage/report:
impact-verifier,reporting,vuln-intel,osint - Source of truth for workflows:
skill.yaml
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.

