port-nuker 1.0.1 → 1.0.4

package/.agent/skills/skills/voice-agents/SKILL.md

@@ -1,68 +0,0 @@
----
-name: voice-agents
-description: "Voice agents represent the frontier of AI interaction - humans speaking naturally with AI systems. The challenge isn't just speech recognition and synthesis, it's achieving natural conversation flow with sub-800ms latency while handling interruptions, background noise, and emotional nuance.  This skill covers two architectures: speech-to-speech (OpenAI Realtime API, lowest latency, most natural) and pipeline (STT→LLM→TTS, more control, easier to debug). Key insight: latency is the constraint. Hu"
-source: vibeship-spawner-skills (Apache 2.0)
----
-
-# Voice Agents
-
-You are a voice AI architect who has shipped production voice agents handling
-millions of calls. You understand the physics of latency - every component
-adds milliseconds, and the sum determines whether conversations feel natural
-or awkward.
-
-Your core insight: Two architectures exist. Speech-to-speech (S2S) models like
-OpenAI Realtime API preserve emotion and achieve lowest latency but are less
-controllable. Pipeline architectures (STT→LLM→TTS) give you control at each
-step but add latency. Mos
-
-## Capabilities
-
-- voice-agents
-- speech-to-speech
-- speech-to-text
-- text-to-speech
-- conversational-ai
-- voice-activity-detection
-- turn-taking
-- barge-in-detection
-- voice-interfaces
-
-## Patterns
-
-### Speech-to-Speech Architecture
-
-Direct audio-to-audio processing for lowest latency
-
-### Pipeline Architecture
-
-Separate STT → LLM → TTS for maximum control
-
-### Voice Activity Detection Pattern
-
-Detect when user starts/stops speaking
-
-## Anti-Patterns
-
-### ❌ Ignoring Latency Budget
-
-### ❌ Silence-Only Turn Detection
-
-### ❌ Long Responses
-
-## ⚠️ Sharp Edges
-
-| Issue | Severity | Solution |
-|-------|----------|----------|
-| Issue | critical | # Measure and budget latency for each component: |
-| Issue | high | # Target jitter metrics: |
-| Issue | high | # Use semantic VAD: |
-| Issue | high | # Implement barge-in detection: |
-| Issue | medium | # Constrain response length in prompts: |
-| Issue | medium | # Prompt for spoken format: |
-| Issue | medium | # Implement noise handling: |
-| Issue | medium | # Mitigate STT errors: |
-
-## Related Skills
-
-Works well with: `agent-tool-builder`, `multi-agent-orchestration`, `llm-architect`, `backend`

package/.agent/skills/skills/voice-ai-development/SKILL.md

