
Claw Code Harness
- 720 installs
- 66 repo stars
- Updated July 9, 2026
- aradotso/trending-skills
claw-code-harness is a Claude skill that inspects, audits, and inventories Claude Code agent capabilities through a clean-room Python harness with CLI tooling for manifest and parity analysis.
About
claw-code-harness is a skill from aradotso/trending-skills for Claw Code—a clean-room Python rewrite of the Claude Code agent harness with an in-progress Rust port. The skill exposes CLI workflows for manifest inspection, parity auditing, tool and command inventory, subsystem listing, and tool port metadata review. Documented triggers include phrases like set up claw-code harness, run parity audit claw-code, and claw-code manifest summary. Developers reach for it when comparing harness behavior, auditing tool coverage, or exploring subsystem boundaries without spelunking minified upstream internals. The Daily 2026 Skills collection positions it for engineers porting, testing, or documenting agent harness capabilities from ara.so. Use it during agent platform work when inventory accuracy and parity evidence matter before shipping custom tool integrations.
- Python rewrite of the Claude Code agent harness with CLI tooling
- Manifest inspection, parity auditing, and tool/command inventory features
- Subsystems enumeration and tool port metadata queries
- Importable Python modules plus Rust port in progress
- Zero external dependencies for core functionality
Claw Code Harness by the numbers
- 720 all-time installs (skills.sh)
- +6 installs in the week ending Jul 13, 2026 (Skillselion tracking)
- Ranked #1,381 of 16,659 AI & Agent Building skills by installs in the Skillselion catalog
- Security screen: HIGH risk (skills.sh audit)
- Data as of Jul 19, 2026 (Skillselion catalog sync)
npx skills add https://github.com/aradotso/trending-skills --skill claw-code-harnessAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 720 |
|---|---|
| repo stars | ★ 66 |
| Security audit | 1 / 3 scanners passed |
| Last updated | July 9, 2026 |
| Repository | aradotso/trending-skills ↗ |
How do you audit Claude Code harness tool parity?
Inspect, audit, and inventory Claude Code agent capabilities from a clean Python implementation.
Who is it for?
Engineers building or auditing Claude Code harness ports who need CLI-driven manifest and parity inventories.
Skip if: Application feature development unrelated to agent harness internals or tool registration.
When should I use this skill?
Manifest inspection, parity auditing, or tool/command inventory is needed for a Claw Code Python harness session.
What you get
Manifest summary, parity audit report, command inventory, subsystem list, and tool port metadata.
- manifest summary
- parity audit report
- command inventory
By the numbers
- Documents 8 trigger phrases for manifest, parity, and inventory workflows
- Python harness rewrite with in-progress Rust port
Files
Claw Code Harness
Skill by ara.so — Daily 2026 Skills collection.
Claw Code is a clean-room Python (with Rust port in progress) rewrite of the Claude Code agent harness. It provides tooling to inspect the port manifest, enumerate subsystems, audit parity against an archived source, and query tool/command inventories — all via a CLI entrypoint and importable Python modules.
---
Installation
# Clone the repository
git clone https://github.com/instructkr/claw-code.git
cd claw-code
# Install dependencies (standard library only for core; extras for dev)
pip install -r requirements.txt # if present, else no external deps required
# Verify the workspace
python3 -m unittest discover -s tests -vNo PyPI package yet — use directly from source.
---
Repository Layout
.
├── src/
│ ├── __init__.py
│ ├── commands.py # Python-side command port metadata
│ ├── main.py # CLI entrypoint
│ ├── models.py # Dataclasses: Subsystem, Module, BacklogState
│ ├── port_manifest.py # Current Python workspace structure summary
│ ├── query_engine.py # Renders porting summary from active workspace
│ ├── task.py # Task primitives
│ └── tools.py # Python-side tool port metadata
└── tests/ # Unittest suite---
CLI Reference
All commands are invoked via python3 -m src.main <command>.
summary
Render the full Python porting summary.
python3 -m src.main summarymanifest
Print the current Python workspace manifest (file surface + subsystem names).
python3 -m src.main manifestsubsystems
List known subsystems, with optional limit.
python3 -m src.main subsystems
python3 -m src.main subsystems --limit 16commands
Inspect mirrored command inventory.
python3 -m src.main commands
python3 -m src.main commands --limit 10tools
Inspect mirrored tool inventory.
python3 -m src.main tools
python3 -m src.main tools --limit 10parity-audit
Run parity audit against a locally present (gitignored) archived snapshot.
python3 -m src.main parity-auditRequires the local archive to be present at its expected path (not tracked in git).
---
Core Modules & API
src/models.py — Dataclasses
from src.models import Subsystem, Module, BacklogState
# A subsystem groups related modules
sub = Subsystem(name="tool-harness", modules=[], status="in-progress")
# A module represents a single ported file
mod = Module(name="tools.py", ported=True, notes="tool metadata only")
# BacklogState tracks overall port progress
state = BacklogState(
total_subsystems=8,
ported=5,
backlog=3,
notes="runtime slices pending"
)src/tools.py — Tool Port Metadata
from src.tools import get_tools, ToolMeta
tools: list[ToolMeta] = get_tools()
for t in tools[:5]:
print(t.name, t.ported, t.description)src/commands.py — Command Port Metadata
from src.commands import get_commands, CommandMeta
commands: list[CommandMeta] = get_commands()
for c in commands[:5]:
print(c.name, c.ported)src/query_engine.py — Porting Summary Renderer
from src.query_engine import render_summary
summary_text: str = render_summary()
print(summary_text)src/port_manifest.py — Manifest Access
from src.port_manifest import get_manifest, ManifestEntry
entries: list[ManifestEntry] = get_manifest()
for entry in entries:
print(entry.path, entry.status)---
Common Patterns
Pattern 1: Check how many tools are ported
from src.tools import get_tools
tools = get_tools()
ported = [t for t in tools if t.ported]
print(f"{len(ported)}/{len(tools)} tools ported")Pattern 2: Find unported subsystems
from src.port_manifest import get_manifest
backlog = [e for e in get_manifest() if e.status != "ported"]
for entry in backlog:
print(f"BACKLOG: {entry.path}")Pattern 3: Programmatic summary pipeline
from src.query_engine import render_summary
from src.commands import get_commands
from src.tools import get_tools
print("=== Summary ===")
print(render_summary())
print("\n=== Commands ===")
for c in get_commands(limit=5):
print(f" {c.name}: ported={c.ported}")
print("\n=== Tools ===")
for t in get_tools(limit=5):
print(f" {t.name}: ported={t.ported}")Pattern 4: Run tests before contributing
python3 -m unittest discover -s tests -vPattern 5: Using as part of an OmX/agent workflow
# Generate summary artifact for an agent to consume
python3 -m src.main summary > /tmp/claw_summary.txt
# Feed into another agent tool or diff against previous checkpoint
diff /tmp/claw_summary_prev.txt /tmp/claw_summary.txt---
Rust Port (In Progress)
The Rust rewrite is on the `dev/rust` branch.
# Switch to the Rust branch
git fetch origin dev/rust
git checkout dev/rust
# Build (requires Rust toolchain: https://rustup.rs)
cargo build
# Run
cargo run -- summaryThe Rust port aims for a faster, memory-safe harness runtime. It is not yet merged into main. Until then, use the Python implementation for all production workflows.
---
Troubleshooting
| Problem | Cause | Fix |
|---|---|---|
ModuleNotFoundError: No module named 'src' | Running from wrong directory | cd to repo root, then python3 -m src.main ... |
parity-audit exits with "archive not found" | Local snapshot not present | Place the archive at the expected local path (see port_manifest.py for the path constant) |
| Tests fail with import errors | Missing __init__.py | Ensure src/__init__.py exists; re-clone if needed |
--limit flag not recognized | Old checkout | git pull origin main |
| Rust build fails | Toolchain not installed | Run `curl https://sh.rustup.rs -sSf \ |
---
Key Design Notes for AI Agents
- No external runtime dependencies for the core Python modules — safe to run in sandboxed environments.
- `query_engine.py` is the single aggregation point — prefer it over calling individual modules when you need a full picture.
- `models.py` dataclasses are the canonical data shapes; always import types from there, not inline dicts.
- `parity-audit` is read-only — it does not modify any tracked files.
- The project is not affiliated with Anthropic and contains no proprietary Claude Code source.
Related skills
FAQ
What is claw-code-harness used for?
claw-code-harness drives Claw Code CLI workflows—manifest inspection, parity auditing, command inventory, and subsystem listing—for a clean-room Python rewrite of the Claude Code agent harness with a Rust port in progress.
How do you invoke claw-code-harness?
claw-code-harness activates on triggers such as run parity audit claw-code and claw-code manifest summary, launching CLI tooling that inventories tools, commands, and port metadata without manual harness spelunking.
Is Claw Code Harness safe to install?
skills.sh reports 1 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.