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/commands/basher83/lunar-claude/create-role)<a href="https://agentmods.dev/commands/basher83/lunar-claude/create-role"><img src="https://agentmods.dev/badge/commands/basher83/lunar-claude/create-role/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/commands/basher83/lunar-claude/create-role"><img src="https://agentmods.dev/badge/commands/basher83/lunar-claude/create-role.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.00011 | $0.00663 |
| Opus 5.5 | $0.00004 | $0.00265 |
| Sonnet 5.5 | $0.00002 | $0.00133 |
| Haiku 4.5 | $0.00001 | $0.00066 |
Grade A, and why
create-role 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 2mo 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 an Ansible role named $ARGUMENTS following production patterns.
Load the ansible-role-design and ansible-fundamentals skills first.
If no role name provided, ask for one.
Role location: ansible/roles/$ARGUMENTS/
Create this structure:
ansible/roles/$ARGUMENTS/
├── defaults/main.yml
├── tasks/main.yml
├── handlers/main.yml
├── meta/main.yml
└── README.md
Variable prefix: Convert role name to snake_case (e.g., docker-host → docker_host_*)
defaults/main.yml: Role-prefixed variables with defaults tasks/main.yml: Main task router with validation handlers/main.yml: Service restart handlers (if applicable) meta/main.yml: Galaxy metadata with platform support README.md: Usage documentation
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/roles/$ARGUMENTS/
current_agent: ansible-generator
started_at: "[ISO timestamp]"
validation_attempts: 0
last_validation_passed: true
---
# Ansible Workflows Pipeline
Target: ansible/roles/$ARGUMENTS/
Type: role
- Write scaffolding bundle
$CLAUDE_PROJECT_DIR/.claude/ansible-workflows.scaffolding.bundle.md:
---
source_agent: create-role
target_agent: ansible-generator
timestamp: "[ISO timestamp]"
target_path: ansible/roles/$ARGUMENTS/
target_type: role
---
# Scaffolding Bundle
## Target Path
ansible/roles/$ARGUMENTS/
## User Requirements
[Capture any user-specified requirements or context]
## Files Created
- ansible/roles/$ARGUMENTS/defaults/main.yml
- ansible/roles/$ARGUMENTS/tasks/main.yml
- ansible/roles/$ARGUMENTS/handlers/main.yml
- ansible/roles/$ARGUMENTS/meta/main.yml
- ansible/roles/$ARGUMENTS/README.md
## Variable Prefix
[snake_case version of role name]
## Next Steps
Implement the role tasks based on user requirements.
- Hand off to
ansible-generatoragent with the role path
Report: role path, files created, variable prefix, 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.
- 2mo ago First seen · 102 lines · 11 tokens per session scan A e0f42e541762
create-role is a command published in the GitHub repository basher83/lunar-claude (23 stars, last pushed today), licensed MIT. It adds 11 tokens to every session and 663 once invoked, about $0.0000 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-09-03.
create-role compared with commands from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| create-rolebasher83/lunar-claude | Command | 23 | today | MIT | A | 11 | Claude Code |
| checklistgithub/spec-kit | Command | 149k | today | MIT | A | 13 | Claude Code |
| clarifygithub/spec-kit | Command | 149k | today | MIT | A | 27 | Claude Code |
| specifygithub/spec-kit | Command | 149k | today | MIT | A | 13 | Claude Code |
| analyzegithub/spec-kit | Command | 149k | today | MIT | A | 26 | Claude Code |
| convergegithub/spec-kit | Command | 149k | today | MIT | A | 35 | Claude Code |
| implementgithub/spec-kit | Command | 149k | today | MIT | A | 14 | Claude Code |