@@ -1,302 +0,0 @@
----
-name: voice-ai-development
-description: "Expert in building voice AI applications - from real-time voice agents to voice-enabled apps. Covers OpenAI Realtime API, Vapi for voice agents, Deepgram for transcription, ElevenLabs for synthesis, LiveKit for real-time infrastructure, and WebRTC fundamentals. Knows how to build low-latency, production-ready voice experiences. Use when: voice ai, voice agent, speech to text, text to speech, realtime voice."
-source: vibeship-spawner-skills (Apache 2.0)
----
-
-# Voice AI Development
-
-**Role**: Voice AI Architect
-
-You are an expert in building real-time voice applications. You think in terms of
-latency budgets, audio quality, and user experience. You know that voice apps feel
-magical when fast and broken when slow. You choose the right combination of providers
-for each use case and optimize relentlessly for perceived responsiveness.
-
-## Capabilities
-
-- OpenAI Realtime API
-- Vapi voice agents
-- Deepgram STT/TTS
-- ElevenLabs voice synthesis
-- LiveKit real-time infrastructure
-- WebRTC audio handling
-- Voice agent design
-- Latency optimization
-
-## Requirements
-
-- Python or Node.js
-- API keys for providers
-- Audio handling knowledge
-
-## Patterns
-
-### OpenAI Realtime API
-
-Native voice-to-voice with GPT-4o
-
-**When to use**: When you want integrated voice AI without separate STT/TTS
-
-```python
-import asyncio
-import websockets
-import json
-import base64
-
-OPENAI_API_KEY = "sk-..."
-
-async def voice_session():
-    url = "wss://api.openai.com/v1/realtime?model=gpt-4o-realtime-preview"
-    headers = {
-        "Authorization": f"Bearer {OPENAI_API_KEY}",
-        "OpenAI-Beta": "realtime=v1"
-    }
-
-    async with websockets.connect(url, extra_headers=headers) as ws:
-        # Configure session
-        await ws.send(json.dumps({
-            "type": "session.update",
-            "session": {
-                "modalities": ["text", "audio"],
-                "voice": "alloy",  # alloy, echo, fable, onyx, nova, shimmer
-                "input_audio_format": "pcm16",
-                "output_audio_format": "pcm16",
-                "input_audio_transcription": {
-                    "model": "whisper-1"
-                },
-                "turn_detection": {
-                    "type": "server_vad",  # Voice activity detection
-                    "threshold": 0.5,
-                    "prefix_padding_ms": 300,
-                    "silence_duration_ms": 500
-                },
-                "tools": [
-                    {
-                        "type": "function",
-                        "name": "get_weather",
-                        "description": "Get weather for a location",
-                        "parameters": {
-                            "type": "object",
-                            "properties": {
-                                "location": {"type": "string"}
-                            }
-                        }
-                    }
-                ]
-            }
-        }))
-
-        # Send audio (PCM16, 24kHz, mono)
-        async def send_audio(audio_bytes):
-            await ws.send(json.dumps({
-                "type": "input_audio_buffer.append",
-                "audio": base64.b64encode(audio_bytes).decode()
-            }))
-
-        # Receive events
-        async for message in ws:
-            event = json.loads(message)
-
-            if event["type"] == "resp
-```
-
-### Vapi Voice Agent
-
-Build voice agents with Vapi platform
-
-**When to use**: Phone-based agents, quick deployment
-
-```python
-# Vapi provides hosted voice agents with webhooks
-
-from flask import Flask, request, jsonify
-import vapi
-
-app = Flask(__name__)
-client = vapi.Vapi(api_key="...")
-
-# Create an assistant
-assistant = client.assistants.create(
-    name="Support Agent",
-    model={
-        "provider": "openai",
-        "model": "gpt-4o",
-        "messages": [
-            {
-                "role": "system",
-                "content": "You are a helpful support agent..."
-            }
-        ]
-    },
-    voice={
-        "provider": "11labs",
-        "voiceId": "21m00Tcm4TlvDq8ikWAM"  # Rachel
-    },
-    firstMessage="Hi! How can I help you today?",
-    transcriber={
-        "provider": "deepgram",
-        "model": "nova-2"
-    }
-)
-
-# Webhook for conversation events
-@app.route("/vapi/webhook", methods=["POST"])
-def vapi_webhook():
-    event = request.json
-
-    if event["type"] == "function-call":
-        # Handle tool call
-        name = event["functionCall"]["name"]
-        args = event["functionCall"]["parameters"]
-
-        if name == "check_order":
-            result = check_order(args["order_id"])
-            return jsonify({"result": result})
-
-    elif event["type"] == "end-of-call-report":
-        # Call ended - save transcript
-        transcript = event["transcript"]
-        save_transcript(event["call"]["id"], transcript)
-
-    return jsonify({"ok": True})
-
-# Start outbound call
-call = client.calls.create(
-    assistant_id=assistant.id,
-    customer={
-        "number": "+1234567890"
-    },
-    phoneNumber={
-        "twilioPhoneNumber": "+0987654321"
-    }
-)
-
-# Or create web call
-web_call = client.calls.create(
-    assistant_id=assistant.id,
-    type="web"
-)
-# Returns URL for WebRTC connection
-```
-
-### Deepgram STT + ElevenLabs TTS
-
-Best-in-class transcription and synthesis
-
-**When to use**: High quality voice, custom pipeline
-
-```python
-import asyncio
-from deepgram import DeepgramClient, LiveTranscriptionEvents
-from elevenlabs import ElevenLabs
-
-# Deepgram real-time transcription
-deepgram = DeepgramClient(api_key="...")
-
-async def transcribe_stream(audio_stream):
-    connection = deepgram.listen.live.v("1")
-
-    async def on_transcript(result):
-        transcript = result.channel.alternatives[0].transcript
-        if transcript:
-            print(f"Heard: {transcript}")
-            if result.is_final:
-                # Process final transcript
-                await handle_user_input(transcript)
-
-    connection.on(LiveTranscriptionEvents.Transcript, on_transcript)
-
-    await connection.start({
-        "model": "nova-2",  # Best quality
-        "language": "en",
-        "smart_format": True,
-        "interim_results": True,  # Get partial results
-        "utterance_end_ms": 1000,
-        "vad_events": True,  # Voice activity detection
-        "encoding": "linear16",
-        "sample_rate": 16000
-    })
-
-    # Stream audio
-    async for chunk in audio_stream:
-        await connection.send(chunk)
-
-    await connection.finish()
-
-# ElevenLabs streaming synthesis
-eleven = ElevenLabs(api_key="...")
-
-def text_to_speech_stream(text: str):
-    """Stream TTS audio chunks."""
-    audio_stream = eleven.text_to_speech.convert_as_stream(
-        voice_id="21m00Tcm4TlvDq8ikWAM",  # Rachel
-        model_id="eleven_turbo_v2_5",  # Fastest
-        text=text,
-        output_format="pcm_24000"  # Raw PCM for low latency
-    )
-
-    for chunk in audio_stream:
-        yield chunk
-
-# Or with WebSocket for lowest latency
-async def tts_websocket(text_stream):
-    async with eleven.text_to_speech.stream_async(
-        voice_id="21m00Tcm4TlvDq8ikWAM",
-        model_id="eleven_turbo_v2_5"
-    ) as tts:
-        async for text_chunk in text_stream:
-            audio = await tts.send(text_chunk)
-            yield audio
-
-        # Flush remaining audio
-        final_audio = await tts.flush()
-        yield final_audio
-```
-
-## Anti-Patterns
-
-### ❌ Non-streaming Pipeline
-
-**Why bad**: Adds seconds of latency.
-User perceives as slow.
-Loses conversation flow.
-
-**Instead**: Stream everything:
-- STT: interim results
-- LLM: token streaming
-- TTS: chunk streaming
-Start TTS before LLM finishes.
-
-### ❌ Ignoring Interruptions
-
-**Why bad**: Frustrating user experience.
-Feels like talking to a machine.
-Wastes time.
-
-**Instead**: Implement barge-in detection.
-Use VAD to detect user speech.
-Stop TTS immediately.
-Clear audio queue.
-
-### ❌ Single Provider Lock-in
-
-**Why bad**: May not be best quality.
-Single point of failure.
-Harder to optimize.
-
-**Instead**: Mix best providers:
-- Deepgram for STT (speed + accuracy)
-- ElevenLabs for TTS (voice quality)
-- OpenAI/Anthropic for LLM
-
-## Limitations
-
-- Latency varies by provider
-- Cost per minute adds up
-- Quality depends on network
-- Complex debugging
-
-## Related Skills
-
-Works well with: `langgraph`, `structured-output`, `langfuse`

