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 automateyournetwork/netclaw --skill aap-lintgit clone --depth 1 https://github.com/automateyournetwork/netclawWrote 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/automateyournetwork/netclaw/aap-lint)<a href="https://agentmods.dev/skills/automateyournetwork/netclaw/aap-lint"><img src="https://agentmods.dev/badge/skills/automateyournetwork/netclaw/aap-lint/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/automateyournetwork/netclaw/aap-lint"><img src="https://agentmods.dev/badge/skills/automateyournetwork/netclaw/aap-lint.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00049 | $0.00852 |
| Opus 5 | $0.00024 | $0.00426 |
| Sonnet 5 | $0.00010 | $0.00170 |
| Haiku 4.5 | $0.00005 | $0.00085 |
Grade A, and why
aap-lint 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 10d 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ansible Lint Operations
MCP Server
- Repository: sibilleb/AAP-Enterprise-MCP-Server
- Transport: stdio (Python via
uv run ansible-lint.py) - Install:
git clone+uv sync(orpip install -e .) - Requires:
ansible-lintinstalled
Available Tools (9)
| Tool | What It Does |
|---|---|
lint_playbook |
Lint playbook content with configurable profiles and output formats |
lint_file |
Lint a specific Ansible file at a given path |
lint_role |
Comprehensive linting of an Ansible role directory |
list_rules |
Display available ansible-lint rules with optional tag filtering |
list_tags |
Show all tags for categorizing lint rules |
validate_syntax |
Quick syntax validation using syntax-specific rules |
check_best_practices |
Evaluate content against best practices with severity categorization |
analyze_project |
Comprehensive report on an entire Ansible project structure |
get_ansible_lint_version |
Return installed ansible-lint version |
Key Concepts
| Concept | What It Means |
|---|---|
| Profile | Lint strictness level (min, basic, moderate, safety, shared, production) |
| Rule | Individual lint check (e.g., yaml[truthy], no-changed-when, fqcn) |
| Tag | Rule category for filtering (e.g., command-shell, formatting, idiom) |
| FQCN | Fully Qualified Collection Name — required in production profiles |
Workflow: Pre-Deployment Playbook Validation
- Syntax check:
validate_syntax— catch YAML and Ansible syntax errors - Best practices:
check_best_practices— evaluate against standards - Full lint:
lint_playbookwith production profile — comprehensive check - Review rules:
list_rules— understand which rules triggered violations - Report: Pass/fail with specific violations and remediation guidance
Workflow: Project-Wide Quality Audit
- Analyze project:
analyze_project— scan entire Ansible project structure - Review findings: Group violations by file, rule, and severity
- Check roles:
lint_rolefor each role directory - Report: Project quality scorecard with violation counts and trends
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.
- 10d ago First seen · 72 lines · 49 tokens per session scan A 6b138e63542b
aap-lint is a skill published in the GitHub repository automateyournetwork/netclaw (652 stars, last pushed 4d ago), licensed Apache-2.0. It adds 49 tokens to every session and 852 once invoked, about $0.0002 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.
Other skills, from other repositories
skill-authoring
Guide creating Claude Code skills with TDD and persuasion principles. Use for new skill development.
plugin-review
Review plugin quality with tiered checks and dependency scoping. Use for PR and pre-release audits.
plugin-quality
A review guide for checking Zhin.js plugins before release. It covers plugin structure, feature declarations, resource cleanup, message sending, and security.
test-patterns
Applies proven testing patterns — Arrange-Act-Assert (AAA), Given-When-Then, Test Data Builders, Object Mother, parameterized tests, fixtures, spies, and test doubles — to help write maintainable, reliable, and readable test suites. Use when the user asks about writing unit tests, integration tests, or end-to-end…
code-review-expert
Expert-level code review focusing on quality, security, performance, and maintainability. Use this skill for conducting thorough code reviews, identifying issues, and providing constructive feedback.
code-review
Performs thorough code reviews with focus on best practices, security, performance, and maintainability. Use this skill when reviewing pull requests, auditing code quality, or getting feedback on implementations.