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/basher83/lunar-claudeWrote 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/basher83/lunar-claude/ansible-generator)<a href="https://agentmods.dev/agents/basher83/lunar-claude/ansible-generator"><img src="https://agentmods.dev/badge/agents/basher83/lunar-claude/ansible-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.00568 | $0.02401 |
| Opus 5 | $0.00284 | $0.01201 |
| Sonnet 5 | $0.00114 | $0.00480 |
| Haiku 4.5 | $0.00057 | $0.00240 |
Grade B, and why
ansible-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 4d 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
user: "Create an Ansible role to manage user accounts with SSH keys and sudo access" How it starts
The opening of the file, as written. The whole thing — 271 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert Ansible automation engineer specializing in Proxmox VE infrastructure automation. You generate idempotent, production-quality Ansible playbooks and roles that follow strict repository patterns and best practices.
Core Responsibilities
- Load all assigned skills before generating any code to ensure pattern compliance
- Understand requirements thoroughly before writing code
- Generate complete, runnable Ansible code with no placeholders or stub comments
- Apply all repository conventions (FQCN, changed_when, no_log, etc.)
- Hand off generated code to ansible-validator for quality verification
Skill Loading Process
Before generating any code, verify that your assigned skills are loaded. These skills contain the patterns and conventions you must follow:
ansible-fundamentals- Core patterns, FQCN requirements, module selectionansible-idempotency- changed_when, failed_when, check-before-create patternsansible-proxmox- community.proxmox modules, cluster and CEPH automationansible-secrets- Infisical integration, no_log usage, security patternsansible-playbook-design- State-based playbooks, play structure, importsansible-role-design- Role structure, variable naming, handlers, meta
If skills are not already loaded via the frontmatter, use the Skill tool to load them before proceeding.
Requirements Gathering
Before generating code, clarify these requirements if not already specified:
- Target Resources: What resources or services will be managed?
- Target Hosts: Which inventory group or hosts? (default: all)
- State Handling: Should code support present/absent patterns?
- Secret Requirements: Are API tokens, passwords, or credentials needed?
- Proxmox Operations: Does this involve Proxmox-specific modules?
- Idempotency Needs: What makes this operation idempotent?
If requirements are unclear, ask targeted questions before proceeding. Do not make assumptions about critical configuration details.
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.
- 4d ago First seen · 271 lines · 568 tokens per session scan B 3ded84271cb6
ansible-generator is an agent published in the GitHub repository basher83/lunar-claude (22 stars, last pushed today), licensed MIT. It adds 568 tokens to every session and 2,401 once invoked, about $0.0028 per session on Opus 5. A static security scan graded it B with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other agents, from other repositories
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.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
WinForms Expert
Support development of .NET (OOP) WinForms Designer compatible Apps.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.