Runs OpenAI's Codex coding agent locally on your computer from the command line.
Taste Lint
mblode · Agent
Taste Lint runs design and writing rules over a project on every commit. It checks motion, copy, typography and search metadata, and with the code profile also things like unbounded reads and tests that assert nothing. Judgement calls, such as vague errors or empty states with no action, go to a review step called Jev, which answers with a probability and needs a Vercel AI Gateway key. Profiles scope a run, and a rule pack can add your own voice.
Written by ooruby from the README of taste-lint 0.6.0.
Not claimed by its maker. Is this yours? Prove it and answer the findings
Why it's useful
Design, copy and typography slips are flagged at commit time, before they reach review or production.
What you could do with it
- Run the dry run to see the mechanical results and the cost of the review pass before it is billed.
- Add a pre-commit hook with lefthook, husky or lint-staged so commits are blocked on the mechanical checks.
- Run the writing profile over your Markdown docs to flag long chained sentences and stock phrases.
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
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
Taste linter: copy and typography rules from agent-skills answered by TypeSafe Jev probabilities, with mechanical checks, calibration and a scorecard
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.6.0, the file with digest sha512-4iEzDOmMoA3fEzJrDK9Lk8LNsBKlAh2te1PHhgsKovi+qwZDfcmA7VUWENuCaUJkccL5Fas3cgm7+nbLZbitJQ==, 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 taste-lint@0.6.0Pinned to 0.6.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
- taste-lint
- Version read
- 0.6.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/mblode/taste-lint
- Commit
- 86837329dfb9
- 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/taste-lint)About this listing
- Kind
- Agent
- Category
- Developer tools
- Pricing
- Free
- Sandbox
- No
- Hosted
- No
- Updated
- 2026-10-08
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.