claude-for-legal
A suite of plugins for legal workflows
Runssource: GitHubPythonApache-2.0commit 4a6c651889c9
Python, Apache-2.0 licensed.
claude-for-legal runs. An Argusic agent installed it in 8 minutes and hit no errors on a clean machine with no GPU, and the whole session was recorded.
The claude-for-legal repository validates cleanly: marketplace schema passes, all 13 plugin manifests pass, all 5 managed-agent cookbooks pass tool-scope lint and body structure checks, and all 151+ JSON and YAML files parse correctly.
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 100 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.
- Install time
- 8 minutes
- Cold machine to finish
- 6 minutes
- Errors hit and fixed
- 0 hit, 0 fixed with no human help
- How the result was proved
- claude plugin validate .claude-plugin/marketplace.json passed; claude plugin validate on all 13 plugin dirs passed (expected warnings about root-level CLAUDE.md); python3 scripts/lint-tool-scope.py exited 0 (5/5 orchestrators clean); bash scripts/test-cookbooks.sh exited 0 (5 cookbooks tool-scope clean, 22 total agent bodies validated with non-empty system prompts and proper depth); python3 -c 'json.load/open all JSON' and 'yaml.safe_load/open all YAML' passed without errors
- Model tokens used
- 241,456
- Exact commit tested
- 4a6c651889c9
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
renewal-watcher: OK === Scripts === validate.py: loads OK (requires jsonschema) lint-tool-scope.py: runs OK test-cookbooks.sh: runs OK orchestrate.py: imports OK (requires ANTHROPIC_API_KEY to execute) === SKILL.md === 151 This repo is a collection of Claude Code plugin definitions, skills, prompts, and managed-agent coo… tokens used 241,456 This repo is a collection of Claude Code plugin definitions, skills, prompts, and managed-agent coo…
Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Reached a running state on a clean machine, with the session recorded.
- Nothing broke on the way: zero errors between clone and running.
- Ran without a GPU, so it does not need one to start.
- Licensed Apache-2.0, as reported by its host.
What did not, or is not known
- Took 8 minutes to install, slower than the median of the 12 comparable projects Argusic has measured.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 13 Python projects Argusic has installed and timed, claude-for-legal was the 8th fastest to reach a running state, and 8 of 13 reached one at all.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
- A quick evaluation: it was running 8 minutes after the clone.
- Following its own README: the documented path worked with nothing to fix.
Run history
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/claude-for-legal)Questions
- Does claude-for-legal run?
- Yes. claude-for-legal runs. Argusic installed and launched it on a clean machine in 8 minutes, hitting 0 errors on the way, and recorded the session.
- How did Argusic test claude-for-legal?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 4a6c651889c9. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test claude-for-legal?
- The run that produced this verdict cost $0.03: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does claude-for-legal take to install?
- 8 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does claude-for-legal need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing claude-for-legal?
- Nothing did, in the recorded run: zero errors between clone and running.
- How does claude-for-legal compare with the alternatives?
- Of the 13 Python projects Argusic has installed and timed, claude-for-legal was the 8th fastest to reach a running state, and 8 of 13 reached one at all.
- Where is the evidence for claude-for-legal?
- The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.