메뉴
Bug bounty program management and security disclosure expertise for smart contracts. Covers program setup on Immunefi, vulnerability triage, responsible disclosure coordination, bounty payments, and post-disclosure analysis.
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.
npx skills add https://github.com/a5c-ai/babysitter --skill bug-bounty명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.
로컬 사본을 원하시나요? SkillsMP에서 현재 제공할 수 있는 파일을 다운로드하세요.
Reference for querying the Atlas knowledge graph through its MCP tools — the SECONDARY enrichment/comparison layer that adds best-practice context to systems you have ALREADY scanned from your real sources (`az`, repos, dirs). Use when you need to look up nodes, edges, kinds, clusters, stats, or wiki pages in Atlas to compare against your real inventory. (atlas graph, query atlas, atlas mcp, search the graph, graph neighbors, atlas record, atlas kinds, enrichment layer)
Atlas turns your STATED NEED into a real systems atlas by SCANNING your actual sources (Azure via `az`, git repos, local dirs) and process/data mining them, THEN enriching against the Atlas knowledge graph. Use this skill when asked to inventory/map your real systems, scan your cloud + repos + directories, mine the real processes or data they contain, or collect their real constraints/gotchas. (atlas, scan my systems, inventory our azure account, map my repos, real systems atlas, process mining, data mining, collect nuances, system discovery)
This skill should be used when the user asks to "find skills in the wild", "assimilate popular workflows", "discover SKILL.md files in repos", "research external skills", "find workflow patterns", "survey the skill landscape", "what skills exist out there", or wants to investigate public repositories for extractable processes, babysitter plugins, and reusable procedural insights. Searches GitHub for SKILL.md files, classifies repos by archetype, and maintains structured research under docs/reference-repos/.
SKILL.md 표시 중
SOC 직업 분류 기준
| name | bug-bounty |
| description | Bug bounty program management and security disclosure expertise for smart contracts. Covers program setup on Immunefi, vulnerability triage, responsible disclosure coordination, bounty payments, and post-disclosure analysis. |
| allowed-tools | Read, Grep, Write, Bash, Edit, Glob, WebFetch, WebSearch |
| graph | {"domains":["domain:security"],"specializations":["specialization:cryptography-blockchain"],"skillAreas":["skill-area:smart-contract-security","skill-area:vulnerability-scanning-remediation","skill-area:incident-response-forensics"],"roles":["role:security-engineer","role:security-risk-analyst"]} |
Expert management of bug bounty programs and responsible security disclosure for blockchain protocols.
| Tool | Purpose |
|---|
| Reference |
|---|
| Trail of Bits Skills | Security analysis, property testing | building-secure-contracts |
| Slither MCP | Static analysis for validation | slither-mcp |
| Phalcon MCP | Transaction analysis | phalcon-mcp |
program:
name: "Protocol Name"
website: "https://protocol.xyz"
assets:
smart_contracts:
- type: "Smart Contract"
target: "0x..."
severity: "Critical"
websites:
- type: "Web Application"
target: "https://app.protocol.xyz"
severity: "High"
severity_levels:
critical:
range: "$100,000 - $1,000,000"
description: "Direct theft of funds, permanent freezing"
high:
range: "$10,000 - $100,000"
description: "Theft requiring user action, temporary freezing"
medium:
range: "$1,000 - $10,000"
description: "Griefing, DoS with medium impact"
low:
range: "$100 - $1,000"
description: "Minor issues, informational"
exclusions:
- "Issues in test files"
- "Third-party dependencies"
- "Issues requiring admin key compromise"
- "Front-running issues without significant impact"
| Severity | Impact | Examples |
|---|---|---|
| Critical | Direct fund loss, protocol takeover | Reentrancy draining funds, access control bypass |
| High | Significant fund loss, protocol disruption | Oracle manipulation, flash loan attacks |
| Medium | Limited fund loss, degraded functionality | Griefing attacks, minor calculation errors |
| Low | No fund loss, minor issues | Gas inefficiency, informational findings |
## Triage Checklist
- [ ] Report is within program scope
- [ ] Vulnerability is reproducible
- [ ] Impact assessment is accurate
- [ ] No duplicate of existing report
- [ ] Not a known issue or design decision
## Initial Classification
| Field | Value |
|-------|-------|
| Report ID | BB-2024-XXX |
| Submission Date | YYYY-MM-DD |
| Reporter | @handle |
| Asset Affected | Contract/URL |
| Initial Severity | Critical/High/Medium/Low |
| Status | Triaging |
# Clone and setup test environment
git clone <protocol-repo>
cd protocol
# Create PoC test
forge test --match-test test_VulnerabilityPoC -vvvv
# Run against mainnet fork
forge test --fork-url $MAINNET_RPC --match-test test_VulnerabilityPoC
Consider:
Final Severity = Base Impact - Mitigating Factors + Aggravating Factors
Day 0: Report received
Day 1-3: Initial triage and acknowledgment
Day 3-7: Validation and severity confirmation
Day 7-14: Fix development
Day 14-21: Fix review and testing
Day 21-30: Coordinated disclosure preparation
Day 30+: Public disclosure (if agreed)
Acknowledgment:
Subject: [BB-XXXX] Report Acknowledged
Dear Security Researcher,
Thank you for your submission to our bug bounty program. We have received
your report and assigned it reference number BB-XXXX.
Our security team is currently reviewing your submission. We will provide
an initial assessment within 3 business days.
Timeline:
- Initial response: 24-72 hours
- Severity assessment: 3-7 days
- Fix timeline: TBD based on severity
Best regards,
Security Team
Severity Confirmation:
Subject: [BB-XXXX] Severity Assessment Complete
Dear Security Researcher,
After thorough review, we have assessed your vulnerability report:
Severity: [CRITICAL/HIGH/MEDIUM/LOW]
Bounty Range: $X - $Y
Fix Timeline: X days
[Details of assessment]
Next Steps:
1. Fix development (ETA: X days)
2. Fix verification with your input
3. Coordinated disclosure discussion
Best regards,
Security Team
const bountyCalculation = {
baseBounty: getSeverityBase(severity), // Based on tier
adjustments: {
qualityOfReport: 1.0 - 1.5, // Well-documented PoC
impactAccuracy: 0.8 - 1.2, // Accurate impact assessment
firstReporter: 1.0, // First to report
duplicatePartial: 0.0 - 0.5, // Partial duplicate
responsibleBehavior: 1.0 - 1.2 // No public disclosure
},
calculate() {
return this.baseBounty *
this.adjustments.qualityOfReport *
this.adjustments.impactAccuracy *
this.adjustments.responsibleBehavior;
}
};
# Security Incident Post-Mortem: [Title]
## Summary
- **Date Discovered**: YYYY-MM-DD
- **Date Fixed**: YYYY-MM-DD
- **Severity**: Critical/High/Medium/Low
- **Bounty Paid**: $X
## Root Cause
[Detailed explanation of the vulnerability]
## Timeline
| Time | Event |
|------|-------|
| T+0h | Report received |
| T+2h | Triage complete |
| T+24h | Fix developed |
| T+48h | Fix deployed |
| T+168h | Public disclosure |
## Technical Details
[Code snippets, attack vectors, affected functions]
## Fix Implementation
[How the issue was resolved]
## Lessons Learned
1. [Lesson 1]
2. [Lesson 2]
3. [Lesson 3]
## Process Improvements
- [ ] Improvement 1
- [ ] Improvement 2
This skill integrates with:
bug-bounty-program.js - Full program management processincident-response-exploits.js - Exploit response coordinationsmart-contract-security-audit.js - Pre-launch security review| Issue | Solution |
|---|---|
| Slow response | Set up triage rotation, clear escalation |
| Scope disputes | Pre-define edge cases in program terms |
| Severity disagreements | Use CVSS scoring, document rationale |
| Payment delays | Pre-fund bounty pool, streamline KYC |
## Summary
[Brief description]
## Severity
[CVSS Score] - [Critical/High/Medium/Low]
## Affected Versions
- >= 1.0.0, < 1.2.3
## Patches
Fixed in version 1.2.3
## Workarounds
[If applicable]
## References
- [Link to fix PR]
- [Related documentation]
## Credits
Thanks to @researcher for responsible disclosure
agents/incident-response/AGENT.md - Incident response expertsmart-contract-security-audit.js - Security audit processreferences.md - Security disclosure resources