packmind
Packmind seamlessly captures your engineering playbook and turns it into AI context, guardrails, and governance.
Runssource: GitHubhomepageTypeScriptApache-2.0commit ded906d14859
TypeScript, Apache-2.0 licensed. The project labels itself: ai code governance, ai coding assistant, ai guardrails, claude code, context engineering, contextops, copilot and cursor.
packmind runs. An Argusic agent installed it in 11 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
pnpm install completed, tsconfig.base.effective.json generated, all 22 backend-test projects pass (694 suites, 15067 tests), frontend passes (165 suites, 2532 tests), packmind-cli builds and runs (version 0.36.1-next), eslint lint passes on all checked projects.
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.

What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- CLI dist binary failed with 'Cannot find module minimatch'3 minutes
- Node v18 detected but project requires >=24.13.0. pnpm not found.2 minutes
- Missing tsconfig.base.effective.json referenced by all tsconfig files1 minute
- Install time
- 11 minutes
- Cold machine to finish
- 10 minutes
- Errors hit and fixed
- 3 hit, 3 fixed with no human help
- How the result was proved
- nx test on 22 projects (types, logger, node-utils, git, standards, eslint-rules, feature-flags, test-utils, ui, llm, commands, skills, spaces, accounts, coding-agent, linter-execution, linter-ast, migrations, deployments, playbook-change-applier, packmind-cli, api, packmind-plugin) and frontend (vitest) all exited 0, 694 suites, 15067 tests passed. CLI binary answered 'packmind --help' showing all subcommands and 'packmind --version' returned '0.36.1-next'.
- Model tokens used
- 250,427
- Exact commit tested
- ded906d14859
- 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.
succeeded in 0ms: START_TIME=1792880040 1792880730 Minutes elapsed: 11 exec /bin/sh -lc 'echo "START_EPOCH=$(date -d '"'2026-10-24T22:14:00Z' +%s 2>/dev/null || echo 'unknown'… succeeded in 0ms: START_EPOCH=1792880040 Let me compile the final structured report. tokens used 250,427 Let me compile the final structured report.
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.
- Installed in 11 minutes.
- Recovered from all 3 errors without a human stepping in, which says the failures are documented well enough to solve.
- 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
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
Topics (from GitHub)
ai-code-governanceai-coding-assistantai-guardrailsclaude-codecontext-engineeringcontextopscopilotcursor
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/packmind)Questions
- Does packmind run?
- Yes. packmind runs. Argusic installed and launched it on a clean machine in 11 minutes, hitting 3 errors on the way, and recorded the session.
- How did Argusic test packmind?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit ded906d14859. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test packmind?
- The run that produced this verdict cost $0.04: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does packmind take to install?
- 11 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 packmind need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing packmind?
- 3 things broke in the recorded run, and 3 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for packmind?
- 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.