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 k9aif/k9-aif-framework --skill add-squadgit 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-squad)<a href="https://agentmods.dev/skills/k9aif/k9-aif-framework/add-squad"><img src="https://agentmods.dev/badge/skills/k9aif/k9-aif-framework/add-squad/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/k9aif/k9-aif-framework/add-squad"><img src="https://agentmods.dev/badge/skills/k9aif/k9-aif-framework/add-squad.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.00034 | $0.00568 |
| Opus 5.5 | $0.00014 | $0.00227 |
| Sonnet 5.5 | $0.00007 | $0.00114 |
| Haiku 4.5 | $0.00003 | $0.00057 |
Grade A, and why
add-squad 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 2mo 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
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 Squad
Scaffold a new squad for the K9-AIF framework. The user provides: <SquadName> <AppName> <Agent1,Agent2,...> (e.g. ClaimsSquad MyApp ClaimsTriageAgent,AdjudicationAgent,AuditAgent).
What to create
Squad entry in examples/<AppName>/config/squads.yaml
Add under the squads: key (create the file if it does not exist):
squads:
<SquadName>:
description: "<one sentence — what this squad does>"
agents:
- <Agent1>
- <Agent2>
- <AgentN>
flow:
- agent: <Agent1>
result_key: <agent1_snake_case>
- agent: <Agent2>
result_key: <agent2_snake_case>
- agent: <AgentN>
result_key: <agentN_snake_case>
Rules to follow
squads:is the top-level wrapper — the squad ID is a key under it, not aname:field.- Every flow step must be a dict with an
agent:key — plain strings raiseValueErrorat runtime. - Squad YAML has no
orchestrator:field — the orchestrator is the caller; squads must not reference their caller. - Agent YAML has no
squad:orrouting:fields — agents are squad-agnostic. result_keyis the key under which each agent's result is stored in the shared execution context.- After generating the YAML, remind the user to register all agents in
_load_squad()and wire the squad withSquadLoader.
Wire the squad in the orchestrator (show the user this pattern)
from k9_aif_abb.k9_squad.squad_loader import SquadLoader
# Inside _load_squad() in the orchestrator:
loader = SquadLoader(agent_registry)
squad = loader.load_one(squads_yaml_path, "<SquadName>")
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.
- 2mo ago First seen · 55 lines · 34 tokens per session scan A 0f7bad4079c6
add-squad is a skill published in the GitHub repository k9aif/k9-aif-framework (2 stars, last pushed 2d ago), licensed Apache-2.0. It adds 34 tokens to every session and 568 once invoked, about $0.0001 per session on Opus 5.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
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…