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/k9aif/k9-aif-framework/add-validation-loopnpx skills add k9aif/k9-aif-framework --skill add-validation-loopgit clone --depth 1 https://github.com/k9aif/k9-aif-frameworkWrote 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/k9aif/k9-aif-framework/add-validation-loop)<a href="https://agentmods.dev/skills/k9aif/k9-aif-framework/add-validation-loop"><img src="https://agentmods.dev/badge/skills/k9aif/k9-aif-framework/add-validation-loop.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.00029 | $0.00888 |
| Opus 5 | $0.00015 | $0.00444 |
| Sonnet 5 | $0.00006 | $0.00178 |
| Haiku 4.5 | $0.00003 | $0.00089 |
Grade A, and why
add-validation-loop 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 4d 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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Before doing anything else, check that /k9aif:configure has been run.
If K9AIF_PROJECT_ROOT and K9AIF_APP_NAME are not set, refuse and say:
"Please run
/k9aif:configurefirst to set your project root and app name." Do not proceed until init has been run.
K9-AIF: Add Validation Loop
Convert an existing agent — or scaffold a new one — that uses the iterative K9ValidationLoopAgent pattern instead of one-shot BaseAgent. Use this when an agent needs to test a hypothesis, observe the result, and decide whether to try again.
The user provides: <AgentName> <AppName> (e.g. FraudDetectionAgent EOC).
Decision rule — ask this first
"Does this agent need to test something, observe the result, and decide whether to try again — or does it produce its answer in one pass?"
One-pass → keep BaseAgent |
Iterative → use K9ValidationLoopAgent |
|---|---|
| Triage, routing, audit, guard, graph sync | Fraud signal correlation, claims evidence, compliance gap, document confidence |
What to generate
Python class — examples/<AppName>/agents/src/<agent_name_lower>.py
from typing import Any, Dict, Optional
from k9_aif_abb.k9_agents.validation import (
K9ValidationLoopAgent,
ValidationDisposition,
ValidationLoopContext,
ValidationLoopResult,
)
class <AgentName>(K9ValidationLoopAgent):
layer = "<AppName> <AgentName> SBB"
def __init__(self, config: Optional[Dict[str, Any]] = None, monitor=None, **kwargs):
super().__init__(config or {}, monitor=monitor, **kwargs)
def generate_hypothesis(self, loop_ctx: ValidationLoopContext):
return {"query": "<what to test>", **loop_ctx.payload}
def run_validation(self, hypothesis, loop_ctx: ValidationLoopContext):
# Call rule engine, database, LLM, or external tool here
return {"result": "placeholder", "score": 0.5}
def evaluate_observation(self, tool_result, loop_ctx: ValidationLoopContext):
confidence = tool_result.get("score", 0.0)
return {"confidence": confidence, "result": tool_result.get("result")}
def should_continue(self, observation, loop_ctx: ValidationLoopContext):
threshold = self.config.get("confidence_threshold", 0.8)
if observation["confidence"] >= threshold:
return ValidationDisposition.FINALIZE
if loop_ctx.iteration >= 3 and observation["confidence"] < 0.3:
return ValidationDisposition.ESCALATE
return ValidationDisposition.CONTINUE
def finalize(self, loop_ctx: ValidationLoopContext) -> ValidationLoopResult:
last = loop_ctx.steps[-1]
return ValidationLoopResult(
disposition=ValidationDisposition.FINALIZE,
output={"decision": "complete", "confidence": last.confidence},
steps=loop_ctx.steps,
iterations=loop_ctx.iteration,
final_confidence=last.confidence,
evidence=[str(s.observation) for s in loop_ctx.steps],
)
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.
- 4d ago First seen · 93 lines · 29 tokens per session scan A de3bdedb0015
add-validation-loop is a skill published in the GitHub repository k9aif/k9-aif-framework (2 stars, last pushed today), licensed Apache-2.0. It adds 29 tokens to every session and 888 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-31.
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…