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/configure)<a href="https://agentmods.dev/skills/k9aif/k9-aif-framework/configure"><img src="https://agentmods.dev/badge/skills/k9aif/k9-aif-framework/configure.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.00038 | $0.00454 |
| Opus 5 | $0.00019 | $0.00227 |
| Sonnet 5 | $0.00008 | $0.00091 |
| Haiku 4.5 | $0.00004 | $0.00045 |
Grade A, and why
configure 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 7d 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.
What it actually says
K9-AIF: Configure
Set up the K9-AIF plugin context for this session. This must be run before any other /k9aif: skill.
What to do
Ask the user the following two questions (one at a time):
-
Project root — the absolute path to the k9-aif-framework repository.
"What is your project root? (e.g.
/Users/yourname/ai/k9-aif-framework)"- Verify the path exists and contains
k9_aif_abb/— if not, tell the user it doesn't look like a K9-AIF project and ask again.
- Verify the path exists and contains
-
App name — the name of the app to work on.
"Which app are you working on?"
- List the existing folders under
examples/andk9_projects/so the user can pick one. - Or the user can type a new name to create a new app.
- If a new name is given, confirm: "App
<name>does not exist yet. Create it underexamples/<name>/?"
- List the existing folders under
On success
Confirm with:
"K9-AIF context configured. Project: <project_root> App: <app_name> → <project_root>/examples/<app_name>/
You can now use: /k9aif:add-agent, /k9aif:add-squad, /k9aif:add-validation-loop, /k9aif:add-router, /k9aif:add-adapter, /k9aif:inspect"
Store the confirmed values as:
K9AIF_PROJECT_ROOT= the absolute project pathK9AIF_APP_NAME= the app name
Re-running configure
If configure has already been run, show the current context and ask:
"Current context — Project: , App: . Do you want to change it?"
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.
- 7d ago First seen · 41 lines · 38 tokens per session scan A 505f1c9e00c1
configure is a skill published in the GitHub repository k9aif/k9-aif-framework (2 stars, last pushed today), licensed Apache-2.0. It adds 38 tokens to every session and 454 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…
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…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
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…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…