Agentpathfinder

v1.2.7

Unlimited tamper-evident cryptographic task tracking for AI agents. Green = proven complete. Red = failed or incomplete. Free forever — no usage caps, no tel...

0· 190·0 current·0 all-time

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for certainlogicai/agentpathfinder-agent-task-tracker-free.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Agentpathfinder" (certainlogicai/agentpathfinder-agent-task-tracker-free) from ClawHub.
Skill page: https://clawhub.ai/certainlogicai/agentpathfinder-agent-task-tracker-free
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Bare skill slug

openclaw skills install agentpathfinder-agent-task-tracker-free

ClawHub CLI

Package manager switcher

npx clawhub@latest install agentpathfinder-agent-task-tracker-free
Security Scan
Capability signals
CryptoCan make purchasesRequires sensitive credentials
These labels describe what authority the skill may exercise. They are separate from suspicious or malicious moderation verdicts.
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
The name/description describe cryptographic, tamper‑evident task tracking and the included code (key generation, XOR sharding, HMAC audit trail, CLI/SDK hooks, local vault) implements exactly that. No unexpected cloud credentials, SDKs, or unrelated dependencies are requested.
Instruction Scope
Runtime instructions and examples operate on local data in ~/.agentpathfinder and describe offline operation. The example Python bindings show running arbitrary subprocesses (pytest, docker commands) — expected for a task runner, but it means bound step functions can execute arbitrary system commands. The SKILL.md and SAFETY.md assert 'no telemetry' and local-only storage; the code indeed writes exclusively to a data directory under the user's home. Small doc/code mismatches: SKILL.md says data in ~/.agentpathfinder; TaskEngine defaults to ~/.agentpathfinder/pathfinder_data. Also SAFETY.md claims MIT-0 while README/SKILL.md claim MIT — license string mismatch.
Install Mechanism
No remote download/install URL is embedded in the skill manifest; it's an instruction-and-code package with setup.py/requirements.txt included. There is no evidence of fetching arbitrary code from a third‑party server during runtime. Installation writes files under the user's home directory (normal for a CLI tool).
Credentials
The skill declares no required environment variables or external credentials. It manages its own local agent shared secrets in ~/.agentpathfinder/agents/registry.json (expected for agent authentication). There are no unrelated credentials requested.
Persistence & Privilege
The skill persists data and secret shards on disk in the user's home directory (creates ~/.agentpathfinder/*). always:true is not set. This is expected for a local vault-style tool, but it means anyone or any process with filesystem access to that directory can read shards (the project documents this limitation and suggests Pro/Enterprise fixes).
Assessment
This package appears internally consistent with its stated purpose (local, tamper‑evident task tracking). Before installing or running it, consider these practical checks: - Inspect the shipped code (you can review the included Python files) and confirm you trust the publisher/repo before running pf install or pip install. The package runs locally and writes secrets to your home directory. - Run it in an isolated environment (VM, container, or dedicated user account) if you plan to bind steps that run system commands (examples show docker and subprocess usage). Bound step functions can execute arbitrary commands — that's a feature for automation but also a risk if agents or step code are untrusted. - Protect the data directory (~/.agentpathfinder or ~/.agentpathfinder/pathfinder_data) with filesystem permissions and avoid using it on multi‑user/shared machines unless you accept that anyone with access to that directory can read shards. The free tier is explicitly "tamper‑evident, not tamper‑proof." If you need stronger guarantees, follow the project's stated upgrade path (hosted vault/TEE) when available. - Verify the repository/source you install from (signed releases or a trustworthy GitHub repo). There are small doc mismatches (data path and license string) worth noting but not security‑critical by themselves. - Consider running a test with harmless tasks first and inspect the files created under your home directory to confirm what is stored and ensure no unexpected network activity occurs. If you want additional assurance, provide the exact install command/source URL you intend to use (clawhub or pip/GitHub), and I can re-check for remote install URLs or publish artifacts that would change the assessment.

Like a lobster shell, security has layers — review code before you run it.

latestvk97fyrs12gwspdr7e2fnvd5qkn85nbw3open-sourcevk97fyrs12gwspdr7e2fnvd5qkn85nbw3tamper-evidentvk97fyrs12gwspdr7e2fnvd5qkn85nbw3task-trackingvk97fyrs12gwspdr7e2fnvd5qkn85nbw3
190downloads
0stars
20versions
Updated 17h ago
v1.2.7
MIT-0

AgentPathfinder

Green = cryptographically proven complete. Red = not. Dead simple in every reply.

AgentPathfinder gives your AI agents cryptographic proof of task completion. Decompose any task into N steps, shard a master key across them via XOR, and only reconstruct the key when every step finishes successfully. Every event is HMAC-SHA256 signed and written to an append-only audit trail.

Free forever, unlimited tasks, no usage caps. Upgrade when you want a dashboard, multi-agent views, or exportable audit files.

What You Get

FeatureHow It Works
✅ Unlimited tamper-evident trackingGreen/red in every message
✅ Cryptographic sharding256-bit master key → N+1 shards via XOR
✅ Audit trailHMAC-SHA256 signed, append-only JSONL
✅ Crash recoveryAtomic writes + fsync + rename
✅ CLI with visual confirmationspf status shows ✅/❌/⏳ at a glance

Pro (coming soon): Dashboard, multi-agent tracking, audit exports, webhooks.

Enterprise: On-prem, SSO/SAML, hosted vault for compliance.

Install

