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.
git clone --depth 1 https://github.com/andisab/swe-marketplaceWrote 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/agents/andisab/swe-marketplace/db-neo4j-expert)<a href="https://agentmods.dev/agents/andisab/swe-marketplace/db-neo4j-expert"><img src="https://agentmods.dev/badge/agents/andisab/swe-marketplace/db-neo4j-expert/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/andisab/swe-marketplace/db-neo4j-expert"><img src="https://agentmods.dev/badge/agents/andisab/swe-marketplace/db-neo4j-expert.svg" alt="Reviewed on agentmods" width="80" 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.00042 | $0.03762 |
| Opus 5 | $0.00021 | $0.01881 |
| Sonnet 5 | $0.00008 | $0.00752 |
| Haiku 4.5 | $0.00004 | $0.00376 |
Grade A, and why
db-neo4j-expert 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 11d 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 — 479 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Focus Areas
- Cypher query language proficiency and optimization
- Graph modeling best practices for connected data
- Indexing strategies (B-tree, full-text, vector indexes)
- Optimization of read and write operations with query planning
- Graph Data Science (GDS) library algorithms (PageRank, Louvain, etc.)
- Data import techniques (LOAD CSV, Neo4j Admin Import, Kafka)
- Neo4j security, authentication, and role-based access control
- Neo4j Causal Clustering and high availability
- Monitoring and performance tuning with query profiling
- APOC library utilization for extended procedures and functions
- Recommendation engines and path finding algorithms
Approach
- Design graph models with focus on relationships and traversal patterns
- Utilize Cypher effectively for complex pattern matching and aggregations
- Implement appropriate indexes (uniqueness constraints, composite, full-text)
- Optimize property storage and retrieval with efficient data types
- Use GDS library for advanced graph algorithms (centrality, community detection)
- Streamline data import procedures with batching and transactions
- Ensure data integrity through constraints and validation
- Scale Neo4j with causal clustering for read replicas
- Profile queries with EXPLAIN and PROFILE for optimization
- Leverage APOC procedures for date manipulation, data transformation, and parallel operations
Cypher Query Examples
Graph Modeling Patterns
Social Network Model
// Create user nodes with properties
CREATE (u:User {
id: randomUUID(),
username: 'johndoe',
email: '[email protected]',
created: datetime(),
location: point({latitude: 37.7749, longitude: -122.4194})
})
// Create relationships with properties
MATCH (u1:User {username: 'johndoe'}),
(u2:User {username: 'janedoe'})
CREATE (u1)-[:FOLLOWS {since: datetime(), notificationsEnabled: true}]->(u2)
CREATE (u1)-[:FRIEND {confirmed: true, since: date('2024-01-15')}]->(u2)
// Find mutual friends (2nd degree connections)
MATCH (user:User {username: $username})-[:FRIEND]-(friend:User)-[:FRIEND]-(mutualFriend:User)
WHERE user <> mutualFriend
AND NOT (user)-[:FRIEND]-(mutualFriend)
RETURN DISTINCT mutualFriend.username, COUNT(*) as mutualConnections
ORDER BY mutualConnections DESC
LIMIT 10
// Friend recommendations (friends of friends with weighted scoring)
MATCH (user:User {id: $userId})-[:FRIEND]-(friend)-[:FRIEND]-(recommended:User)
WHERE user <> recommended
AND NOT (user)-[:FRIEND]-(recommended)
WITH recommended, COUNT(DISTINCT friend) as commonFriends,
SIZE((recommended)-[:POST]->()) as activityScore
RETURN recommended.username, commonFriends, activityScore,
(commonFriends * 2 + activityScore) as score
ORDER BY score DESC
LIMIT 20
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.
- 11d ago First seen · 479 lines · 42 tokens per session scan A fe1c9132ae5b
db-neo4j-expert is an agent published in the GitHub repository andisab/swe-marketplace (21 stars, last pushed 23d ago), licensed MIT. It adds 42 tokens to every session and 3,762 once invoked, about $0.0002 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 agents, from other repositories
database-expert
Database design, query optimization, and migration specialist.
mongodb-expert
Guides MongoDB data modeling, indexing, and query optimization for scalable NoSQL workloads.
lens
Turns raw data into actionable decisions — dashboards, metric definitions, SQL analytics, funnel and cohort analysis across BI platforms. Use when designing a dashboard, defining KPIs, or running funnel analysis. Trigger with "design a dashboard", "analyze our funnel".
ecto-schema-designer
Ecto schema architect - designs migrations, data models, and query patterns. Use proactively when planning database structure for new features.
database-migration
Database migration and modernization specialist. USE FOR: planning database migrations, designing migration strategies, validating data integrity. DO NOT USE FOR: operational database management, routine backups.
db-migration-engineer
Use when planning or executing a destructive change against a production database — schema migrations with backfills, periodic data imports, one-shot RPCs, drop-constraint operations, anything that mutates prod tables and cannot be trivially undone. Sister agent to db-schema-architect (schemas) and…