sensitive-browser
Execute sensitive browser actions (login, payments, form filling) outside the core agent loop using a dedicated CLI tool. Use when Claude needs to handle credentials, payment information, or other sensitive data in browser automation workflows. Triggers when users ask to log into websites, fill payment forms, or perform authenticated browser actions where sensitive data must be kept secure and separate from the main agent context.
What this skill does
# Sensitive Browser
Execute sensitive browser actions securely by delegating credential handling, payments, and form filling to a dedicated subprocess with isolated context.
## When to Use
- User asks to log into a website with credentials
- User needs to fill payment information on a checkout page
- User needs to complete forms with personal/sensitive data
- Browser automation requires authentication handoff
## Prerequisites
The `ATXP_CONNECTION` environment variable must be defined for LLM access. This provides the connection string to the ATXP platform.
If not configured, see the [ATXP CLI](https://github.com/atxp-dev/cli) for setup instructions.
## Workflow
### 1. Prepare Sensitive Data File
Create a JSON file with the user's sensitive data. Ask the user for the values needed:
```json
{
"credentials": {
"username": "[email protected]",
"password": "secret"
},
"payment": {
"cardNumber": "4111111111111111",
"expiry": "12/28",
"cvv": "123",
"billingZip": "94102"
},
"personal": {
"fullName": "Jane Doe",
"phone": "+1-555-0123",
"address": "123 Main St"
}
}
```
Only include the fields needed for the task. Store securely and delete after use.
### 2. Execute the Sensitive Action
```bash
npx sensitive-browser "<task>" \
--sensitive-data ./creds.json \
--url <target-url> \
--state ./session.json \
--output ./session.json
```
**Options:**
| Option | Description |
|--------|-------------|
| `<task>` | Natural language task (e.g., "log in with credentials") |
| `-d, --sensitive-data <path>` | Path to sensitive data JSON (required) |
| `-u, --url <url>` | Target URL to navigate to |
| `-s, --state <path>` | Playwright storage state to load |
| `-o, --output <path>` | Output path for updated state |
### 3. Integration with agent-browser
When used with agent-browser, hand off session state:
```bash
# Save current session
agent-browser --session myapp state save ./session.json
# Hand off to sensitive-browser for login
npx sensitive-browser "log in with credentials" \
--state ./session.json \
--sensitive-data ./creds.json
# Resume agent-browser with authenticated session
agent-browser --session myapp state load ./session.json
```
## Security Notes
- Sensitive data values are never logged or displayed
- The tool shows which fields will be used, not their values
- Delete sensitive data files after use
- Consider environment variables or secret managers for production
## Sensitive Data Schema
Supported field categories:
- `credentials`: username, password, email
- `payment`: cardNumber, expiry, cvv, billingZip, cardholderName
- `personal`: fullName, firstName, lastName, phone, address, city, state, zip, country, dateOfBirth
- Custom fields: Any additional `key: value` pairs as needed
Related in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.