clawhub install agentpathfinder

Then verify:

pf install

Quickstart

# Create a 4-step deployment task
pf create "deploy_api" "run_tests" "build_docker" "push_registry" "restart_service"
# → Task created: a7f3d2e1-...

# Run it (simulation mode — see what it looks like)
pf run a7f3d2e1-...
# → ⏳ SIMULATION MODE — No real code executed.
#    ✅ deploy_api is complete! Progress: 4/4
#    ✅ Step 1 complete: run_tests (token: tok_abc123…)
#    ✅ Step 2 complete: build_docker (token: tok_def456…)

# Check status — one glance says it all
pf status a7f3d2e1-...
# → ✅ task_complete 4/4 (all green)

# Verify audit integrity
pf audit a7f3d2e1-...
# → ✅ All 6 events verified

# Reconstruct the master key (only works when all steps pass)
pf reconstruct a7f3d2e1-...
# → ✅ Key reconstructed successfully

Real Execution (Python SDK)

The CLI marks steps complete for demo. For real automation, bind Python functions:

from pathfinder_client import PathfinderClient
from agentpathfinder import AgentRuntime

pf = PathfinderClient()
tid = pf.create("deploy", ["test", "build", "push"])

# Bind real functions
def run_tests():
    subprocess.run(["pytest", "-v"], check=True)
    return "passed"

def build_docker():
    subprocess.run(["docker", "build", "-t", "app", "."], check=True)
    return "app:latest"

# Execute
runtime = AgentRuntime(pf.engine, pf.issuing)
runtime.execute_task(tid, {
    "test": run_tests,
    "build": build_docker,
    "push": lambda: subprocess.run(["docker", "push", "app"], check=True),
})

# If any step fails → task pauses, audit trail shows exactly what happened
# Retry after fixing:
runtime.retry_step(tid, 2, build_docker)

Architecture

┌─────────────┐  create_task()   ┌──────────────┐
│   CLI/SDK   │ ───────────────▶ │  TaskEngine  │
│ (pf create) │                  │              │
└─────────────┘                  │ - Generate K │
                                 │ - Split(K,N) │
                                 │ - Write JSON │
                                 └──────────────┘
                                        │
                                 Vault: step shards
                                 Tasks: metadata only
                                        │
┌─────────────┐         ┌──────────────┘
│ AgentRuntime│◄────────│ IssuingLayer │
│(execute_step│  token  │              │
└─────────────┘         │ - HMAC sign  │
        │               │ - Audit log  │
        ▼               └──────────────┘
┌─────────────┐                ▲
│ AuditTrail  │◄───────────────┘
│(JSONL+HMAC) │
└─────────────┘

Security

Tamper-evident, not tamper-proof. Every event is HMAC-SHA256 signed with a derived audit key. If someone modifies the audit trail or task files, verification fails and you know immediately.

Current limitations: A malicious agent with filesystem access to ~/.agentpathfinder/vault/ could read shards and reconstruct the key. For full isolation, upgrade to Pro (hosted vault) or Enterprise (TEE/remote attestation).

FeatureHow It Works
Cryptographic sharding256-bit master key split into N+1 shards via XOR
Atomic persistencetemp + fsync + rename — no partial writes
Crash recoverySteps in running state detected and reset
Concurrency controlAdvisory file locks per task
Audit integrityHMAC-SHA256 chain, any edit breaks verification
Agent authenticationShared-secret HMAC tokens per agent

Data Storage

All data stays in ~/.agentpathfinder/ only. No external servers, no telemetry, no analytics.

WhatWhereContent
Task metadata~/.agentpathfinder/tasks/*.jsonTask name, steps, status
Vault shards~/.agentpathfinder/vault/*.shard32-byte shards per step
Audit trail~/.agentpathfinder/audit/*.jsonlHMAC-signed events
Agent config~/.agentpathfinder/agents/registry.jsonAgent IDs, shared secrets

CLI Reference

CommandWhat It Does
pf installOne-command setup, verify deps
pf create <name> [steps...]Create a new sharded task
pf run <task_id>Simulate running all steps
pf status <task_id>Visual status: ✅/❌/⏳ at a glance
pf audit <task_id>Show tamper-verified audit trail
pf reconstruct <task_id>Reconstruct master key (all steps required)
pf register-agent <id>Register an agent for authenticated execution
pf dashboardGenerate static HTML dashboard

Dashboard

# Generate a static HTML dashboard (no server needed)
python3 scripts/dashboard_static.py --output report.html
# Open report.html in your browser

# Or start live dashboard (requires Flask)
pf dashboard --port 8080
# Open http://localhost:8080

The dashboard shows:

  • Tasks tab: Live status, progress bars, step icons
  • Audit tab: Recent events with timestamps
  • Data storage: Confirms everything is local in ~/.agentpathfinder/

Troubleshooting

ProblemFix
"agentpathfinder not found"Run pf install to verify setup
"Task not found"Check task ID. Use pf status to list recent tasks
"Reconstruction failed"Not all steps complete. Run pf status to see which
"Step already running"Previous run crashed. Auto-reset or call reset_running_step()
"Agent auth failed"Re-run pf register-agent <id>
Dashboard won't startInstall Flask: pip install flask
Audit reports tamperedFiles were modified outside the engine. Investigate immediately

License

MIT. Free forever. No usage caps. Pro dashboard coming soon.


Built by CertainLogic — deterministic AI, cryptographic proof.

Comments

Loading comments...