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/terrene-foundation/metis/14-code-templatesnpx skills add terrene-foundation/metis --skill 14-code-templatesgit 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/skills/terrene-foundation/metis/14-code-templates)<a href="https://agentmods.dev/skills/terrene-foundation/metis/14-code-templates"><img src="https://agentmods.dev/badge/skills/terrene-foundation/metis/14-code-templates.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.00100 | $0.00846 |
| Opus 5 | $0.00050 | $0.00423 |
| Sonnet 5 | $0.00020 | $0.00169 |
| Haiku 4.5 | $0.00010 | $0.00085 |
Grade A, and why
code-templates 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 — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Kailash Code Templates
Production-ready templates for common Kailash development tasks. All follow the canonical 4-parameter pattern from /01-core-sdk.
Sub-File Index
Workflow Templates
- template-workflow-basic - Standard workflow
- WorkflowBuilder setup, node addition, 4-param connections, runtime execution, result access, error handling
- template-cyclic-workflow - Iterative workflows
- CycleNode setup, convergence checking, state persistence, iteration limits
Custom Development
- template-custom-node - Custom node creation
- Extend BaseNode, parameter definition, execute method, input validation, output formatting, registration
- template-mcp-server - MCP server creation
- MCPServer init, tool/resource registration, transport config, auth, progress reporting
Test Templates
- template-test-unit - Tier 1: Unit tests
- Fixtures, mock setup (allowed in Tier 1), assertions, fast execution
- template-test-integration - Tier 2: Integration tests
- Real database setup, workflow execution, real infrastructure fixtures, resource cleanup
- template-test-e2e - Tier 3: End-to-end tests
- Full system setup, real HTTP requests, complete user flows
Template Selection
| Task | Template | Key Pattern |
|---|---|---|
| New workflow | template-workflow-basic |
WorkflowBuilder + .build() + runtime.execute() |
| Iterative logic | template-cyclic-workflow |
CycleNode + convergence check |
| New node type | template-custom-node |
Extend BaseNode, implement execute() |
| MCP integration | template-mcp-server |
MCPServer + tool registration |
| Fast tests | template-test-unit |
Mocking allowed, <1s |
| Real infra tests | template-test-integration |
Real DB/runtime, no mocks |
| Full system tests | template-test-e2e |
Real HTTP, complete flows |
What ships with it
7 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 74 lines · 100 tokens per session scan A 7b7559f5532b
code-templates is a skill published in the GitHub repository terrene-foundation/metis (2 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 100 tokens to every session and 846 once invoked, about $0.0005 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…