lint-playbook

lint-playbook is a command for coding agents from armanzeroeight/fastagent-plugins. It costs 12 tokens per session (854 once invoked), scanned A, original, MIT.

A command for checking Ansible playbooks, which are YAML files that automate server setup and deployment, for syntax errors and common problems.

In plain words
What is it for?
Use it to run Ansible's syntax check and, when installed, ansible-lint and yamllint against a selected playbook.
Why use it?
It catches invalid YAML, broken playbook structure, outdated patterns, and some security or quality issues before the playbook is run.

Command

Install

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.

agentmods
npx agentmods add commands/armanzeroeight/fastagent-plugins/lint-playbook
Clone the repo
git clone --depth 1 https://github.com/armanzeroeight/fastagent-plugins

Wrote 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.

agentmods badge for lint-playbook

README.md
[![agentmods](https://agentmods.dev/badge/commands/armanzeroeight/fastagent-plugins/lint-playbook.svg)](https://agentmods.dev/commands/armanzeroeight/fastagent-plugins/lint-playbook)
Your own site
<a href="https://agentmods.dev/commands/armanzeroeight/fastagent-plugins/lint-playbook"><img src="https://agentmods.dev/badge/commands/armanzeroeight/fastagent-plugins/lint-playbook.svg" alt="Measured on agentmods" height="20"></a>
Per session 12 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 854 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00012 $0.00854
Opus 5 $0.00006 $0.00427
Sonnet 5 $0.00002 $0.00171
Haiku 4.5 $0.00001 $0.00085

Measured 4d ago against content hash 6daef9ddeccf, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

lint-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 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.

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.

plugins/ansible-toolkit/commands/lint-playbook.md · 147 lines

How it starts

The opening of the file, as written. The whole thing — 147 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Lint Ansible Playbook

Context

  • Current directory: !pwd
  • Available playbooks: !find . -name "*.yml" -o -name "*.yaml" | grep -E "(playbook|site)" | head -20
  • Ansible version: !ansible --version 2>&1 | head -1 || echo "Ansible not installed"
  • ansible-lint installed: !ansible-lint --version 2>&1 || echo "ansible-lint not installed"

Your Task

Lint and validate the specified Ansible playbook for syntax errors, best practices violations, and potential issues.

Arguments

  • $1: Path to Ansible playbook file (required)

Steps

  1. Verify playbook file exists

    • Check if the specified file exists
    • If not provided, list available playbooks and ask user to specify
  2. Run syntax check

    ansible-playbook --syntax-check $1
    
    • Verify YAML syntax
    • Check for undefined variables
    • Validate task structure
    • Report syntax errors
  3. Run ansible-lint (if available)

    ansible-lint $1
    
    • Check best practices
    • Identify deprecated syntax
    • Check for security issues
    • Report warnings and errors
    • If not installed, suggest: pip install ansible-lint
  4. Run yamllint (if available)

    yamllint $1
    
    • Check YAML formatting
    • Verify indentation
    • Check line length
    • If not installed, suggest: pip install yamllint
  5. Analyze and summarize results

    • Categorize issues by severity
    • Highlight critical issues
    • Provide specific recommendations
    • Show line numbers for issues
  6. Provide actionable recommendations

    • Explain each issue
    • Suggest specific fixes
    • Prioritize by impact
    • Reference best practices

Output Format

## Ansible Playbook Lint Results

**Playbook:** [filename]
**Size:** [file size]

### Syntax Check
✓ Passed / ✗ Failed
[Details of syntax check]

### ansible-lint Analysis
✓ Passed / ✗ Failed
- Errors: [count]
- Warnings: [count]

[List of issues with line numbers and rules]

### YAML Lint
✓ Passed / ✗ Failed
- Errors: [count]
- Warnings: [count]

### Summary

**Critical Issues:** [count]
- [Issue 1 with fix]
- [Issue 2 with fix]

**Warnings:** [count]
- [Warning 1 with recommendation]

**Recommendations:**
1. [Priority 1 fix with code example]
2. [Priority 2 fix with code example]

Read the full file on GitHub · 147 lines

Changes

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.

  1. 4d ago First seen · 147 lines · 12 tokens per session scan A 6daef9ddeccf

Subscribe to this mod's changes

lint-playbook is a command published in the GitHub repository armanzeroeight/fastagent-plugins (29 stars, last pushed 1mo ago), licensed MIT. It adds 12 tokens to every session and 854 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.