princejain756/agent-trials is a tool for validating coding agents before deployment. According to the repository description, it runs the same task suite identically across multiple agent CLIs and scores them in isolated environments. The commit d65976ef of October 26, 2026 added the CI workflow, the release workflow, and the README badges all at once. The commit message is 'Add CI, release workflow, and README badges', and the change touches 3 files with 42 insertions and 0 deletions.
The added .github/workflows/ci.yml runs npm install and npm test on ubuntu-latest for every push to the main branch and every pull request. The Node version matrix is 18, 20, and 22, and because fail-fast: false is set, the remaining axes keep running even if one version fails. .github/workflows/release.yml runs gh release create --generate-notes --verify-tag with contents: write permission and GITHUB_TOKEN on pushes of v*-style tags, creating a GitHub release and automatically generated release notes. At the top of README.md, an npm version badge, a CI status badge, and an MIT license badge were attached.
However, no npm publishing step is visible in this commit. An npm version badge pointing to npmjs.com/package/agent-trials was added, but the added release workflow contains only the GitHub release creation, so whether the package is actually published or updated cannot be determined from this change alone. As for the license, it is indicated by the MIT badge, and the body of the LICENSE file was not included in this commit. There are no figures for the scoring criteria or pass conditions in the publicly available change, so it is still premature to judge what level this tool treats as passing. If it is to be used as a formal procedure for comparing agent CLIs by swapping between them, it seems worth watching whether the CI and v* tag releases actually repeat.