[seanebones-lang]

What kind of change?

• New agent listings (content/agents/<slug>.json added)
• Correction to an existing entry
• Removal
• Code / site change

For new listings

Four vendor-submitted, independently categorized NextEleven tools with actual public release packages. This is a small curated batch, not a request for featured or verified placement. Please review each entry on its merits.

Product	Product URL	Installable release	Fit / status
DeadBolt	https://www.nexteleven.dev/deadbolt	https://github.com/seanebones-lang/deadbolt/releases/tag/v2.0.0	Stable local admission gate; CLI, local HTTP and stdio MCP
Harness by NextEleven	https://github.com/seanebones-lang/harness	https://github.com/seanebones-lang/harness/releases/tag/v1.4.0-beta.2	Developer-evaluation beta; Rust assistant, CLI and local HTTP/SSE
Repo Salvage	https://github.com/seanebones-lang/repo-salvage	https://github.com/seanebones-lang/repo-salvage/releases/tag/v0.2.1	Development prototype; packaged CLI/MCP adapter and local retrieval API
PersonalRAGVault	https://github.com/seanebones-lang/personal-RAG	https://github.com/seanebones-lang/personal-RAG/releases/tag/v1.5.1	Local Python document retrieval; wheel/source, CLI and local HTTP

Why they belong here: documented programmatic access, public source, pinned release downloads and an identifiable vendor. DeadBolt also has matching stable packages on crates.io and PyPI, and an MCPB release. Those are distribution signals, not claims of customer adoption. We do not claim funding, independent certification or general usefulness benchmarks. The beta/prototype status remains in the corresponding descriptions.

Relationship: submitted on behalf of Sean McDonnell / NextEleven, the maintainer and vendor, with AI assistance.

Integration boundaries

• DeadBolt gates connected routes before tool dispatch; it is not an OS sandbox, agent-wide interception or cancellation of in-flight actions. bearer describes its local HTTP role-separated credentials. The CLI and MCP configuration have their documented operator setup. No public remote operator endpoint is advertised. See integration boundaries.
• Harness is a prerelease for developer evaluation, not a verified general-production release. Its local HTTP API uses a bearer token. CLI model-provider credentials or a local backend are configured separately. mcp is intentionally not an access method here: consuming MCP integrations does not establish that Harness is an MCP server.
• Repo Salvage retrieval is public on a user-run instance; private contribution/analysis has separate authorization. There is no public hosted catalog or npm registry publication. The release contains actual CLI and MCP tarballs. Independent usefulness remains unproven.
• PersonalRAGVault is local first, not necessarily offline on first use: embedding models/dependencies download, and an explicitly chosen external generation endpoint receives retrieved context. Its local HTTP API has optional bearer authentication; none describes the default local retrieval setup. The wheel is available on GitHub, not promised on PyPI.

Documentation for reviewers

• Harness quickstart
• Repo Salvage quickstart
• PersonalRAGVault sample

Checklist

• npx tsx scripts/validate-content.ts passes locally (770 entries; zero violations)
• TypeScript typecheck passes
• Lint completes with zero errors (three warnings in unchanged upstream files)
• Production build passes (811 pages generated)
• Repository test suite passes (46 tests)
• Added four lines to content/changelog.json
• Provider/product URLs load (HTTP 200)
• Skills describe documented capabilities
• Vendor listings have verified: false and featured: false
• official left unset

No application code or homepage promotion changes. Publication remains subject to your review and merge.

Upstream GitHub CI currently reports action_required for this fork submission; its run requires maintainer approval. The Vercel preview requests project-owner authorization. These are pending upstream checks, not claimed passes; the local checks above all completed.

[vercel]

Someone is attempting to deploy a commit to the assafbar-gmailcom's projects Team on Vercel.

A member of the Team first needs to authorize it.

[greptile-apps]

Your trial has ended. Reactivate Greptile to resume code reviews.

[seanebones-lang]

Thank you for considering these four listings. The submission remains ready for maintainer review; I can adjust or split the entries if that makes the review easier.

The fork’s GitHub checks and Vercel preview are waiting for upstream maintainer authorization, as recorded in the PR. Could you approve those checks when reviewing the submission, or let us know if you need a different validation route? The local check receipts and product boundaries are in the PR description. We are not requesting featured/verified status or a paid review service.

Sean / NextEleven