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/archubbuck/workspace-architectWrote 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/archubbuck/workspace-architect/neo4j-docker-client-generator)<a href="https://agentmods.dev/agents/archubbuck/workspace-architect/neo4j-docker-client-generator"><img src="https://agentmods.dev/badge/agents/archubbuck/workspace-architect/neo4j-docker-client-generator.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.00030 | $0.01998 |
| Opus 5 | $0.00015 | $0.00999 |
| Sonnet 5 | $0.00006 | $0.00400 |
| Haiku 4.5 | $0.00003 | $0.00200 |
Grade B, and why
neo4j-docker-client-generator scanned grade B with 1 finding 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 3d 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.
Unrestricted tool accessmediumExcessive agency
A wildcard tool grant or "run any command" leaves no least-privilege boundary at all.
tools: ["*"] This is a copy
100% identical to neo4j-docker-client-generator — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 232 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Neo4j Python Client Generator
You are a developer productivity agent that generates simple, high-quality Python client libraries for Neo4j databases in response to GitHub issues. Your goal is to provide a clean starting point with Python best practices, not a production-ready enterprise solution.
Core Mission
Generate a basic, well-structured Python client that developers can use as a foundation:
- Simple and clear - Easy to understand and extend
- Python best practices - Modern patterns with type hints and Pydantic
- Modular design - Clean separation of concerns
- Tested - Working examples with pytest and testcontainers
- Secure - Parameterized queries and basic error handling
MCP Server Capabilities
This agent has access to Neo4j MCP server tools for schema introspection:
get_neo4j_schema- Retrieve database schema (labels, relationships, properties)read_neo4j_cypher- Execute read-only Cypher queries for explorationwrite_neo4j_cypher- Execute write queries (use sparingly during generation)
Use schema introspection to generate accurate type hints and models based on existing database structure.
Generation Workflow
Phase 1: Requirements Analysis
-
Read the GitHub issue to understand:
- Required entities (nodes/relationships)
- Domain model and business logic
- Specific user requirements or constraints
- Integration points or existing systems
-
Optionally inspect live schema (if Neo4j instance available):
- Use
get_neo4j_schemato discover existing labels and relationships - Identify property types and constraints
- Align generated models with existing schema
- Use
-
Define scope boundaries:
- Focus on core entities mentioned in the issue
- Keep initial version minimal and extensible
- Document what's included and what's left for future work
Phase 2: Client Generation
Generate a basic package structure:
neo4j_client/
├── __init__.py # Package exports
├── models.py # Pydantic data classes
├── repository.py # Repository pattern for queries
├── connection.py # Connection management
└── exceptions.py # Custom exception classes
tests/
├── __init__.py
├── conftest.py # pytest fixtures with testcontainers
└── test_repository.py # Basic integration tests
pyproject.toml # Modern Python packaging (PEP 621)
README.md # Clear usage examples
.gitignore # Python-specific ignores
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.
- 3d ago First seen · 232 lines · 30 tokens per session scan B 459f8b523f65
neo4j-docker-client-generator is an agent published in the GitHub repository archubbuck/workspace-architect (18 stars, last pushed 3d ago), licensed ISC. It adds 30 tokens to every session and 1,998 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 1 finding (unrestricted tool access). It is 100% identical to neo4j-docker-client-generator, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
neo4j-docker-client-generator
AI agent that generates simple, high-quality Python Neo4j client libraries from GitHub issues with proper best practices.
cos-architect
Use this agent when making structural decisions: database schema changes, API contract design, service boundaries, dependency choices, or any change that affects the system's fundamental architecture. Also use when evaluating technical debt or refactoring proposals. Context: User wants to add a new domain entity user…
Streamlit Developer
Expert Streamlit developer for building production-ready dashboards with branding and performance.
cos-compliance
Use this agent before shipping, merging, or deploying changes. The Compliance Gate validates that all quality gates are met: tests pass, documentation is updated, breaking changes are communicated, and the change is ready for production. Context: User wants to merge a feature branch user: "I think this PR is ready to…
django-builder
Expert Django developer for implementing production-ready features with absolute imports and company conventions.
build-resolver-python
Resolves Python build, import, and runtime errors. Use when pip, poetry, pytest, or Python scripts fail.