package/.agent/skills/skills/vulnerability-scanner/SKILL.md

@@ -1,276 +0,0 @@
----
-name: vulnerability-scanner
-description: Advanced vulnerability analysis principles. OWASP 2025, Supply Chain Security, attack surface mapping, risk prioritization.
-allowed-tools: Read, Glob, Grep, Bash
----
-
-# Vulnerability Scanner
-
-> Think like an attacker, defend like an expert. 2025 threat landscape awareness.
-
-## 🔧 Runtime Scripts
-
-**Execute for automated validation:**
-
-| Script | Purpose | Usage |
-|--------|---------|-------|
-| `scripts/security_scan.py` | Validate security principles applied | `python scripts/security_scan.py <project_path>` |
-
-## 📋 Reference Files
-
-| File | Purpose |
-|------|---------|
-| [checklists.md](checklists.md) | OWASP Top 10, Auth, API, Data protection checklists |
-
----
-
-## 1. Security Expert Mindset
-
-### Core Principles
-
-| Principle | Application |
-|-----------|-------------|
-| **Assume Breach** | Design as if attacker already inside |
-| **Zero Trust** | Never trust, always verify |
-| **Defense in Depth** | Multiple layers, no single point |
-| **Least Privilege** | Minimum required access only |
-| **Fail Secure** | On error, deny access |
-
-### Threat Modeling Questions
-
-Before scanning, ask:
-1. What are we protecting? (Assets)
-2. Who would attack? (Threat actors)
-3. How would they attack? (Attack vectors)
-4. What's the impact? (Business risk)
-
----
-
-## 2. OWASP Top 10:2025
-
-### Risk Categories
-
-| Rank | Category | Think About |
-|------|----------|-------------|
-| **A01** | Broken Access Control | Who can access what? IDOR, SSRF |
-| **A02** | Security Misconfiguration | Defaults, headers, exposed services |
-| **A03** | Software Supply Chain 🆕 | Dependencies, CI/CD, build integrity |
-| **A04** | Cryptographic Failures | Weak crypto, exposed secrets |
-| **A05** | Injection | User input → system commands |
-| **A06** | Insecure Design | Flawed architecture |
-| **A07** | Authentication Failures | Session, credential management |
-| **A08** | Integrity Failures | Unsigned updates, tampered data |
-| **A09** | Logging & Alerting | Blind spots, no monitoring |
-| **A10** | Exceptional Conditions 🆕 | Error handling, fail-open states |
-
-### 2025 Key Changes
-
-```
-2021 → 2025 Shifts:
-├── SSRF merged into A01 (Access Control)
-├── A02 elevated (Cloud/Container configs)
-├── A03 NEW: Supply Chain (major focus)
-├── A10 NEW: Exceptional Conditions
-└── Focus shift: Root causes > Symptoms
-```
-
----
-
-## 3. Supply Chain Security (A03)
-
-### Attack Surface
-
-| Vector | Risk | Question to Ask |
-|--------|------|-----------------|
-| **Dependencies** | Malicious packages | Do we audit new deps? |
-| **Lock files** | Integrity attacks | Are they committed? |
-| **Build pipeline** | CI/CD compromise | Who can modify? |
-| **Registry** | Typosquatting | Verified sources? |
-
-### Defense Principles
-
-- Verify package integrity (checksums)
-- Pin versions, audit updates
-- Use private registries for critical deps
-- Sign and verify artifacts
-
----
-
-## 4. Attack Surface Mapping
-
-### What to Map
-
-| Category | Elements |
-|----------|----------|
-| **Entry Points** | APIs, forms, file uploads |
-| **Data Flows** | Input → Process → Output |
-| **Trust Boundaries** | Where auth/authz checked |
-| **Assets** | Secrets, PII, business data |
-
-### Prioritization Matrix
-
-```
-Risk = Likelihood × Impact
-
-High Impact + High Likelihood → CRITICAL
-High Impact + Low Likelihood  → HIGH
-Low Impact + High Likelihood  → MEDIUM
-Low Impact + Low Likelihood   → LOW
-```
-
----
-
-## 5. Risk Prioritization
-
-### CVSS + Context
-
-| Factor | Weight | Question |
-|--------|--------|----------|
-| **CVSS Score** | Base severity | How severe is the vuln? |
-| **EPSS Score** | Exploit likelihood | Is it being exploited? |
-| **Asset Value** | Business context | What's at risk? |
-| **Exposure** | Attack surface | Internet-facing? |
-
-### Prioritization Decision Tree
-
-```
-Is it actively exploited (EPSS >0.5)?
-├── YES → CRITICAL: Immediate action
-└── NO → Check CVSS
-         ├── CVSS ≥9.0 → HIGH
-         ├── CVSS 7.0-8.9 → Consider asset value
-         └── CVSS <7.0 → Schedule for later
-```
-
----
-
-## 6. Exceptional Conditions (A10 - New)
-
-### Fail-Open vs Fail-Closed
-
-| Scenario | Fail-Open (BAD) | Fail-Closed (GOOD) |
-|----------|-----------------|---------------------|
-| Auth error | Allow access | Deny access |
-| Parsing fails | Accept input | Reject input |
-| Timeout | Retry forever | Limit + abort |
-
-### What to Check
-
-- Exception handlers that catch-all and ignore
-- Missing error handling on security operations
-- Race conditions in auth/authz
-- Resource exhaustion scenarios
-
----
-
-## 7. Scanning Methodology
-
-### Phase-Based Approach
-
-```
-1. RECONNAISSANCE
-   └── Understand the target
-       ├── Technology stack
-       ├── Entry points
-       └── Data flows
-
-2. DISCOVERY
-   └── Identify potential issues
-       ├── Configuration review
-       ├── Dependency analysis
-       └── Code pattern search
-
-3. ANALYSIS
-   └── Validate and prioritize
-       ├── False positive elimination
-       ├── Risk scoring
-       └── Attack chain mapping
-
-4. REPORTING
-   └── Actionable findings
-       ├── Clear reproduction steps
-       ├── Business impact
-       └── Remediation guidance
-```
-
----
-
-## 8. Code Pattern Analysis
-
-### High-Risk Patterns
-
-| Pattern | Risk | Look For |
-|---------|------|----------|
-| **String concat in queries** | Injection | `"SELECT * FROM " + user_input` |
-| **Dynamic code execution** | RCE | `eval()`, `exec()`, `Function()` |
-| **Unsafe deserialization** | RCE | `pickle.loads()`, `unserialize()` |
-| **Path manipulation** | Traversal | User input in file paths |
-| **Disabled security** | Various | `verify=False`, `--insecure` |
-
-### Secret Patterns
-
-| Type | Indicators |
-|------|-----------|
-| API Keys | `api_key`, `apikey`, high entropy |
-| Tokens | `token`, `bearer`, `jwt` |
-| Credentials | `password`, `secret`, `key` |
-| Cloud | `AWS_`, `AZURE_`, `GCP_` prefixes |
-
----
-
-## 9. Cloud Security Considerations
-
-### Shared Responsibility
-
-| Layer | You Own | Provider Owns |
-|-------|---------|---------------|
-| Data | ✅ | ❌ |
-| Application | ✅ | ❌ |
-| OS/Runtime | Depends | Depends |
-| Infrastructure | ❌ | ✅ |
-
-### Cloud-Specific Checks
-
-- IAM: Least privilege applied?
-- Storage: Public buckets?
-- Network: Security groups tightened?
-- Secrets: Using secrets manager?
-
----
-
-## 10. Anti-Patterns
-
-| ❌ Don't | ✅ Do |
-|----------|-------|
-| Scan without understanding | Map attack surface first |
-| Alert on every CVE | Prioritize by exploitability + asset |
-| Ignore false positives | Maintain verified baseline |
-| Fix symptoms only | Address root causes |
-| Scan once before deploy | Continuous scanning |
-| Trust third-party deps blindly | Verify integrity, audit code |
-
----
-
-## 11. Reporting Principles
-
-### Finding Structure
-
-Each finding should answer:
-1. **What?** - Clear vulnerability description
-2. **Where?** - Exact location (file, line, endpoint)
-3. **Why?** - Root cause explanation
-4. **Impact?** - Business consequence
-5. **How to fix?** - Specific remediation
-
-### Severity Classification
-
-| Severity | Criteria |
-|----------|----------|
-| **Critical** | RCE, auth bypass, mass data exposure |
-| **High** | Data exposure, privilege escalation |
-| **Medium** | Limited scope, requires conditions |
-| **Low** | Informational, best practice |
-
----
-
-> **Remember:** Vulnerability scanning finds issues. Expert thinking prioritizes what matters. Always ask: "What would an attacker do with this?"