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 DDS-Solutions/AI-TadPole-OS --skill lint-and-validategit clone --depth 1 https://github.com/DDS-Solutions/AI-TadPole-OSWrote 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/dds-solutions/ai-tadpole-os/lint-and-validate)<a href="https://agentmods.dev/skills/dds-solutions/ai-tadpole-os/lint-and-validate"><img src="https://agentmods.dev/badge/skills/dds-solutions/ai-tadpole-os/lint-and-validate/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/dds-solutions/ai-tadpole-os/lint-and-validate"><img src="https://agentmods.dev/badge/skills/dds-solutions/ai-tadpole-os/lint-and-validate.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.00048 | $0.01608 |
| Opus 5.5 | $0.00019 | $0.00643 |
| Sonnet 5.5 | $0.00010 | $0.00322 |
| Haiku 4.5 | $0.00005 | $0.00161 |
Grade A, and why
lint-and-validate 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 9d 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.
This is a copy
86% identical to lint-and-validate — 123 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
[!IMPORTANT] AI Context & Knowledge Heritage
- Subsystem: Agent Skills Registry / lint-and-validate
- Architecture:
@docs ARCHITECTURE:Documentation- Failure Path: Type mismatches, uninspected lint regressions, or ADG manifest drift.
- Observability: Traceability via
execution/parity_guard.py([SKILL])
Lint and Validate Quality Gate Protocol
Sovereign Invariant: Run appropriate validation gates after EVERY code modification. No task may be declared complete or reported as "done" while syntax errors, type regressions, lint warnings, or broken invariants remain.
Workflow Bindings: Integrated into/test,/refactor, and/audit.
🎯 Progressive Disclosure & L3 Reference Index
Read the core Sovereign rules below; consult deep L3 Reference Guides on demand:
| L3 Reference Guide | Purpose | Trigger / When to Load |
|---|---|---|
references/static_analysis_and_quality_gates.md |
The 4-Tier Quality Gate Hierarchy, Clippy policies, and ADG v2 standards | Auditing multi-ecosystem quality gates & configuring linters |
scripts/lint_runner.py |
Unified multi-ecosystem runner (Node.js, Rust Cargo, Python) with --test mode |
Running all applicable linters in a single deterministic pass |
scripts/type_coverage.py |
Type safety and coverage auditor detecting any/Any escapes |
Auditing TypeScript and Python type coverage ratios |
🚦 1. The 4-Tier Sovereign Quality Hierarchy
Execute checks from lowest to highest tier:
[TIER 1: SYNTAX & TYPES] ──> [TIER 2: LINTERS] ──> [TIER 3: INVARIANTS/ADG] ──> [TIER 4: PARITY]
tsc / cargo check eslint / clippy adg:verify / vitest parity_guard.py
What ships with it
3 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.
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.
- 9d ago Changed · +59 lines b4f3d5518cc4
- 1mo ago First seen · 52 lines · 48 tokens per session scan A 4d5f5d7103b7
lint-and-validate is a skill published in the GitHub repository DDS-Solutions/AI-TadPole-OS (8 stars, last pushed 5d ago), licensed MIT. It adds 48 tokens to every session and 1,608 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 86% identical to lint-and-validate, differing in 123 lines, and is treated as a copy.
Other skills, from other repositories
migrate-oxlint
Guide for migrating a project from ESLint to Oxlint. Use when asked to migrate, convert, or switch a JavaScript/TypeScript project's linter from ESLint to Oxlint.
walkeros-using-transformer-ga4
Use when wiring @walkeros/transformer-ga4 into a server flow, overriding default GA4 event mappings, dropping events, adding custom event keys, or troubleshooting GA4 Measurement Protocol decoding. Covers the before-chain wiring contract, configuration recipes, and per-field patching with extend/remove.
walkeros-debugging
Use when walkerOS events aren't reaching destinations, debugging event flow, or troubleshooting mapping issues. Covers common problems and debugging strategies.
resolving-ingestion-warnings
Diagnoses and resolves PostHog ingestion warnings — problems recorded while ingesting events (dropped events, rejected person merges, oversized payloads, invalid data). Use when a user asks why events are missing, dropped, or undercounted, why identify/alias calls don't work or accounts stay duplicated, why person or…
monitoring-ingestion-pipeline
Guide for using the Grafana MCP to monitor and diagnose the Node.js ingestion pipeline workers in production. Use when investigating event lag, drops, pipeline errors, person/group processing, Kafka consumer health, Redis, Postgres, ClickHouse downstream health, or any ingestion worker question. Covers prod-us and…
triaging-merge-queue-failures
Decision procedure for a PR that failed or was removed from the Trunk merge queue: classify the kick (superseded by a newer commit, not mergeable, a gate that failed on a cancelled run, real failure, one-off flake, or repo-wide flaky/infra issue) and take the matching action (wait, hold and fix, requeue once, or…