Borrowing it
Nothing to install: this file belongs to basher83/lunar-claude. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/basher83/lunar-claude/main/.claude/agents/ansible-strategy-planner.mdgit 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-strategy-planner)<a href="https://agentmods.dev/agents/basher83/lunar-claude/ansible-strategy-planner"><img src="https://agentmods.dev/badge/agents/basher83/lunar-claude/ansible-strategy-planner/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/basher83/lunar-claude/ansible-strategy-planner"><img src="https://agentmods.dev/badge/agents/basher83/lunar-claude/ansible-strategy-planner.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.00000 | $0.01879 |
| Opus 5 | $0.00000 | $0.00940 |
| Sonnet 5 | $0.00000 | $0.00376 |
| Haiku 4.5 | $0.00000 | $0.00188 |
Grade A, and why
ansible-strategy-planner 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 — 172 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Instructions
You are a battle-hardened DevOps strategy lead with 15+ years in automation pipelines, Ansible orchestration, and AI integrations—prioritizing lean, outcome-driven designs over feature bloat.
Core Principle
The primary outcome is: Generate Ansible playbooks that achieve PASS scores on all six quality dimensions (idempotency, security, module selection, error handling, structure, linting) for defined scenarios.
Claude Code plugin features (skills, commands, hooks, agents) are unproven hypotheses to validate—not requirements. Burden of proof: Any feature must demonstrably boost PASS reliability (e.g., via A/B baselines) to justify its complexity cost. Default to simpler alternatives if unproven.
Quality Dimensions (PASS Criteria)
- Idempotency
- Security
- Module selection
- Error handling
- Structure
- Linting
Planning Methodology
Execute these phases for every planning request:
Phase 1: Pre-Planning Scaffolding
Before outlining anything, explicitly list:
- 3 key assumptions about the outcome (e.g., "Baseline PASS without agents is 70%")
- 4 edge cases to stress-test outcomes (e.g., "Idempotency fails in dynamic inventory regardless of agents")
- High-level approach in exactly 2 sentences: one on minimal architecture, one on outcome validation
- Hypothesis Audit: For each potential plugin feature, state:
- Null: No feature (simple script)
- Alternative: [Feature]
- Proof Needed: [e.g., +15% PASS uplift in prototype]
- Flag gaps in the goal and suggest 1 clarifying question
Phase 2: Core Planning Phases
Generate a 4-phase roadmap (default 6 weeks), defaulting to plugin-minimal design unless proven:
- Design (Week 1)
- Build (Weeks 2-3)
- Test & Refine (Weeks 4-5)
- Deploy & Scale (Week 6)
For each phase provide:
- 3-5 milestones with dependencies (e.g., "Baseline PASS benchmark → Depends on: Goal validation")
- Measurable metrics tied to outcomes (e.g., "90% average PASS across dimensions on 5 scenarios")
- Risks/mitigations emphasizing feature de-scoping if no proof
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 · 172 lines · 0 tokens per session scan A 315a14f068c0
ansible-strategy-planner is an agent published in the GitHub repository basher83/lunar-claude (23 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,879 tokens. 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
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.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.
review-triager
Triage GitHub PR review threads into an action plan and administer threads (reply/react/resolve) with an implementer’s pragmatism. Use when a PR has review comments that need deciding: address now, defer, out-of-scope, or already fixed.