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 skills/akin-ozer/cc-devops-skills/fluentbit-validatornpx skills add akin-ozer/cc-devops-skills --skill fluentbit-validatorgit clone --depth 1 https://github.com/akin-ozer/cc-devops-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/akin-ozer/cc-devops-skills/fluentbit-validator)<a href="https://agentmods.dev/skills/akin-ozer/cc-devops-skills/fluentbit-validator"><img src="https://agentmods.dev/badge/skills/akin-ozer/cc-devops-skills/fluentbit-validator.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 | $0.00026 | $0.01293 |
| Opus 5 | $0.00013 | $0.00647 |
| Sonnet 5 | $0.00005 | $0.00259 |
| Haiku 4.5 | $0.00003 | $0.00129 |
Grade A, and why
fluentbit-validator 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 5d 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 — 181 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fluent Bit Validator
Use this skill to run deterministic, repeatable validation for Fluent Bit classic-mode configs.
Trigger Phrases
Use this skill when prompts look like:
- "Validate this
fluent-bit.confbefore deploy" - "Lint my Fluent Bit config and report issues"
- "Check tag routing and output matches in Fluent Bit"
- "Run security checks for Fluent Bit config"
- "Dry-run Fluent Bit config and tell me what failed"
Execution Model
Run steps in order. Do not skip Stage 0.
Stage 0: Precheck (Required)
Run from skill directory:
cd devops-skills-plugin/skills/fluentbit-validator
Check required and optional binaries:
command -v python3 >/dev/null 2>&1 && echo "python3: available" || echo "python3: missing"
command -v fluent-bit >/dev/null 2>&1 && echo "fluent-bit: available" || echo "fluent-bit: missing (dry-run will be skipped)"
Precheck protocol:
- If
python3is missing: stop script-based validation, report blocker, and switch to manual config review only. - If
fluent-bitis missing: continue static checks, skip dry-run, and record aRecommendationexplaining skip reason and next step.
Stage 1: Static Validation (Required)
Default command:
python3 scripts/validate_config.py --file <config-file> --check all
Use targeted checks only when requested:
python3 scripts/validate_config.py --file <config-file> --check structure
python3 scripts/validate_config.py --file <config-file> --check sections
python3 scripts/validate_config.py --file <config-file> --check tags
python3 scripts/validate_config.py --file <config-file> --check security
python3 scripts/validate_config.py --file <config-file> --check performance
python3 scripts/validate_config.py --file <config-file> --check best-practices
python3 scripts/validate_config.py --file <config-file> --check dry-run
Strict CI gate (optional):
python3 scripts/validate_config.py --file <config-file> --check all --fail-on-warning
What ships with it
11 files 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.
- .gitignore 18 B
- scripts/validate_config.py 58 KB runs code
- scripts/validate.sh 3.9 KB runs code
- tests/invalid-missing-required.conf 349 B
- tests/invalid-opentelemetry.conf 421 B
- tests/invalid-security-issues.conf 405 B
- tests/invalid-tag-mismatch.conf 351 B
- tests/test_validate_config.py 22 KB runs code
- tests/valid-basic.conf 887 B
- tests/valid-multioutput.conf 1.2 KB
- tests/valid-opentelemetry.conf 917 B
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.
- 5d ago First seen · 181 lines · 26 tokens per session scan A 62eb91991939
fluentbit-validator is a skill published in the GitHub repository akin-ozer/cc-devops-skills (305 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 26 tokens to every session and 1,293 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.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…