Installs and manages skills for your AI coding agents from a browsable catalogue.
Harness Toolkit
tech-leads-club · Agent
Harness Toolkit steers Cursor and Claude Code agents through the editor's own hooks. Each hook event gets a decision: allow, ask, deny, or text injected into the turn, and a record of what was decided and why is written. Floor rules and always-on checks cannot be switched off, while optional rails are chosen one by one, and a project can carry its own rules. Commands cover status, a health check, lint and test follow-ups when the agent stops, pause and resume, and handoff state between turns and sessions.
Written by ooruby from the README of @tech-leads-club/harness-toolkit 0.16.2.
Not claimed by its maker. Is this yours? Prove it and answer the findings
Why it's useful
You decide which actions your coding agent may take and can trace each allow, ask or deny back to the rule behind it.
What you could do with it
- Give one repository its own rules by asking the agent to set up the harness there.
- Turn on lint and test follow-ups that run when the agent stops.
- Trace a message on your screen back to the rule that produced 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
- Command execution is bounded
- inventory
- node child_process (tools/doctor.ts:1)
- synchronous shell execution (tools/doctor.ts:76)
- node child_process (tools/install-runtime.ts:1)
- node child_process (src/platform/process.ts:1)
- 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
Multi-provider agent steering: gates, follow-up, handoff, policy
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.16.2, the file with digest sha512-rwZ58hjIE22kbTw+Jh6oYZhyb/NNGY0Bqc/FeeqcShnNLQ/WqVbDl/oBC+pOhFL2d3odjqEFpMfWN+cSAk+yuA==, 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 @tech-leads-club/harness-toolkit@0.16.2 tlcPinned to 0.16.2, 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
- @tech-leads-club/harness-toolkit
- Version read
- 0.16.2
- 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/tech-leads-club/harness-toolkit
- Commit
- 96cf87f27cf3
- 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/tech-leads-club-harness-toolkit)About this listing
- Kind
- Agent
- Category
- Developer tools
- Pricing
- Free
- Sandbox
- No
- Hosted
- No
- Updated
- 2026-10-03
More from tech-leads-club
See the storefrontSimilar 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.