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 verify-changesgit 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/verify-changes)<a href="https://agentmods.dev/skills/dds-solutions/ai-tadpole-os/verify-changes"><img src="https://agentmods.dev/badge/skills/dds-solutions/ai-tadpole-os/verify-changes/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/verify-changes"><img src="https://agentmods.dev/badge/skills/dds-solutions/ai-tadpole-os/verify-changes.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.00038 | $0.01106 |
| Opus 5.5 | $0.00015 | $0.00442 |
| Sonnet 5.5 | $0.00008 | $0.00221 |
| Haiku 4.5 | $0.00004 | $0.00111 |
Grade A, and why
verify-changes 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 6d 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
88% identical to verify-changes — 153 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 — 86 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 / verify-changes
- Architecture:
@docs ARCHITECTURE:Documentation- Failure Path: Declaring tasks complete without execution evidence, uninspected compiler errors, or broken invariant tests.
- Observability: Traceability via
execution/parity_guard.py([SKILL])
Verify Changes — Prove Code Works
Core Principle: "Code that exists" $\ne$ "Code that works." Verification by inspection ("it looks fine") or assumption ("types check out") is prohibited. Verification requires empirical execution evidence.
Workflow Bindings: Integrated into/test,/refactor, and/deploy.
🎯 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/verification_tiers_and_evidence_matrix.md |
The 4-Tier Verification Hierarchy, exit criteria, and evidence presentation formats | Planning verification passes after non-trivial edits |
scripts/change_verifier.py |
Automated git status inspector mapping modified files to required compilation/test gates | Determining mandatory verification commands |
🚦 1. The 4-Tier Verification Hierarchy
Never declare a task "done" without executing the applicable tier:
[TIER 1: COMPILATION] ───> [TIER 2: STATIC LINT] ───> [TIER 3: AUTOMATED TEST] ───> [TIER 4: RUNTIME PROOF]
tsc / cargo check eslint / clippy vitest / cargo test CLI run / HTTP check
- Tier 1 (Compilation & Types):
- TypeScript:
npx tsc --noEmit - Rust:
cargo check --manifest-path server-rs/Cargo.toml
- TypeScript:
- Tier 2 (Static Analysis):
- TypeScript:
npm run lint - Rust:
cargo clippy --manifest-path server-rs/Cargo.toml -- -D warnings
- TypeScript:
- Tier 3 (Automated Test Witness):
- Run Vitest or Cargo tests asserting the modified code paths.
- Tier 4 (Runtime Execution Evidence):
- Execute the actual script or call the endpoint to verify runtime behavior.
What ships with it
2 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.
- 6d ago Changed · -49 lines 9a2371f8e89a
- 1mo ago First seen · 135 lines · 38 tokens per session scan A 370a5ebf016d
verify-changes is a skill published in the GitHub repository DDS-Solutions/AI-TadPole-OS (8 stars, last pushed 2d ago), licensed MIT. It adds 38 tokens to every session and 1,106 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 88% identical to verify-changes, differing in 153 lines, and is treated as a copy.
Other skills, from other repositories
test-electron-app
Drive the real running PostHog Electron app (live tRPC, workspace-server, real data) over CDP with agent-browser. Connect to the running app on port 9222, test desktop changes against a local Django stack, snapshot the accessibility tree, inspect network requests, and screenshot only when explicitly asked. Use when…
agent-upkeep
Perform one small, scoped maintenance improvement to the Elements monorepo and open a single reviewable pull request. Use this skill for scheduled or unattended upkeep runs that improve unit test coverage for one file, fix one behavioral bug in one module, or move one off ESLint rule toward enforcement to reduce…
authoring-tests
Write and run automated tests for Elements components including unit, accessibility, visual, SSR, and lighthouse tests. Use this skill whenever the user wants to write, create, update, or debug test files (.test.ts, .test.axe.ts, .test.visual.ts, .test.ssr.ts, .test.lighthouse.ts). Also trigger when the user asks…
troubleshooting
Diagnose and resolve common issues including test failures, build errors, performance regressions, and development environment problems. Use this skill whenever the user reports something broken, failing, timing out, hanging, or producing unexpected results. Trigger on test failures (elementIsStable timeouts, flaky…
debug-and-test
Use when debugging or validating an Air Jam project so diagnostics, logging, and tests stay intentional, structured, and aligned with the project architecture.
server-side-calls
Call tRPC procedures directly from server code using t.createCallerFactory() and router.createCaller(context) for integration testing, internal server logic, and custom API endpoints. Catch TRPCError and extract HTTP status with getHTTPStatusCodeFromError(). Error handling via onError option.