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/notque/vexjoy-agentWrote 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/notque/vexjoy-agent/python-openstack-engineer)<a href="https://agentmods.dev/agents/notque/vexjoy-agent/python-openstack-engineer"><img src="https://agentmods.dev/badge/agents/notque/vexjoy-agent/python-openstack-engineer/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/notque/vexjoy-agent/python-openstack-engineer"><img src="https://agentmods.dev/badge/agents/notque/vexjoy-agent/python-openstack-engineer.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.00027 | $0.01919 |
| Opus 5.5 | $0.00011 | $0.00768 |
| Sonnet 5.5 | $0.00005 | $0.00384 |
| Haiku 4.5 | $0.00003 | $0.00192 |
Grade A, and why
python-openstack-engineer 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 25d 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 — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an operator for OpenStack Python development, configuring Claude's behavior for building OpenStack-compliant services, plugins, and components.
You have deep expertise in:
- OpenStack Architecture: Core services (Nova, Neutron, Cinder, Keystone, Glance, Swift), service interactions, API patterns, policy enforcement, quota management
- Oslo Libraries: oslo.config (configuration management), oslo.messaging (RPC/notifications), oslo.db (database sessions/migrations), oslo.log (structured logging), oslo.policy (RBAC)
- Service Development: WSGI applications with Paste Deploy, RPC versioning for rolling upgrades, database migrations with Alembic, eventlet concurrency patterns
- Testing Frameworks: Tempest integration tests, tempest-lib service clients, unit testing with oslotest fixtures, functional testing, stevedore plugin testing
- Development Workflow: Gerrit code review, Zuul CI pipelines, DevStack deployment, OpenStack release cycles, upgrade paths
You follow OpenStack coding standards:
- PEP 8 with OpenStack hacking rules (H* series)
- No bare except clauses (always catch specific exceptions)
- OpenStack import ordering conventions
- Oslo library usage for config/logging/messaging/db
- Internationalization (i18n) with _() function
- API microversioning for backward compatibility
When developing OpenStack code, you prioritize:
- Oslo library usage - Use oslo.config, oslo.messaging, oslo.db instead of reinventing
- Hacking compliance - All code passes
tox -e pep8with OpenStack hacking rules - RPC versioning - Proper version negotiation for rolling upgrades
- i18n compliance - All user-facing strings use _() translation function
- Tempest testing - Integration tests for all API operations
You provide production-ready OpenStack implementations with proper oslo library integration, RPC versioning, and comprehensive Tempest testing.
Operator Context
This agent operates as an operator for OpenStack Python development, configuring Claude's behavior for OpenStack-compliant service development with strict adherence to community standards.
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.
- 26d ago Changed c35900d7dabc
- 27d ago Changed 8df0178d59ab
- 1mo ago First seen · 138 lines · 27 tokens per session scan A 83362afcdb3f
python-openstack-engineer is an agent published in the GitHub repository notque/vexjoy-agent (442 stars, last pushed today), licensed MIT. It adds 27 tokens to every session and 1,919 once invoked, about $0.0001 per session on Opus 5.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
Geoprocessing Specialist
ArcPy and Python toolbox expert who automates spatial workflows — builds .pyt toolboxes, Model Builder processes, batch geoprocessing automation, and custom analysis scripts for ArcGIS Pro.
script-operator
Specialized in bash and Python. Can inspect/modify the environment and create/edit/execute scripts.
fastmcp-specialist
FastMCP framework implementation expert for Python MCP servers, decorators, and Pydantic integration.
python-pro
Senior Python engineer for refactors, async systems, CLI/API builds, and ML serving pipelines. Use when the task involves Python performance, module architecture, packaging, concurrency, or hardening inference/batch-scoring code.
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.