Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add instructions/neo4jrb/neo4j-ruby-driver/claude-mdgit clone --depth 1 https://github.com/neo4jrb/neo4j-ruby-driverWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/instructions/neo4jrb/neo4j-ruby-driver/claude-md)<a href="https://agentmods.dev/instructions/neo4jrb/neo4j-ruby-driver/claude-md"><img src="https://agentmods.dev/badge/instructions/neo4jrb/neo4j-ruby-driver/claude-md.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.01518 | $0.01518 |
| Opus 5 | $0.00759 | $0.00759 |
| Sonnet 5 | $0.00304 | $0.00304 |
| Haiku 4.5 | $0.00152 | $0.00152 |
Grade A, and why
neo4j-ruby-driver CLAUDE.md scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 6d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Neo4j Ruby Driver
Branches
main is the active development branch — base feature branches on it and
target PRs at it. 4.4 is a diverged, older release line (it predates the
JRuby/shared split and the auth-manager work); don't branch off it.
Essential References
Specifications
- Bolt Protocol: https://neo4j.com/docs/bolt/current/
- PackStream: https://neo4j.com/docs/bolt/current/packstream/
Official Drivers (for comparison)
- Java (reference impl): https://github.com/neo4j/neo4j-java-driver and https://github.com/neo4j/bolt-connection-java
- Python: https://github.com/neo4j/neo4j-python-driver
- JavaScript: https://github.com/neo4j/neo4j-javascript-driver
- Go: https://github.com/neo4j/neo4j-go-driver
When in doubt, check the Java driver - it's the most comprehensive reference implementation.
Two implementations behind one public API: the MRI impl is a pure-Ruby implementation of the Neo4j Bolt protocol (no Java dependency); the JRuby impl wraps the official Java driver. When in doubt about driver semantics, the Java driver is the reference: https://github.com/neo4j/neo4j-java-driver
See DEVELOPMENT.md for dev-loop commands and DECISIONS.md for the
dated log of architectural choices.
Layout
Dev tree is split into lib/{shared,mri,jruby}/. The published gem is
flattened to lib/ via a staged build (Pattern 1 — see JRUBY.md).
lib/shared/neo4j/driver.rb Gem entry (Zeitwerk setup; pushes shared + impl roots)
lib/mri/neo4j/driver/ MRI implementation
bolt/ Bolt protocol: connection, messages
packstream/ Binary serialization: packer/unpacker
types/ Neo4j types (Node, Relationship, Path, temporal, Point, Duration)
exceptions/ Exception hierarchy, one class per file
session.rb Session + auto-commit
transaction.rb Explicit transactions
result.rb Streaming result
record.rb / summary.rb
lib/jruby/neo4j/driver/ JRuby implementation: thin wrapper over the
Java driver (org.neo4j.driver jars). `ext/`
mixins are prepended onto the Java classes
for Ruby<->Java type/exception conversion.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 6d ago First seen · 102 lines · 1,518 tokens per session scan A 27cb9ee3d9ad
neo4j-ruby-driver CLAUDE.md is an instructions file published in the GitHub repository neo4jrb/neo4j-ruby-driver (51 stars, last pushed 2d ago), licensed MIT. It adds 1,518 tokens to every session, about $0.0076 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other instructions, from other repositories
turso AGENTS.md
AGENTS.md instructions for tursodatabase/turso, covering turso agent guidelines, quick reference, testing, running tests and test organization.
questdb CLAUDE.md
Claude Code instructions for questdb/questdb, covering claude.md, project overview, coding guidelines, tests and questdb's sql dialect.
mikro-orm copilot-instructions.md
Copilot instructions for mikro-orm/mikro-orm, covering mikroorm typescript orm development instructions, working effectively, environment setup, building and testing and environment reset (when pulling master).
prest copilot-instructions.md
Copilot instructions for prest/prest, covering copilot instructions for prest go backend, project scope, core engineering principles, solid principles for go and s — single responsibility.
redis-vl-python CLAUDE.md
Claude Code instructions for redis/redis-vl-python, covering claude.md - redisvl project context, frequently used commands, development workflow, redis setup and documentation.
ruby2d AGENTS.md
Instructions for ruby2d/ruby2d, covering ruby 2d guide for ai coding agents, testing, architecture, multi-ruby support and documentation.