Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add k9aif/k9-aif-framework/plugin install k9aifWrote 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/inspect)<a href="https://agentmods.dev/skills/k9aif/k9-aif-framework/inspect"><img src="https://agentmods.dev/badge/skills/k9aif/k9-aif-framework/inspect.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.1 | $0.00036 | $0.01210 |
| Opus 5 | $0.00018 | $0.00605 |
| Sonnet 5 | $0.00007 | $0.00242 |
| Haiku 4.5 | $0.00004 | $0.00121 |
Grade A, and why
inspect 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 — 92 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: Inspect (k9_code_review)
Review K9-AIF Solution Building Block (SBB) code for architectural compliance against ABB contracts.
First: check $ARGUMENTS. If empty, ask the user before doing anything else:
"Which folder would you like to inspect? (e.g.
examples/MyApp,k9_projects/MyApp, or a subfolder likeexamples/MyApp/agents)" Do not proceed until the user provides a path.
The user specifies the SBB folder to inspect via $ARGUMENTS. Accepted forms:
- App name:
EOC→ resolves toexamples/K9X_Enterprise_Insurance_OperationsCenter/ - Relative path:
examples/MyApp/ - Absolute path:
/Users/ravinatarajan/ai/k9-aif-framework/examples/MyApp/ - Subfolder:
examples/MyApp/agents/— inspect only agents in that app
Default: inspect SBBs only.
- Primary targets:
examples/<AppName>/andk9_projects/<AppName>/ - If the user explicitly passes a path inside
k9_aif_abb/, inspect it — some organizations extend or customize the ABB layer and need to verify their changes are consistent with the ABB contracts. - If the user passes
k9_aif_abb/without a subfolder (the entire ABB), ask for confirmation: "You are about to inspect the full ABB layer. Are you sure? This is usually only needed if your organization has modified the framework core."
What to check
1. Three-layer decoupling violations
- Agent imports or references a Squad class → violation
- Squad YAML contains an
orchestrator:field → violation - Agent YAML contains a
squad:orrouting:field → violation - Orchestrator references another orchestrator by name directly (not via registry) → warning
2. LLM invocation pattern
- Agent calls
OllamaLLMdirectly → violation (must usellm_invoke) - Agent calls
LLMFactory.get()directly → violation (must usellm_invoke) - Agent calls
llm_invokewithout wrapping in try/except RuntimeError → warning InferenceRequestbuilt withouttask_type→ warning (model scoring degraded)
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 · 92 lines · 36 tokens per session scan A 05960f30c095
inspect is a skill published in the GitHub repository k9aif/k9-aif-framework (2 stars, last pushed 2d ago), licensed Apache-2.0. It adds 36 tokens to every session and 1,210 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
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…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…