anymous 1.3.0 → 1.3.2

package/skills/claude-api/typescript/managed-agents/README.md

@@ -1,358 +0,0 @@
-# Managed Agents — TypeScript
-
-> **Bindings not shown here:** This README covers the most common managed-agents flows for TypeScript. If you need a class, method, namespace, field, or behavior that isn't shown, WebFetch the TypeScript SDK repo **or the relevant docs page** from `shared/live-sources.md` rather than guess. Do not extrapolate from cURL shapes or another language's SDK.
-
-> **Agents are persistent — create once, reference by ID.** Store the agent ID returned by `agents.create` and pass it to every subsequent `sessions.create`; do not call `agents.create` in the request path. **Recommended:** define agents and environments as version-controlled YAML applied with the `ant` CLI — see `shared/anthropic-cli.md` (its live-docs URL is in `shared/live-sources.md`). The CLI owns the control plane (create/update); your code owns the data plane (sessions with the stored ID). The examples below show in-code creation for when you must provision programmatically; in production the create call belongs in setup, not in the request path.
-
-## Installation
-
-```bash
-npm install @anthropic-ai/sdk
-```
-
-## Client Initialization
-
-```typescript
-import Anthropic from "@anthropic-ai/sdk";
-
-// Default — resolves credentials from the environment:
-// ANTHROPIC_API_KEY, or ANTHROPIC_AUTH_TOKEN, or an `ant auth login` profile.
-// Prefer this for local dev; don't hardcode a key.
-const client = new Anthropic();
-
-// Explicit API key (only when you must inject a specific key)
-const client = new Anthropic({ apiKey: "your-api-key" });
-```
-
----
-
-## Create an Environment
-
-```typescript
-const environment = await client.beta.environments.create(
-  {
-    name: "my-dev-env",
-    config: {
-      type: "cloud",
-      networking: { type: "unrestricted" },
-    },
-  },
-);
-console.log(environment.id); // env_...
-```
-
----
-
-## Create an Agent (required first step)
-
-> ⚠️ **There is no inline agent config.** `model`/`system`/`tools` live on the agent object, not the session. Always start with `agents.create()` — the session only takes `agent: { type: "agent", id: agent.id }`.
-
-### Minimal
-
-```typescript
-// 1. Create the agent (reusable, versioned)
-const agent = await client.beta.agents.create(
-  {
-    name: "Coding Assistant",
-    model: "claude-opus-5",
-    tools: [{ type: "agent_toolset_20260401", default_config: { enabled: true } }],
-  },
-);
-
-// 2. Start a session
-const session = await client.beta.sessions.create(
-  {
-    agent: { type: "agent", id: agent.id, version: agent.version },
-    environment_id: environment.id,
-  },
-);
-console.log(session.id, session.status);
-console.log(`Trace: https://platform.claude.com/workspaces/default/sessions/${session.id}`); // swap 'default' for your workspace ID if the API key is not in the Default workspace
-```
-
-### With system prompt and custom tools
-
-```typescript
-const agent = await client.beta.agents.create(
-  {
-    name: "Code Reviewer",
-    model: "claude-opus-5",
-    system: "You are a senior code reviewer.",
-    tools: [
-      { type: "agent_toolset_20260401", default_config: { enabled: true } },
-      {
-        type: "custom",
-        name: "run_tests",
-        description: "Run the test suite",
-        input_schema: {
-          type: "object",
-          properties: {
-            test_path: { type: "string", description: "Path to test file" },
-          },
-          required: ["test_path"],
-        },
-      },
-    ],
-  },
-);
-
-const session = await client.beta.sessions.create(
-  {
-    agent: { type: "agent", id: agent.id, version: agent.version },
-    environment_id: environment.id,
-    title: "Code review session",
-    resources: [
-      {
-        type: "github_repository",
-        url: "https://github.com/owner/repo",
-        mount_path: "/workspace/repo",
-        authorization_token: process.env.GITHUB_TOKEN,
-        branch: "main",
-      },
-    ],
-  },
-);
-```
-
----
-
-## Send a User Message
-
-```typescript
-await client.beta.sessions.events.send(
-  session.id,
-  {
-    events: [
-      {
-        type: "user.message",
-        content: [{ type: "text", text: "Review the auth module" }],
-      },
-    ],
-  },
-);
-```
-
-> 💡 **Stream-first:** Open the stream *before* (or concurrently with) sending the message. The stream only delivers events that occur after it opens — stream-after-send means early events arrive buffered in one batch. See [Steering Patterns](../../shared/managed-agents-events.md#steering-patterns).
-
----
-
-## Stream Events (SSE)
-
-```typescript
-// Stream-first: open stream and send concurrently
-const [events] = await Promise.all([
-  collectStream(session.id),
-  client.beta.sessions.events.send(
-    session.id,
-    { events: [{ type: "user.message", content: [{ type: "text", text: "..." }] }] },
-  ),
-]);
-
-// Standalone stream iteration:
-const stream = await client.beta.sessions.events.stream(
-  session.id,
-);
-
-for await (const event of stream) {
-  switch (event.type) {
-    case "agent.message":
-      for (const block of event.content) {
-        if (block.type === "text") {
-          process.stdout.write(block.text);
-        }
-      }
-      break;
-    case "agent.custom_tool_use":
-      // Custom tool invocation — session is now idle
-      console.log(`\nCustom tool call: ${event.name}`);
-      console.log(`Input: ${JSON.stringify(event.input)}`);
-      break;
-    case "session.status_idle":
-      console.log("\n--- Agent idle ---");
-      break;
-    case "session.status_terminated":
-      console.log("\n--- Session terminated ---");
-      break;
-  }
-}
-```
-
----
-
-## Provide Custom Tool Result
-
-```typescript
-await client.beta.sessions.events.send(
-  session.id,
-  {
-    events: [
-      {
-        type: "user.custom_tool_result",
-        custom_tool_use_id: "sevt_abc123",
-        content: [{ type: "text", text: "All 42 tests passed." }],
-      },
-    ],
-  },
-);
-```
-
----
-
-## Poll Events
-
-```typescript
-const events = await client.beta.sessions.events.list(
-  session.id,
-);
-for (const event of events.data) {
-  console.log(`${event.type}: ${event.id}`);
-}
-```
-
----
-
-## Full Streaming Loop with Custom Tools
-
-```typescript
-function runCustomTool(toolName: string, toolInput: unknown): string {
-  if (toolName === "run_tests") {
-    // Your tool implementation here
-    return "All tests passed.";
-  }
-  return `Unknown tool: ${toolName}`;
-}
-
-async function runSession(client: Anthropic, sessionId: string) {
-  while (true) {
-    const stream = await client.beta.sessions.events.stream(
-      sessionId,
-    );
-
-    const toolCalls: Anthropic.Beta.Sessions.BetaManagedAgentsAgentCustomToolUseEvent[] = [];
-
-    for await (const event of stream) {
-      if (event.type === "agent.message") {
-        for (const block of event.content) {
-          if (block.type === "text") {
-            process.stdout.write(block.text);
-          }
-        }
-      } else if (event.type === "agent.custom_tool_use") {
-        toolCalls.push(event);
-      } else if (event.type === "session.status_idle") {
-        break;
-      } else if (event.type === "session.status_terminated") {
-        return;
-      }
-    }
-
-    if (toolCalls.length === 0) break;
-
-    // Process custom tool calls
-    const results = toolCalls.map((call) => ({
-      type: "user.custom_tool_result" as const,
-      custom_tool_use_id: call.id,
-      content: [{ type: "text" as const, text: runCustomTool(call.name, call.input) }],
-    }));
-
-    await client.beta.sessions.events.send(
-      sessionId,
-      { events: results },
-    );
-  }
-}
-```
-
----
-
-## Upload a File
-
-```typescript
-import fs from "fs";
-
-const file = await client.beta.files.upload({
-  file: fs.createReadStream("data.csv"),
-});
-
-// Use in a session
-const session = await client.beta.sessions.create(
-  {
-    agent: { type: "agent", id: agent.id, version: agent.version },
-    environment_id: environment.id,
-    resources: [{ type: "file", file_id: file.id, mount_path: "/workspace/data.csv" }],
-  },
-);
-```
-
----
-
-## List and Download Session Files
-
-List files the agent wrote to `/mnt/session/outputs/` during a session, then download them.
-
-```typescript
-import fs from "fs";
-
-// List files associated with a session
-const files = await client.beta.files.list({
-  scope_id: session.id,
-  betas: ["managed-agents-2026-04-01"],
-});
-for (const f of files.data) {
-  console.log(f.filename, f.size_bytes);
-
-  // Download and save to disk
-  const resp = await client.beta.files.download(f.id);
-  const buffer = Buffer.from(await resp.arrayBuffer());
-  fs.writeFileSync(f.filename, buffer);
-}
-```
-
-> 💡 There's a brief indexing lag (~1–3s) between `session.status_idle` and output files appearing in `files.list`. Retry once or twice if the list is empty.
-
----
-
-## Session Management
-
-```typescript
-// Get session details
-const session = await client.beta.sessions.retrieve("sesn_011CZxAbc123Def456");
-console.log(session.status, session.usage);
-
-// List sessions
-const sessions = await client.beta.sessions.list();
-
-// Delete a session
-await client.beta.sessions.delete("sesn_011CZxAbc123Def456");
-
-// Archive a session
-await client.beta.sessions.archive("sesn_011CZxAbc123Def456");
-```
-
----
-
-## MCP Server Integration
-
-```typescript
-// Agent declares MCP server (no auth here — auth goes in a vault)
-const agent = await client.beta.agents.create({
-  name: "MCP Agent",
-  model: "claude-opus-5",
-  mcp_servers: [
-    { type: "url", name: "my-tools", url: "https://my-mcp-server.example.com/sse" },
-  ],
-  tools: [
-    { type: "agent_toolset_20260401", default_config: { enabled: true } },
-    { type: "mcp_toolset", mcp_server_name: "my-tools" },
-  ],
-});
-
-// Session attaches vault(s) containing credentials for those MCP server URLs
-const session = await client.beta.sessions.create({
-  agent: agent.id,
-  environment_id: environment.id,
-  vault_ids: [vault.id],
-});
-```
-
-See `shared/managed-agents-tools.md` §Vaults for creating vaults and adding credentials.

package/skills/code-security-auditor/SKILL.md

@@ -1,164 +0,0 @@
----
-name: code-security-auditor
-description: Perform pre-execution security audits of untrusted codebases through static analysis. Use when analyzing a codebase for potential malicious behavior, supply chain risks, or security vulnerabilities before local execution. Triggered by requests like "analyze this project for security risks", "audit this code before running", "check if this codebase is safe", or similar security review requests.
----
-
-# Code Security Auditor
-
-## Overview
-
-This skill enables OpenCode to perform a comprehensive pre-execution security audit of a given codebase and produce a structured, high-signal risk report. It analyzes the entire project including source code, dependency manifests, build scripts, and configuration files from a security-first perspective.
-
-## When to Use This Skill
-
-Use this skill when:
-- User requests security analysis of a codebase
-- User asks to "audit", "scan", or "check" code for safety before running
-- User wants to know if code is safe to execute locally
-- Analyzing untrusted or third-party code
-- Performing due diligence on new dependencies or projects
-
-## Analysis Workflow
-
-### Step 1: Understand the Project Scope
-
-1. Identify the primary language and ecosystem (JavaScript/Node, Python, Go, Ruby, etc.)
-2. Locate all dependency manifests:
-   - `package.json`, `package-lock.json` (Node.js)
-   - `requirements.txt`, `Pipfile`, `pyproject.toml` (Python)
-   - `Gemfile`, `Gemfile.lock` (Ruby)
-   - `go.mod`, `go.sum` (Go)
-   - `Cargo.toml` (Rust)
-   - `pom.xml`, `build.gradle`, `build.gradle.kts` (Java/Kotlin)
-3. Identify entry points: main scripts, entry files, startup commands
-
-### Step 2: Perform Static Analysis
-
-#### 1. Dependencies Audit
-
-Scan dependency manifests for:
-- Known malicious or compromised packages (check known malware databases)
-- Unmaintained packages (no recent updates, abandoned repos)
-- Newly published packages (< 30 days) with high download counts
-- Typosquatting risks (packages with similar names to popular libraries)
-- Packages with install-time scripts (`preinstall`, `postinstall`, `prepare`, `prepublish`)
-
-Reference: Use `references/package_checks.md` for known suspicious packages and patterns.
-
-#### 2. Script Inspection
-
-Examine all scripts for:
-- Lifecycle hooks in manifest files (`postinstall`, `preinstall`, `prepare`, `prepublish`)
-- Shell execution patterns: `exec`, `spawn`, backticks, `system()`, `os.system()`, `subprocess` calls
-- Dynamic code execution: `eval()`, `Function()`, `setTimeout()` with strings, `pickle.loads()`, `unserialize()`
-- Encoded payloads: base64, hex, obfuscated strings, string concatenation
-- Download and execute patterns: curl/wget piping to shell
-
-#### 3. File System Behavior
-
-Detect operations that:
-- Write outside the project directory
-- Access sensitive paths: `~/.ssh`, `~/.aws`, `/etc`, `/var`, `/proc`, `/sys`
-- Create hidden files: dotfiles in home directory, startup scripts
-- Modify system configuration: cron, systemd services, launch agents
-
-#### 4. Network Activity
-
-Identify:
-- Hardcoded IP addresses (especially external)
-- Hardcoded domains and endpoints
-- Suspicious URL patterns: data exfiltration endpoints, command-and-control
-- Unexpected ports or protocols
-- DNS lookups or reverse IP queries
-
-#### 5. Obfuscation and Evasion
-
-Flag:
-- Minified or obfuscated code (especially in dependencies)
-- Anti-debugging techniques: debugger detection, stack trace manipulation
-- Dynamic imports: `import()`, `require()` with variable paths
-- Runtime code generation: `eval()`, `new Function()`, `createElement` with strings
-
-### Step 3: Risk Assessment
-
-For each finding, assess:
-- **Impact**: What can happen if this code runs locally?
-- **Likelihood**: How likely is this to be malicious vs. legitimate?
-- **Evidence**: Specific file, line number, and code snippet
-
-#### Potential Impact Categories
-
-- **File system compromise**: Code that writes to arbitrary locations
-- **Credential theft**: Access to SSH keys, environment variables, tokens, passwords
-- **Remote command execution**: Network-enabled code execution capabilities
-- **Persistence**: Cron jobs, startup scripts, systemd services, launch agents
-- **Privilege escalation**: Code that requests or attempts to gain elevated privileges
-- **Data exfiltration**: Network transmission of sensitive data
-
-### Step 4: Generate Structured Report
-
-Produce output following the strict format in Output Format section.
-
-## Output Format
-
-### 🔴 Critical Risks
-
-Provide each critical risk with:
-- **Risk title**: Brief descriptive title
-- **Evidence**: File path, line number, specific code snippet
-- **Why it is dangerous**: Technical explanation of the risk
-- **What to verify manually**: Steps to confirm the finding
-
-### 🟠 Suspicious Findings
-
-Same structure as critical risks but lower severity.
-
-### 🟡 Low Risk / Observations
-
-Interesting findings that don't pose immediate danger but worth noting.
-
-### 🔍 Manual Review Checklist
-
-Provide actionable checklist items:
-- [ ] Verify specific package legitimacy
-- [ ] Check maintainer reputation
-- [ ] Review network connections
-- [ ] Audit file system operations
-- etc.
-
-### 🚨 Indicators of Malicious Intent
-
-List specific patterns that strongly indicate malicious code:
-- Obfuscated code executing commands
-- Suspicious network exfiltration
-- Persistence mechanism installation
-- Credential harvesting patterns
-
-### 🧾 Final Verdict
-
-Choose ONE and provide justification:
-- **SAFE TO RUN**: No significant risks identified
-- **SAFE WITH SANDBOX ONLY**: Risks exist but contained by sandbox
-- **HIGH RISK — DO NOT RUN**: Significant malicious indicators found
-
-## Constraints
-
-- DO NOT assume code is safe
-- DO NOT execute any code
-- DO NOT skip files
-- Prefer false positives over false negatives
-- Document all findings, even minor ones
-
-## Resources
-
-### scripts/
-
-This skill does not require executable scripts.
-
-### references/
-
-- `package_checks.md`: Reference for known suspicious packages, malware patterns, and risky dependency indicators
-
-### assets/
-
-This skill does not require assets.

package/skills/code-security-auditor/references/package_checks.md

@@ -1,59 +0,0 @@
-# Package Security Reference
-
-## Known Malicious Packages
-
-### npm / JavaScript
-
-| Package | Indicator | Notes |
-|---------|-----------|-------|
-| `pluggable-json` | Typosquat of `printable-json` | Data exfiltration |
-| `babel-node` (unofficial) | Typosquat | Malware distribution |
-| `eslint-scope` (compromised) | Historical supply chain attack | Credential theft |
-| `event-stream` (compromised) | Famous attack | Bitcoin stealing |
-| `flatmap-stream` | Embedded in event-stream attack | Cryptocurrency theft |
-| `crossenv` | Typosquat of `cross-env` | Malware distribution |
-| `hueter-json` | Typosquat | Suspicious behavior |
-
-### PyPI / Python
-
-| Package | Indicator | Notes |
-|---------|-----------|-------|
-| `reqs` | Typosquat of `reqwest` | Malware |
-| `pyyaml` (unofficial) | Typosquat | Backdoor |
-| `requests` (typo variants) | Typosquat | Various attacks |
-
-## Suspicious Patterns
-
-### Install-Time Scripts
-
-Red flags in package.json:
-- `postinstall`: Code runs after `npm install`
-- `preinstall`: Pre-installation hooks
-- `prepare`: Development dependency hook
-- `prepublish`: Publishing hook
-
-### Network Indicators
-
-Suspicious patterns:
-- Hardcoded IP addresses (especially non-local)
-- Base64-encoded domains
-- DNS lookups for reconnaissance
-- Data sent to external servers
-- Command and control patterns
-
-### File System Red Flags
-
-Dangerous operations:
-- Writing to `~/.npmrc`, `~/.ssh/`, `~/.aws/`
-- Modifying `/etc/hosts`
-- Creating cron jobs
-- Writing to `~/Library/LaunchAgents/`
-- Modifying systemd services
-
-## Quick Checks
-
-1. **Age**: Package published < 30 days with high download count = suspicious
-2. **Maintainer**: Single maintainer with no history = suspicious
-3. **Dependencies**: Heavy dependency tree = attack surface
-4. **Repository**: No GitHub link or dead link = suspicious
-5. **License**: No license or proprietary = investigate further