Menu
DEPRECATED in v0.2.0 -- use browser-extract instead; this is a thin shim for backward compatibility, removed in v0.3.0
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | browser-scrape |
| description | DEPRECATED in v0.2.0 -- use browser-extract instead; this is a thin shim for backward compatibility, removed in v0.3.0 |
| argument-hint | <url> |
| allowed-tools | Bash Read |
Deprecated since plugin v0.2.0. Removed in v0.3.0.
Use
browser-extractinstead. It provides the same scraping capability plus:
- RVF cognitive container per session (replayable, federatable)
- Mandatory AIDefence PII + prompt-injection gates
- Persistent
browser-templatesnamespace for reusable recipes- Automatic
browser-selectorsnamespace updates so DOM drift is recoverable
| v0.1 invocation | v0.2 equivalent |
|---|---|
/browser-scrape <url> | /browser-extract <url> |
/browser-scrape <url> (with template intent) | /browser-extract <url> --template <name> |
Manual selector storage in browser-patterns namespace | Automatic — browser-extract writes to browser-templates and browser-selectors |
This skill delegates to browser-extract. Calling it emits a deprecation notice and proceeds.
# This skill is intentionally minimal — it just points the agent at the new skill.
echo "browser-scrape is deprecated; running browser-extract instead." >&2
The deprecation notice is captured in the agent's transcript so callers see the remediation. There is no behavior preserved here beyond the redirect — if you depended on a specific extraction shape, port to browser-extract and use --template to encode it.
Run one tick of the sales business-pod (ADR-164 §4.1, Phase 2). Loads templates/sales.json, validates it against the pod-schema, resolves agents against ruflo's agent registry, reserves budget via the Phase-2 file-based stub ledger (atomic SQLite tracker is Phase 3 per ADR-164.1), constructs per-agent dry-run prompts, posts a summary envelope to room "sales" via the federation_bbs_publish JSONL backing store, and emits a structured {podName, tickId, agentsRan, totalUsd, envelopeId, status} line for /loop ingestion. Dry-run by default; --live is reserved for Phase 3.
Run full security scans on the codebase using Ruflo security tools. Use when reviewing PRs for security regressions, auditing auth/input-handling code, before production deploys, or when the user asks for a security check at quick/standard/deep depth.
Initialize a multi-agent swarm with anti-drift configuration. Use when starting a complex multi-file task that needs 3+ coordinated agents (feature implementation, refactor across modules, security audit). Skip for single-file edits or quick questions.
Run the SPARC Pseudocode and Architecture phases (2 and 3) — write algorithm pseudocode, design module boundaries and API contracts, then implement
Scaffold a new Claude Code plugin with proper directory structure, plugin.json, skills, commands, and agents
Scan project dependencies for known vulnerabilities and CVEs. Use when auditing third-party packages, before releases, after `npm install`/lockfile changes, or when investigating reported CVE advisories.