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 commands/basher83/lunar-claude/create-playbookgit 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/commands/basher83/lunar-claude/create-playbook)<a href="https://agentmods.dev/commands/basher83/lunar-claude/create-playbook"><img src="https://agentmods.dev/badge/commands/basher83/lunar-claude/create-playbook.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.00015 | $0.00665 |
| Opus 5 | $0.00008 | $0.00332 |
| Sonnet 5 | $0.00003 | $0.00133 |
| Haiku 4.5 | $0.00002 | $0.00067 |
Grade A, and why
create-playbook 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 2d 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.
What it actually says
Create a state-based Ansible playbook named $1.
Load the ansible-playbook-design and ansible-fundamentals skills first.
If no playbook name provided, ask for one.
Playbook location: ansible/playbooks/$1.yml (add .yml if missing)
Target hosts: Use $2 if provided with --hosts, otherwise default to all
Create state-based playbook supporting present/absent:
---
# Usage:
# Create: uv run ansible-playbook playbooks/$1.yml
# Remove: uv run ansible-playbook playbooks/$1.yml -e "resource_state=absent"
- name: [Descriptive play name]
hosts: [target]
become: true
gather_facts: true
vars:
resource_state: present
tasks:
- name: Validate state variable
ansible.builtin.assert:
that:
- resource_state in ['present', 'absent']
fail_msg: "resource_state must be 'present' or 'absent'"
# Main tasks here
After scaffolding, initialize the pipeline:
-
Create the
.claude/directory if it doesn't exist:mkdir -p "$CLAUDE_PROJECT_DIR/.claude" -
Ensure
.gitignorecontains ansible-workflows patterns (append if missing):
# Ansible Workflows plugin state (auto-added)
.claude/ansible-workflows.local.md
.claude/ansible-workflows.*.bundle.md
- Write state file
$CLAUDE_PROJECT_DIR/.claude/ansible-workflows.local.md:
---
active: true
pipeline_phase: generating
target_path: ansible/playbooks/$1.yml
current_agent: ansible-generator
started_at: "[ISO timestamp]"
validation_attempts: 0
last_validation_passed: true
---
# Ansible Workflows Pipeline
Target: ansible/playbooks/$1.yml
Type: playbook
- Write scaffolding bundle
$CLAUDE_PROJECT_DIR/.claude/ansible-workflows.scaffolding.bundle.md:
---
source_agent: create-playbook
target_agent: ansible-generator
timestamp: "[ISO timestamp]"
target_path: ansible/playbooks/$1.yml
target_type: playbook
---
# Scaffolding Bundle
## Target Path
ansible/playbooks/$1.yml
## User Requirements
[Capture any user-specified requirements, hosts, or context]
## Files Created
- ansible/playbooks/$1.yml (scaffolded)
## Next Steps
Implement the playbook tasks based on user requirements.
- Hand off to
ansible-generatoragent with the playbook path
Report: playbook path, state pattern implemented, pipeline initialized.
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.
- 2d ago First seen · 104 lines · 15 tokens per session scan A 44181f72556f
create-playbook is a command published in the GitHub repository basher83/lunar-claude (22 stars, last pushed today), licensed MIT. It adds 15 tokens to every session and 665 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-09-03.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
constitution
Create or update the project constitution from interactive or provided principle inputs.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.