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 skills add stoleas/ansible-skills --skill ansible-cop-reviewgit clone --depth 1 https://github.com/stoleas/ansible-skillsWrote 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/skills/stoleas/ansible-skills/ansible-cop-review)<a href="https://agentmods.dev/skills/stoleas/ansible-skills/ansible-cop-review"><img src="https://agentmods.dev/badge/skills/stoleas/ansible-skills/ansible-cop-review/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/skills/stoleas/ansible-skills/ansible-cop-review"><img src="https://agentmods.dev/badge/skills/stoleas/ansible-skills/ansible-cop-review.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.00101 | $0.03710 |
| Opus 5 | $0.00051 | $0.01855 |
| Sonnet 5 | $0.00020 | $0.00742 |
| Haiku 4.5 | $0.00010 | $0.00371 |
Grade A, and why
ansible-cop-review 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 12d 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 — 620 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ansible CoP Review Skill
Review Ansible code against all Red Hat Communities of Practice (CoP) automation good practices, providing detailed feedback and actionable recommendations.
Review Scope
This skill reviews Ansible automation against the complete Red Hat CoP framework:
- Structure & Organization - Project layout, directory structure, naming
- Role Design - Variable naming, idempotency, platform support
- Playbook Design - Type-Function pattern, simplicity, tagging
- Code Quality - YAML formatting, ansible-lint compliance, documentation
- Testing - Molecule tests, idempotence validation, CI/CD integration
- Security - Credential handling, privilege escalation, validation
Review Process
1. Identify What to Review
Determine the scope:
- Single role - Review role structure and implementation
- Playbook - Review playbook design and role usage
- Collection - Review collection organization and content
- Complete project - Review entire automation project
2. Read the Code
Use appropriate tools to read all relevant files:
# List project structure
find . -type f -name "*.yml" -o -name "*.yaml"
# Read playbooks
cat playbooks/*.yml
# Read role files
cat roles/*/tasks/main.yml
cat roles/*/defaults/main.yml
cat roles/*/meta/main.yml
3. Apply CoP Standards
Check against all Red Hat CoP criteria (detailed below).
4. Generate Review Report
Provide structured feedback:
- Summary - Overall assessment
- Critical Issues - Must fix (breaks standards)
- Warnings - Should fix (best practices)
- Recommendations - Nice to have (improvements)
- Strengths - What's done well
Red Hat CoP Standards Checklist
Structure & Organization
Project Structure
Standard:
project/
├── ansible.cfg
├── inventory/
│ ├── production/
│ │ ├── hosts
│ │ └── group_vars/
│ └── staging/
├── playbooks/
│ ├── types/ # Type playbooks
│ │ ├── web_server.yml
│ │ └── database.yml
│ └── landscapes/ # Landscape playbooks
│ └── ecommerce.yml
├── roles/ # Local roles
└── collections/
└── requirements.yml
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 12d ago First seen · 620 lines · 101 tokens per session scan A 7d1694528720
ansible-cop-review is a skill published in the GitHub repository stoleas/ansible-skills (5 stars, last pushed 2d ago), licensed MIT. It adds 101 tokens to every session and 3,710 once invoked, about $0.0005 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-31.
Other skills, from other repositories
autoreview
Pre-commit/ship code review: Codex default; optional Claude or Pi.
omh-code-review
This is a Hermes-native code-review workflow skill.
revdiff-plan
Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…
code-reviewer
Code review specialist focused on patterns, bugs, security, and performance.
full-repo-review
Comprehensive four-wave review of all repo source files, producing a prioritized issue backlog.
agent-teams-simplify-and-harden
Implementation + audit loop using parallel agent teams with structured simplify, harden, and document passes. Spawns implementation agents to do the work, then audit agents to find complexity, security gaps, and spec deviations, then loops until code compiles cleanly, all tests pass, and auditors find zero issues or…