WAYS OF WORKING · DEMO 12 NINO CHAVEZ
A coding-agent plugin with sixty-six thousand stars keeps arriving in my inbox as a link. Answering "should I adopt this" turned out to be an evidence problem, not a feature problem — and once the sources were sorted by who published them, almost nothing was left standing on its own.
"read through and research "oh my opencode" to understand its use case and how it compares to what i'm already doindg and if using it or adopting it is useful in my agentic ways of working." operator message, verbatim — one prompt, four links, no other context
→ or scroll to advance · ← to go back
02 BEFORE THE FEATURES
Two of the four links pointed at repositories with the same name. Both had a polished page, the same hero image, the same testimonial wall. One of them was a fork whose last commit was six months old.
What the pages looked like
Identical. Same README, same feature table, same reviews section. Nothing rendered on either page announced that one was a copy that had stopped moving in January.
What one command said
951 stars, last pushed 2026-01-25, fork of the other one. The live project had 66,836 stars, a different name after a rename, and had been pushed to that same morning.
Identity first. A stale fork reads exactly like the original.
Twenty seconds of repository metadata separated a live project from an abandoned copy of it. That check ran before I read a single feature claim, and it is the cheapest one in this entire demo.
03 THE LEDGER
Every claim I had been handed, with one column added: who owns the page it appeared on. The sort takes minutes. Skipping it is what costs you.
54 lifecycle hooks, 11 named agents, a parallel team mode
The project's own feature table
"Cancelled my Cursor subscription." "You will never go back."
Quotes the maintainer selected and pasted into a file he controls
A video review showing token burn, erratic behavior, and a config the plugin deleted unprompted
A third party — listed approvingly in the project's own reviews section
66,836 stars
Counted by the host, displayed on the project's page. Unaudited, gameable, and a measure of interest rather than fit — but nobody wrote it
Users arguing about whether it actually helps
A forum thread. Nobody curating it. The only genuinely independent source in the pile
The most useful item in the pile is the critical review, because it is the only one that shows the tool failing. It is also quoted approvingly a few lines above a link to the project's chat server. A critical review the vendor chose to feature is still evidence — it just survived a filter someone else set.
04 THE HONEST FAILURE
A forum thread asking, in plain words, whether this thing really provides an advantage. Six attempts across five different routes. Every one refused.
Summarizing a discussion I never read would have produced the most quotable section in the writeup and the only invented one. The thread got written down as unreachable, and the pile carried a known hole through to the end. the disposition — demo 07's rule, applied to a source instead of a claim
The gap matters more than the missing quotes. After it, everything still standing had been published by a party with something at stake in my answer.
05 WHAT DECIDED IT
The plugin's strongest edition runs on a different coding agent than mine. My subscription is with the model vendor. So the whole question reduced to one thing: can those two be connected?
The plugin's own answer
Honest, and I respect it: technically possible, but I cannot recommend it. Still a sentence on the project's own page, in a document written to persuade.
The answer that settled it
The host agent's documentation offers a subscription login option and then says, about its own feature, that the model vendor explicitly prohibits this — noting the components enabling it were removed in a later release.
Adverse interest. Nobody writes that for marketing.
Secondary reporting fills in a timeline across four months — token rejection, updated terms, legal demands, a final cutoff. I read several accounts and could not confirm the specific clause on the vendor's own terms page, which carries only a generic line about not sharing credentials. That timeline stays labeled as reporting. The verified part was enough: the flagship edition means paying for other subscriptions and setting mine aside — a price that appears on no page I was handed.
06 TRUSTING NOBODY
Both were cheap for one reason worth naming: my own setup is already written down, in public, for unrelated reasons. Lining the plugin's inventory up against mine was reading, not excavation.
The inventory diff
Most of the 54 hooks had a counterpart already running: idle-agent recovery, duplicate-read prevention, rules injection, language-server navigation, documentation lookup, structured search, an interviewing planner.
Covered · absent · blocked. Three buckets, not two.
The reverse direction
One item ran the other way. A guard that refuses to let two sessions commit from the same working directory — enforced as a denied tool call, not offered as an optional flag. The plugin has no equivalent.
The collision check
The lighter edition installs command-line tools into a shared directory and writes blocks into a config file I have been editing for months. Every name it adds is prefixed; every block is a new named section. Nothing collided.
But: it sets a ceiling of 1,000 parallel threads per session.
Two things were genuinely absent. A hash-anchored edit tool that rejects a stale edit instead of corrupting the file — a real idea, with one weak model reported going from 6.7% to 68.3% success on that change alone, and one I cannot act on because I cannot patch my agent's editor. And structural code search, which turned out to be a separate open-source tool that installs in one command and requires adopting nothing. I took that one.
07 YOUR VERSION OF THIS
If a tool arrives as a link
Check identity before features — forks and renames are free and invisible. Then add one column to everything you have been handed: who owns the page. Expect most rows to come back owned by the vendor. That is what a product page is for; it is only a problem when you did not notice.
If you need one claim to decide
Go looking for a source that loses by publishing it. For agent tooling that is almost always the host platform's documentation, the license file rather than the badge, or the terms page itself. It outweighs the entire testimonial wall above it.
If you cannot reach a source
Write down that you could not, and carry the hole forward. The summary you would have invented is indistinguishable from the one you would have read, which is exactly why it is the most dangerous paragraph available to you.