{"passport":{"unfragile":{"@version":"1.0","version":"2026-05","artifact":{"id":"github-ertugrulakben--cashclaw","slug":"ertugrulakben--cashclaw","name":"cashclaw","type":"agent","url":"https://cashclawai.com/","page_url":"https://unfragile.ai/ertugrulakben--cashclaw","categories":["ai-agents"],"tags":["ai-agent","autonomous-agent","cashclaw","cli","freelance","hyrve","monetization","npm-package","open-source","openclaw","stripe"],"pricing":{"model":"open_source","free":true,"starting_price":null},"status":"active","verified":false},"capabilities":[{"id":"github-ertugrulakben--cashclaw__cap_0","uri":"capability://automation.workflow.mission.lifecycle.state.machine.with.immutable.audit.trails","name":"mission-lifecycle state machine with immutable audit trails","description":"Manages complete service delivery workflows through a deterministic state machine (pending → accepted → executing → completed/failed) with every state transition persisted as immutable JSON records in ~/.cashclaw/missions/. Each mission is stored as a UUID-keyed JSON file capturing client request, work execution, and completion metadata. The Mission Runner (src/core/mission-runner.js) implements CRUD operations and enforces state validity, preventing invalid transitions and enabling forensic reconstruction of all work performed.","intents":["I need to track every step of an AI agent's work from client request through completion for accountability","I want an immutable record of what work was done, when, and by whom for dispute resolution","I need to ensure missions can only transition through valid states to prevent data corruption","I want to reconstruct the complete history of a failed mission for debugging"],"best_for":["autonomous AI agents performing freelance work requiring audit compliance","teams building self-billing systems where work history is legally required","developers implementing mission-based agent orchestration without external databases"],"limitations":["JSON file-based storage scales to ~10k missions before filesystem performance degrades","No built-in sharding or partitioning — all missions stored in single directory","State machine is hardcoded; custom workflows require code modification","Concurrent mission updates to same file can cause write conflicts without external locking"],"requires":["Node.js 18+","Write access to ~/.cashclaw/ directory","OpenClaw-compatible agent with skill registry"],"input_types":["client request object (JSON)","agent skill execution results (JSON)","completion status with metadata"],"output_types":["mission state object (JSON)","audit trail entries (JSON)","mission history timeline"],"categories":["automation-workflow","memory-knowledge"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"github-ertugrulakben--cashclaw__cap_1","uri":"capability://automation.workflow.autonomous.job.polling.and.auto.accept.daemon","name":"autonomous job polling and auto-accept daemon","description":"Runs a background polling loop that continuously queries the HYRVEai marketplace API (50+ endpoints) for new job postings matching the agent's configured skills, automatically accepts matching jobs based on configurable criteria, and transitions them into the mission lifecycle. The daemon implements exponential backoff for API failures, maintains polling state, and integrates with the HYRVEai Bridge (src/integrations/hyrve-bridge.js) for agent registration and job discovery. Auto-accept mode bypasses manual approval, enabling fully autonomous work acceptance.","intents":["I want my AI agent to continuously discover and accept work from a freelance marketplace without manual intervention","I need to configure which job types my agent auto-accepts based on skills and pricing thresholds","I want the polling daemon to handle API failures gracefully and retry with backoff","I need visibility into which jobs were discovered, accepted, and why some were rejected"],"best_for":["autonomous agents monetizing through HYRVEai marketplace integration","developers building self-operating freelance bots with minimal human oversight","teams testing agent autonomy with real marketplace demand signals"],"limitations":["Polling interval is fixed; no adaptive polling based on job frequency","Auto-accept criteria are static configuration — no dynamic learning from past job performance","No built-in rate limiting; can hit HYRVEai API quotas if polling interval is too aggressive","Job filtering logic is hardcoded; custom acceptance rules require code modification","No prioritization between competing jobs — accepts in discovery order"],"requires":["HYRVEai API credentials (agent ID, API key)","Active agent registration on HYRVEai marketplace","Configured skills matching marketplace job categories","Node.js 18+ with npm"],"input_types":["HYRVEai job posting objects (JSON)","agent skill configuration (JSON)","auto-accept criteria (JSON)"],"output_types":["accepted mission objects (JSON)","polling status logs (text)","rejection reason codes (text)"],"categories":["automation-workflow","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"github-ertugrulakben--cashclaw__cap_10","uri":"capability://memory.knowledge.immutable.mission.audit.trail.with.json.persistence.and.forensic.reconstruction","name":"immutable mission audit trail with json persistence and forensic reconstruction","description":"Maintains an immutable audit trail for every mission by recording all state transitions, skill executions, and payment events as JSON entries appended to mission records. Each mission file (UUID-keyed in ~/.cashclaw/missions/) contains a complete history of events with timestamps, actor information, and state snapshots. The audit trail enables forensic reconstruction of what happened during a mission, when it happened, and why it failed (if applicable). Entries are append-only; historical records cannot be modified or deleted, ensuring compliance with audit requirements.","intents":["I need a complete forensic record of everything that happened during a mission for debugging","I want to prove to clients what work was done and when for dispute resolution","I need to comply with audit requirements for financial and legal purposes","I want to analyze mission failures by reviewing the complete event history"],"best_for":["autonomous agents operating in regulated industries requiring audit trails","teams building self-billing systems with legal compliance requirements","developers debugging complex multi-step workflows"],"limitations":["Audit trail is append-only; no ability to correct erroneous entries (only add corrections)","JSON file size grows with mission history; very long missions can create large files","No built-in compression or archival; old missions consume disk space indefinitely","Forensic reconstruction requires manual JSON parsing; no built-in query tools","Timestamps are system clock-based; no protection against clock skew or manipulation","No cryptographic signing; audit trail can be modified by anyone with file access"],"requires":["Write access to ~/.cashclaw/missions/ directory","Sufficient disk space for mission history","Node.js 18+"],"input_types":["event type (string: state-transition, skill-execution, payment, etc.)","event data (JSON object)","timestamp (ISO 8601 or Unix timestamp)"],"output_types":["audit trail entry (JSON)","mission history timeline (JSON array)","forensic reconstruction report (text or JSON)"],"categories":["memory-knowledge","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"github-ertugrulakben--cashclaw__cap_11","uri":"capability://automation.workflow.initial.setup.wizard.with.interactive.configuration.prompts","name":"initial setup wizard with interactive configuration prompts","description":"Provides an interactive CLI wizard (src/cli/commands/init.js) that guides users through agent configuration on first run. The wizard prompts for agent identity (name, description), marketplace credentials (HYRVEai API key), payment settings (Stripe API key, pricing), and skill selection. Validates inputs in real-time, provides helpful error messages, and generates the initial config.json file. The wizard is idempotent; running it again updates configuration without losing existing mission data.","intents":["I want to set up my agent quickly without manually editing JSON configuration files","I need guidance on what configuration values are required and what they mean","I want to validate my configuration before starting the agent","I need to update my configuration later without losing mission history"],"best_for":["non-technical users setting up agents for the first time","developers quickly bootstrapping new agent instances","teams onboarding new agents with consistent configuration"],"limitations":["Wizard is interactive; cannot be automated or scripted easily","No support for batch configuration of multiple agents","Validation is basic; complex configuration rules are not checked","Wizard output is text-based; no structured output for programmatic consumption","Re-running the wizard overwrites all configuration; no selective updates"],"requires":["Node.js 18+ with npm","Interactive terminal (TTY) for prompts","HYRVEai and Stripe API credentials"],"input_types":["user responses to interactive prompts (strings)","API credentials (strings)"],"output_types":["config.json file (JSON)","setup completion message (text)"],"categories":["automation-workflow","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"github-ertugrulakben--cashclaw__cap_12","uri":"capability://automation.workflow.mission.status.querying.and.filtering.with.cli.and.rest.api","name":"mission status querying and filtering with cli and rest api","description":"Provides multiple interfaces for querying mission status: CLI commands (cashclaw mission list, cashclaw mission view) and REST API endpoints (/api/missions, /api/missions/:id). Supports filtering by status (pending, accepted, executing, completed, failed), time range, skill type, and earnings. Results can be displayed as formatted tables (CLI) or JSON (API). The status query layer reads from the mission audit trail and aggregates state information without requiring a separate database.","intents":["I want to see all my agent's missions and their current status","I need to filter missions by status to find pending work or completed jobs","I want to query mission details programmatically via REST API","I need to see which missions are in progress and which are waiting for payment"],"best_for":["developers monitoring agent operations via CLI or API","teams integrating mission status into dashboards or monitoring systems","autonomous agents needing to query their own mission history"],"limitations":["Filtering is client-side; no server-side indexing means large mission volumes are slow","No pagination support; querying thousands of missions returns all results at once","Time range filtering is approximate; no sub-second precision","REST API is read-only; mission updates require CLI or direct file manipulation","No caching; every query re-reads mission files from disk"],"requires":["Completed missions in ~/.cashclaw/missions/ directory","Node.js 18+ for CLI","Network access to port 3847 for REST API"],"input_types":["filter criteria (status, time range, skill type)","sort order (ascending/descending)","output format (table, JSON)"],"output_types":["mission list (formatted table or JSON array)","mission details (JSON object)","HTTP status codes (200, 404, 500)"],"categories":["automation-workflow","search-retrieval"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"github-ertugrulakben--cashclaw__cap_2","uri":"capability://data.processing.analysis.time.windowed.earnings.aggregation.and.financial.tracking","name":"time-windowed earnings aggregation and financial tracking","description":"Calculates earnings across configurable time windows (hourly, daily, weekly, monthly) by aggregating completed missions and their associated Stripe payments. The Earnings Tracker (src/core/earnings-tracker.js) implements time-windowed financial aggregations that query the mission audit trail and payment records, computing metrics like total revenue, mission count, average job value, and hourly rates. Results are cached and updated incrementally as new missions complete, enabling real-time earnings dashboards without full recalculation.","intents":["I want to see how much my AI agent has earned in the last hour, day, week, or month","I need to calculate hourly rates and average job values to optimize pricing","I want to track earnings trends over time to identify peak demand periods","I need to generate earnings reports for tax or business analytics purposes"],"best_for":["autonomous agents monetizing work and needing real-time earnings visibility","developers building agent dashboards with financial metrics","teams analyzing agent productivity and profitability across time periods"],"limitations":["Aggregations are computed from mission audit trail; no direct Stripe API queries for real-time payment status","Time window calculations assume system clock accuracy; no timezone-aware windowing","Caching strategy is in-memory only; earnings data is lost on process restart","No support for multi-currency aggregation; assumes single currency per agent","Refunds or payment reversals are not automatically reflected in historical aggregations"],"requires":["Completed missions in ~/.cashclaw/missions/ directory","Stripe payment records linked to missions","Node.js 18+"],"input_types":["mission completion records (JSON)","Stripe payment objects (JSON)","time window specification (ISO 8601 or relative)"],"output_types":["earnings summary object (JSON)","time-series earnings data (JSON array)","financial metrics (numbers: total, count, average, rate)"],"categories":["data-processing-analysis","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"github-ertugrulakben--cashclaw__cap_3","uri":"capability://tool.use.integration.openclaw.skill.installation.and.workspace.detection","name":"openclaw skill installation and workspace detection","description":"Automatically discovers, installs, and registers OpenClaw-compatible skills into the agent's workspace via the OpenClaw Bridge (src/integrations/openclaw-bridge.js). The bridge detects installed skills by scanning the workspace directory structure, validates skill schemas, and registers them into a runtime skill registry that mission execution can invoke. Supports 12 specialized skills for common freelance tasks (code generation, content writing, image processing, etc.), with extensibility for custom skills via the OpenClaw standard interface.","intents":["I want to install OpenClaw skills into my agent workspace and have them automatically discovered","I need to verify that installed skills are valid and compatible with my agent","I want to see which skills are available and what capabilities each provides","I need to add custom skills to my agent's capability set without modifying core code"],"best_for":["developers building OpenClaw-compatible agents with modular skill systems","teams managing multi-skill agents performing diverse freelance work","solo developers extending agent capabilities without forking the codebase"],"limitations":["Skill discovery is filesystem-based; requires skills to follow OpenClaw directory conventions","No version management for skills; installing a new version overwrites the old one","Skill validation is schema-only; no runtime capability testing before accepting jobs","No dependency resolution between skills; circular dependencies can cause runtime failures","Custom skills must implement full OpenClaw interface; partial implementations are rejected"],"requires":["OpenClaw-compatible skill packages (npm modules or local directories)","Node.js 18+ with npm","Write access to agent workspace directory","Valid OpenClaw skill schema (JSON)"],"input_types":["skill package metadata (package.json)","skill schema definition (JSON)","skill implementation code (JavaScript)"],"output_types":["skill registry object (JSON)","installed skills list (JSON array)","skill validation report (JSON)"],"categories":["tool-use-integration","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"github-ertugrulakben--cashclaw__cap_4","uri":"capability://tool.use.integration.stripe.payment.link.generation.and.invoice.creation","name":"stripe payment link generation and invoice creation","description":"Generates Stripe payment links and invoices for completed missions via the Stripe Bridge (src/integrations/stripe-connect.js). When a mission completes, the system creates a Stripe invoice with mission details (description, amount, client info), generates a unique payment link, and stores the link in the mission record. Supports customer management (creating or retrieving Stripe customers by email), automatic payment collection, and webhook integration for payment confirmation. All payment state is persisted to mission records, enabling reconciliation between work completed and payments received.","intents":["I want to automatically generate payment links for completed work so clients can pay immediately","I need to create Stripe invoices with mission details for accounting and client records","I want to track which missions have been paid and which are still outstanding","I need to handle payment confirmations and update mission status when payment is received"],"best_for":["autonomous agents collecting payments for freelance work via Stripe","developers building self-billing systems with minimal payment infrastructure","teams monetizing AI agents with automated invoicing and payment collection"],"limitations":["Stripe API calls are synchronous; payment link generation adds latency to mission completion","No built-in retry logic for failed payment link generation; failed payments are not automatically retried","Customer management is email-based; no support for multiple payment methods per customer","Webhook handling requires external HTTPS endpoint; not suitable for agents behind firewalls","No support for partial payments or payment plans; invoices are all-or-nothing","Currency is fixed at agent configuration time; no multi-currency support"],"requires":["Stripe API key (secret key for server-side operations)","Stripe Connect account for payment collection","Valid Stripe customer email address","Node.js 18+ with Stripe npm package"],"input_types":["mission completion object (JSON)","client email address (string)","mission amount in cents (number)"],"output_types":["Stripe payment link (URL string)","Stripe invoice object (JSON)","payment status (pending/paid/failed)"],"categories":["tool-use-integration","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"github-ertugrulakben--cashclaw__cap_5","uri":"capability://automation.workflow.cli.command.routing.with.commander.js.and.hierarchical.command.structure","name":"cli command routing with commander.js and hierarchical command structure","description":"Implements a hierarchical command-line interface using Commander.js that routes user commands to business logic handlers. The CLI Entry Point (bin/cashclaw.js) loads the Command Router (src/cli/index.js) which parses commands and delegates to handler files organized by domain (missions, config, skills, status). Supports subcommands (e.g., `cashclaw mission accept`, `cashclaw config set`), global options (verbosity, config path), and help text generation. Each command handler is a separate module that imports core business logic and executes it with parsed arguments.","intents":["I want to manage my agent's missions from the command line (accept, list, complete, view details)","I need to configure agent settings (skills, pricing, marketplace credentials) via CLI","I want to check the status of my agent and current earnings without opening a web dashboard","I need to manage skills (install, list, remove) from the command line"],"best_for":["developers managing agents via SSH or CI/CD pipelines","solo developers preferring command-line interfaces over web dashboards","teams automating agent operations through shell scripts"],"limitations":["Commander.js parsing adds ~50ms overhead per command execution","No built-in command history or autocomplete; requires shell integration for convenience","Error messages are text-based; no structured error codes for programmatic handling","No built-in rate limiting on CLI commands; rapid-fire commands can overwhelm the system","Global options are parsed at CLI layer; not available to all handlers without explicit passing"],"requires":["Node.js 18+ with npm","Commander.js npm package (included in dependencies)","Bash or compatible shell for command execution"],"input_types":["command name (string)","subcommand (string)","command arguments (strings)","global options (flags)"],"output_types":["command output (text or JSON)","exit code (0 for success, non-zero for error)","structured error messages (JSON with --json flag)"],"categories":["automation-workflow","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"github-ertugrulakben--cashclaw__cap_6","uri":"capability://automation.workflow.express.based.web.dashboard.with.rest.api.on.port.3847","name":"express-based web dashboard with rest api on port 3847","description":"Provides a web-based dashboard server (src/dashboard/server.js) running on port 3847 that exposes a REST API for querying mission status, earnings, and agent configuration. The dashboard server reads from the same JSON-based state files as the CLI, enabling real-time visibility into agent operations without requiring a separate database. Supports endpoints for mission listing, earnings queries, skill status, and configuration retrieval. The dashboard UI consumes these REST endpoints to display interactive charts, mission timelines, and earnings trends.","intents":["I want to monitor my agent's mission status and earnings in real-time via a web interface","I need to see which missions are pending, executing, or completed without using the CLI","I want to visualize earnings trends and productivity metrics over time","I need to programmatically query agent status via REST API for integration with other systems"],"best_for":["developers monitoring multiple agents across different machines","non-technical founders wanting visual dashboards without CLI knowledge","teams integrating CashClaw status into larger monitoring systems via REST API"],"limitations":["Dashboard reads from JSON files; no caching layer means every API request re-reads disk","No authentication or authorization; dashboard is accessible to anyone with network access","REST API is read-only; mission updates must go through CLI or direct file manipulation","Dashboard server is single-threaded; high request volume can cause slowdowns","No WebSocket support; real-time updates require polling at regular intervals","Port 3847 is hardcoded; no configuration option to change the listening port"],"requires":["Node.js 18+ with Express.js npm package","Network access to port 3847 (may require firewall rules)","Modern web browser for dashboard UI (Chrome, Firefox, Safari, Edge)"],"input_types":["HTTP GET requests to REST endpoints","query parameters for filtering (mission status, time range, etc.)"],"output_types":["JSON responses from REST API","HTML dashboard UI with embedded charts","HTTP status codes (200, 404, 500, etc.)"],"categories":["automation-workflow","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"github-ertugrulakben--cashclaw__cap_7","uri":"capability://automation.workflow.json.based.configuration.management.with.defaults.merging","name":"json-based configuration management with defaults merging","description":"Manages agent configuration through JSON files stored in ~/.cashclaw/config.json, with automatic defaults merging via the Config Manager (src/utils/config.js). The system loads user configuration, merges it with built-in defaults, and validates against a configuration schema. Supports hierarchical configuration (global settings, skill-specific settings, marketplace-specific settings) with environment variable overrides. Configuration changes are persisted immediately to disk, enabling runtime updates without process restart.","intents":["I want to configure my agent's identity, skills, and pricing in a single configuration file","I need to set marketplace credentials (HYRVEai API key, Stripe key) securely","I want to override configuration via environment variables for containerized deployments","I need to validate my configuration before starting the agent to catch errors early"],"best_for":["developers deploying agents in containerized environments (Docker, Kubernetes)","teams managing configuration across multiple agent instances","solo developers wanting simple file-based configuration without external services"],"limitations":["No encryption for sensitive values (API keys, Stripe keys) in config.json; stored in plaintext","Configuration changes require manual file editing or CLI commands; no hot-reload on file changes","No version control for configuration history; overwrites are permanent","Schema validation is basic; no support for complex nested validation rules","Environment variable overrides are limited to top-level keys; no nested path support","No built-in secrets management; API keys must be managed externally (e.g., .env files)"],"requires":["Write access to ~/.cashclaw/ directory","Node.js 18+","Valid JSON syntax in config.json"],"input_types":["JSON configuration object","environment variables (KEY=value)","CLI configuration commands"],"output_types":["merged configuration object (JSON)","validation report (JSON with errors if invalid)"],"categories":["automation-workflow","data-processing-analysis"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"github-ertugrulakben--cashclaw__cap_8","uri":"capability://tool.use.integration.hyrveai.marketplace.agent.registration.and.job.discovery.api.integration","name":"hyrveai marketplace agent registration and job discovery api integration","description":"Integrates with HYRVEai's 50+ API endpoints via the HYRVEai Bridge (src/integrations/hyrve-bridge.js) to register agents on the marketplace, discover job postings, and manage agent availability. The bridge handles authentication (API key-based), implements request/response serialization, and manages the polling daemon that continuously queries for new jobs. Supports filtering jobs by skill category, minimum price, and other criteria. Integration points include agent registration (creating/updating agent profile), job discovery (querying available jobs), and job acceptance (claiming jobs and transitioning them to missions).","intents":["I want to register my AI agent on the HYRVEai marketplace so it can receive job requests","I need to discover new job postings that match my agent's skills and pricing requirements","I want to automatically accept jobs from the marketplace and convert them to missions","I need to update my agent's availability and skill set on the marketplace"],"best_for":["autonomous agents monetizing through HYRVEai marketplace","developers building agent-as-a-service platforms with marketplace integration","teams testing agent autonomy with real marketplace demand"],"limitations":["HYRVEai API is external; network outages or API downtime blocks job discovery","API rate limits are not explicitly handled; rapid polling can trigger rate limiting","Job filtering is client-side; no server-side filtering reduces efficiency for large job volumes","Agent registration is one-time; profile updates require manual API calls or CLI commands","No built-in job priority or ranking; jobs are processed in discovery order","API response format is tightly coupled to HYRVEai's schema; schema changes require code updates"],"requires":["HYRVEai API credentials (agent ID, API key)","Active HYRVEai account with agent profile","Network connectivity to HYRVEai API endpoints","Node.js 18+ with HTTP client library (axios or similar)"],"input_types":["HYRVEai API credentials (strings)","agent profile metadata (JSON)","job filter criteria (JSON)"],"output_types":["agent registration confirmation (JSON)","job posting objects (JSON array)","job acceptance confirmation (JSON)"],"categories":["tool-use-integration","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"github-ertugrulakben--cashclaw__cap_9","uri":"capability://automation.workflow.mission.skill.execution.orchestration.with.openclaw.bindings","name":"mission skill execution orchestration with openclaw bindings","description":"Orchestrates the execution of OpenClaw skills during mission execution by invoking registered skills with mission-specific parameters and aggregating results. When a mission transitions to the executing state, the system determines which skills are required based on the job type, invokes each skill with appropriate inputs, and captures outputs for the audit trail. The orchestration layer handles skill invocation errors, implements retry logic for transient failures, and updates mission status based on skill execution results. Supports parallel skill execution for independent tasks and sequential execution for dependent tasks.","intents":["I want my agent to execute the right skills for each job type automatically","I need to handle skill execution failures gracefully and retry on transient errors","I want to capture skill outputs and include them in the mission audit trail","I need to orchestrate complex workflows with multiple dependent skills"],"best_for":["developers building multi-skill agents with complex workflows","teams automating diverse freelance tasks (code generation, writing, image processing)","autonomous agents performing end-to-end service delivery"],"limitations":["Skill execution is synchronous; long-running skills block mission progress","No built-in timeout handling; skills that hang indefinitely can stall missions","Error handling is basic; no automatic fallback to alternative skills","Skill dependencies are hardcoded; no dynamic workflow generation based on job requirements","Parallel execution is not implemented; all skills execute sequentially","Skill output validation is minimal; malformed outputs can corrupt mission records"],"requires":["Registered OpenClaw skills in agent workspace","Valid skill schema definitions (JSON)","Node.js 18+ with skill execution runtime"],"input_types":["mission object with job details (JSON)","skill parameters derived from job (JSON)","skill registry with available skills (JSON)"],"output_types":["skill execution results (JSON)","mission status update (JSON)","audit trail entries (JSON)"],"categories":["automation-workflow","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0}],"trust":{"score":43,"verified":false,"data_access_risk":"high","permissions":["Node.js 18+","Write access to ~/.cashclaw/ directory","OpenClaw-compatible agent with skill registry","HYRVEai API credentials (agent ID, API key)","Active agent registration on HYRVEai marketplace","Configured skills matching marketplace job categories","Node.js 18+ with npm","Write access to ~/.cashclaw/missions/ directory","Sufficient disk space for mission history","Interactive terminal (TTY) for prompts"],"failure_modes":["JSON file-based storage scales to ~10k missions before filesystem performance degrades","No built-in sharding or partitioning — all missions stored in single directory","State machine is hardcoded; custom workflows require code modification","Concurrent mission updates to same file can cause write conflicts without external locking","Polling interval is fixed; no adaptive polling based on job frequency","Auto-accept criteria are static configuration — no dynamic learning from past job performance","No built-in rate limiting; can hit HYRVEai API quotas if polling interval is too aggressive","Job filtering logic is hardcoded; custom acceptance rules require code modification","No prioritization between competing jobs — accepts in discovery order","Audit trail is append-only; no ability to correct erroneous entries (only add corrections)","builder identity is not verified yet","no observed match outcomes yet"],"rank_breakdown":{"adoption":0.325279473895142,"quality":0.5,"ecosystem":0.6000000000000001,"match_graph":0.25,"freshness":0.75,"weights":{"adoption":0.25,"quality":0.25,"ecosystem":0.1,"match_graph":0.28,"freshness":0.12}},"observed_outcomes":{"matches":0,"success_rate":0,"avg_confidence":0,"top_intents":[],"last_matched_at":null},"maintenance":{"status":"active","updated_at":"2026-05-24T12:16:21.550Z","last_scraped_at":"2026-05-03T13:57:09.058Z","last_commit":"2026-04-05T00:35:20Z"},"community":{"stars":253,"forks":98,"weekly_downloads":null,"model_downloads":null,"model_likes":null}},"distribution":{"claim_url":"https://unfragile.ai/submit?claim=ertugrulakben--cashclaw","compare_url":"https://unfragile.ai/compare?artifact=ertugrulakben--cashclaw"}},"signature":"h1FgoBvx2OMRu+iTBf2sz4FLkFPbuluxy1ZOPj5GcrHVbmoG9/l/M80ZHKCZU6PJeujBnOxYBipSjfEuKQolAg==","signedAt":"2026-06-21T15:58:21.168Z","signedBy":"unfragile.ai","version":1},"_links":{"self":"https://unfragile.ai/api/v1/passport/ertugrulakben--cashclaw","artifact":"https://unfragile.ai/ertugrulakben--cashclaw","verify":"https://unfragile.ai/api/v1/verify?slug=ertugrulakben--cashclaw","publicKey":"https://unfragile.ai/api/v1/trust-passport-public-key","spec":"https://unfragile.ai/trust","schema":"https://unfragile.ai/schema.json","docs":"https://unfragile.ai/docs"}}