Runs OpenAI's Codex coding agent locally on your computer from the command line.
Cursor July
cursor · Agent
BDK is a way to write bots and agents as a versioned project of Markdown and TypeScript, with Cursor's models, tool calling, skills, MCP and subagents running the loop. You can add evals and unit tests, start from templates such as a security pull request reviewer or an issue triager for Linear or Jira, and trigger a project from Slack, webhooks or schedules. It needs Node and runs on Cursor-managed hosting or your own infrastructure.
Written by ooruby from the README of @cursor/july 0.2.23.
Not claimed by its maker. Is this yours? Prove it and answer the findings
Why it's useful
Agent instructions, tools and tests are versioned with your code, so your team can review and test them like any other change.
What you could do with it
- Start from the security reviewer template to review pull requests for exploitable bugs.
- Trigger an agent from a Slack thread, a webhook or a schedule while its instructions stay in your repository.
- Write evals and unit tests in plain TypeScript to check a bot before you deploy it.
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
Build, test, and deploy BDK bots and agents as code on Cursor's agent harness.
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.2.23, the file with digest sha512-eTNiMFKW9zq1JGsL7GjASm3R44aiYgFxnOjMBgZ7TQRRzmqiXN8+Pv/TSGV/yqWVgNftQqEshiQDjb7lU27bHg==, 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 -p @cursor/july@0.2.23 bdkPinned to 0.2.23, 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
- @cursor/july
- Version read
- 0.2.23
- Resolved
- 2026-10-10
No build provenance published. The repository above is the one the publisher declared, and nothing links it to the package you would install. That is not a mark against this listing, since most packages are published this way, but it is a check nobody can run.
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/cursor-july)About this listing
- Kind
- Agent
- Category
- Developer tools
- Pricing
- Free
- Sandbox
- No
- Hosted
- No
- Updated
- 2026-10-09
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.