opencode-goal-plugin

OpenCode goal plugin for Codex-style goal mode, /goal slash commands, persistent objectives, and AI coding agent focus.

Runssource: GitHubhomepageTypeScriptMITcommit e7c356091e25

TypeScript, MIT licensed. The project labels itself: agent, ai agent, coding agent, developer tools, goal, goal mode, npm package and opencode.

opencode-goal-plugin runs. An Argusic agent installed it in 0.3 minutes and hit no errors on a clean machine with no GPU, and the whole session was recorded.

The repo installs cleanly from source: all dependencies resolve, TypeScript typechecks without errors, ESLint reports no violations, the full test suite (296 tests) passes, the server bundles to dist/server.js (206.6 KB), and npm pack --dry-run confirms the correct publish artifact (6 files, 284.4 KB unpacked).

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 60 of 100 (the mean of this project's run scores).

At a glance

verdict
Runs
Argusic Score
60 / 100
cost of the verifying run
$0.01 (measured)
recorded runs
2
last tested
stars
533
forks
42
open issues
2
watchers
1
size
1 MB
created
last push

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
under a minute
Cold machine to finish
2 minutes
Errors hit and fixed
0 hit, 0 fixed with no human help
How the result was proved
bun run test exited 0, 296 passed across 9 files, 1228 expect() calls, 0 fail
Model tokens used
46,170
Exact commit tested
e7c356091e25
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

Watch the session

The whole run, from a clean machine, at the speed it actually happened. Nothing is cut and nothing is sped up.

A recording of attempt 2, run , the attempt that decided the verdict above. The terminal recording it was made from is the evidence, stored with a sha256 fingerprint; the video is a rendering of it. Nothing loads from the video host until you press play.

The end of the recording

The last lines of the terminal session that decided this verdict, exactly as they were recorded.

npm notice filename:      prevalentware-opencode-goal-plugin-0.1.1.tgz
npm notice package size:  63.0 kB
npm notice unpacked size: 284.4 kB
npm notice shasum:        81dc9038e727132cc60e7ea7f8eaa3da1914e16c
npm notice integrity:     sha512-fmc2QCbXGu3kA[...]vPNNTsW/P8rNQ==
npm notice total files:   6
npm notice
prevalentware-opencode-goal-plugin-0.1.1.tgz
Everything passed cleanly from a fresh install. Here's the full accounting.
tokens used
46,170
Everything passed cleanly from a fresh install. Here's the full accounting.

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 0.3 minutes, faster than the median of the 140 comparable projects Argusic has measured.
  • Nothing broke on the way: zero errors between clone and running.
  • Ran without a GPU, so it does not need one to start.
  • Licensed MIT, as reported by its host.
  • Measured 2 times, so the result is not a one-off.

Of the 141 agent projects Argusic has installed and timed, opencode-goal-plugin was the 9th fastest to reach a running state, and 94 of 141 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 0.3 minutes after the clone.
  • Following its own README: the documented path worked with nothing to fix.

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

tested byattemptoutcomescorecost USDwhen
Argusic Runner2/3Runs100.000.01
Argusic Runner1/3Did not run20.000.03

Topics (from GitHub)

agentai-agentcoding-agentdeveloper-toolsgoalgoal-modenpm-packageopencodeopencode-pluginslash-commandtui

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/opencode-goal-plugin.svg)](https://argusic.com/subject/opencode-goal-plugin)

Questions

Does opencode-goal-plugin run?
Yes. opencode-goal-plugin runs. Argusic installed and launched it on a clean machine in 0 minutes, hitting 0 errors on the way, and recorded the session.
How did Argusic test opencode-goal-plugin?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit e7c356091e25. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test opencode-goal-plugin?
The run that produced this verdict cost $0.01: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does opencode-goal-plugin take to install?
0.3 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 opencode-goal-plugin need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing opencode-goal-plugin?
Nothing did, in the recorded run: zero errors between clone and running.
How does opencode-goal-plugin compare with the alternatives?
Of the 141 agent projects Argusic has installed and timed, opencode-goal-plugin was the 9th fastest to reach a running state, and 94 of 141 reached one at all.
Where is the evidence for opencode-goal-plugin?
All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

Discussion