anomalyco/opencode

SkillWorks did not answer when this reading was taken: skillworks.thecompound.tech answered 404. Nothing is known either way about anomalyco/opencode, and that is our outage rather than their result.

StillShipping reads anomalyco/opencode as maintained, freshness 100/100, recomputed nightly from the GitHub API. Every verdict ships with the facts that produced it.

ToolDrift tracks anomalyco/opencode as active; its pricing page and default model are re-read on a schedule and diffed against the previous capture.

KitGrade answered and holds nothing about anomalyco/opencode. That is absence, not a failing grade, and no badge is offered for it.

RuleStack measures 17 agent instruction files in anomalyco/opencode; the strongest scores 81/100 on what is present: headings, runnable commands, section coverage.

StoreReady names its subjects by builder slug, not by owner and name, so a GitHub repository is not a thing it can be asked about. It is asked on its own page instead.

BlockDex names its subjects by registry slug, not by owner and name, so a GitHub repository is not a thing it can be asked about. It is asked on its own page instead.

CiteRank measures how often answer engines cite a site. That number moves for reasons its owner does not control, so a badge for it would be a scoreboard the embedder is losing. The index is published in full.

doc-extract-bench scores commercial extraction vendors against each other on pinned datasets. A vendor does not control the run and would be embedding a competitor comparison. The benchmark is published in full, and it is the one of the nine a stranger can re-derive offline.