Runs OpenAI's Codex coding agent locally on your computer from the command line.
Stdd CLI
stdd · Agent
Stdd is a markdown-first method for teams building software with AI coding agents: edit the docs first, then show a failing test, then write the code. It ships playbooks that become native skills in your agent, and a command line with gates that refuse claims no file backs, such as a pull request body that claims a docs change the diff lacks. You can adopt it as an agent plugin alone, as one command in the repository, or as checks in CI.
Written by ooruby from the README of @stdd/cli 0.11.0.
Not claimed by its maker. Is this yours? Prove it and answer the findings
Why it's useful
A chat log cannot show which docs a change rested on or that its test failed first, so stdd writes those facts to files and checks them.
What you could do with it
- Pipe a pull request description into the check command to catch a docs change it claims but the diff does not contain.
- Add the two check commands to a CI job to enforce the method on the checkout and the pull request description.
- Start with the investigation workflow for a read-only look at current facts before any change is made.
Written from its documentation: what it says it can do, not what our checks found.
Maintenance
Not measuredNo release date is on record for this package yet. The nightly publisher check records one as it reaches each npm package, about once every ten nights.
Release activity only: it says nothing about quality or safety, and a finished small package can be fine without releases. How it is measured
- Command execution is bounded
- inventory
- node child_process (sdk/native-fs.mjs:1)
- node child_process (cli/check.mjs:1)
- synchronous shell execution (cli/check.mjs:189)
- synchronous shell execution (cli/check.mjs:222)
- An inventory of where the code starts another program, not a verdict on this row: whether each one runs a fixed program or whatever it is handed takes a reading by hand.
Published because it was found. A finding is information about where the limits are, not a verdict that the software is unsafe.
What this does not cover
- Everything. Treat it as you would software from anywhere else.
Receipt history: every signed receipt for every version of this listing, and what changed between them.
In its maker's words
Spec + Test Driven Development — a markdown-first methodology kit for teams building software with AI coding agents
Compare with
Compare all 4How far this has been checked
Static scanned
- What it establishes
- Its published package, or for a hosted server its source repository at a recorded commit, was read file by file, without running it, by every check in our current scan.
- What it does not
- How it behaves when it runs, or anything the scan does not read yet: several rubric checks, the repository's history, and compiled code in folders named dist or build. For a hosted server, that the endpoint runs the code that was read. The ooruby Index sets out exactly what was read.
- Exactly what was read
- Version 0.11.0, the file with digest sha512-fMqA0Ygjsj/Q0WCstUhoEhvW4SDq4nEFRoSGPSff1dsjglTKuwBTPYiCMaJvTpc/TXtLIfjhwTos92MwVA6h8Q==, as the registry publishes it. A published version cannot be replaced, so this names the same bytes for anyone who checks.
- Authentication
- Runs locally. No hosted endpoint is listed for this package. You run it on your own machine, so there is no endpoint of ours to authenticate against.
Adding it
Run it with:
npx -y @stdd/cli@0.11.0Pinned to 0.11.0, which is the version the findings above were found in. Drop the version to take whatever is newest, and the report on this page stops describing what you installed.
Where this came from
- Registry
- npm
- Package
- @stdd/cli
- Version read
- 0.11.0
- Resolved
- 2026-10-10
Built from source, attested
npm publishes a signed statement that this exact package was built from the repository below, at this commit. It is verifiable without taking our word for it.
- Repository
- github.com/vsem-azamat/stdd
- Commit
- ba174bff0eff
- Built by
- github.com/actions/runner/github-hosted
- Registry publish attestation
- signed by npm · 2026-10-10
- Checked
- 2026-10-10
The badge, if this is your listing
It renders the current rung (static scanned) and links back here, where what that does and does not establish is one click away. It updates itself as the evidence deepens.
[](https://ooruby.com/market/stdd-cli)About this listing
- Kind
- Agent
- Category
- Developer tools
- Pricing
- Free
- Sandbox
- No
- Hosted
- No
- Updated
- 2026-10-04
Similar agents
All agentsVerification records what our published tests found on a specific version at a specific date. It is not a warranty, and it does not certify that software is free of defects.