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 agents/notque/vexjoy-agent/python-openstack-engineergit clone --depth 1 https://github.com/notque/vexjoy-agentWhat 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 | $0.00027 | $0.01932 |
| Opus 5 | $0.00014 | $0.00966 |
| Sonnet 5 | $0.00005 | $0.00386 |
| Haiku 4.5 | $0.00003 | $0.00193 |
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 yesterday.
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.
- yesterday 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 (417 stars, last pushed 2d ago), licensed MIT. It adds 27 tokens to every session and 1,932 once invoked, about $0.0001 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
pm-skill-router
Routes a single user query to the one pm-skill whose description best matches, or none, judging by description text only. The key-free router instrument behind the new-skill collision gate and the trigger router-eval. Explicit invocation only; dispatch pinned to Haiku.
plinth-architect
Java architecture specialist. Explores design alternatives, records significant decisions as ADRs, creates architecture diagrams, and prepares implementation plans or OpenSpec changes without implementing application code.
plinth-java-coder
Implementation specialist for Java projects. Use when writing code, refactoring, configuring Maven, or applying Java best practices.
performance-optimizer
Performance optimization expert. Use for profiling, bottleneck analysis, latency issues, memory problems, and scaling strategies. Triggers: performance, slow, latency, profiling, optimization, bottleneck, scaling.
product-manager
Product management and value maximization expert. Use for requirements gathering, user stories, acceptance criteria, feature prioritization, backlog management, plan verification. Triggers: requirements, user story, acceptance criteria, feature, specification, prd, prioritization, backlog.
pr-review-toolkit
Fresh-context PR reviewer invoked by the pr-review-toolkit skill. Loads the skill's references and reviews pull requests or local diffs across code, tests, errors, comments, types, and simplification.