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 commands/terrene-foundation/metis/sdkgit clone --depth 1 https://github.com/terrene-foundation/metisWrote 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/commands/terrene-foundation/metis/sdk)<a href="https://agentmods.dev/commands/terrene-foundation/metis/sdk"><img src="https://agentmods.dev/badge/commands/terrene-foundation/metis/sdk.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.00000 | $0.00487 |
| Opus 5 | $0.00000 | $0.00244 |
| Sonnet 5 | $0.00000 | $0.00097 |
| Haiku 4.5 | $0.00000 | $0.00049 |
Grade A, and why
sdk 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.
This is a copy
100% identical to sdk — 0 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/sdk - Core SDK Quick Reference
Purpose
Load the Kailash Core SDK skill for workflow patterns, node configuration, and runtime execution.
Step 0: Verify Project Uses Kailash
Before loading SDK patterns, check that this project uses Kailash:
- Look for
kailashinrequirements.txt,pyproject.toml,setup.py,Cargo.toml - Look for
from kailash/import kailashin source files
If not found, inform the user: "This project doesn't appear to use Kailash SDK. These patterns may not apply. Continue anyway?"
Quick Reference
| Command | Action |
|---|---|
/sdk |
Load Core SDK patterns and workflow basics |
/sdk workflow |
Show WorkflowBuilder patterns |
/sdk runtime |
Show runtime selection guidance |
/sdk nodes |
Show node configuration patterns |
What You Get
- WorkflowBuilder patterns
- Node configuration (3-param pattern)
- Runtime execution (
runtime.execute(workflow.build())) - Connection patterns (4-param)
- Async vs sync runtime selection
Quick Pattern
from kailash.workflow.builder import WorkflowBuilder
from kailash.runtime import LocalRuntime
workflow = WorkflowBuilder()
workflow.add_node("NodeType", "node_id", {"param": "value"})
workflow.add_connection("node1", "output", "node2", "input")
runtime = LocalRuntime()
results, run_id = runtime.execute(workflow.build())
Critical Rules
- ALWAYS call
.build()before execution - ALWAYS use
runtime.execute(workflow.build())- neverworkflow.execute(runtime) - ALWAYS use absolute imports (never relative)
- ALWAYS use string-based node registration
Agent Teams
When working with Core SDK, deploy:
- pattern-expert — Workflow patterns, node configuration, cyclic patterns
Related Commands
/db- DataFlow database operations/api- Nexus multi-channel deployment/ai- Kaizen AI agents/test- Testing strategies/validate- Project compliance checks
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 · 70 lines · 0 tokens per session scan A d8165b6b0ce6
sdk is a command published in the GitHub repository terrene-foundation/metis (2 stars, last pushed 4mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 487 tokens. A static security scan graded it A with 0 findings. It is 100% identical to sdk, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.