Borrowing it
Nothing to install: this file belongs to terrene-foundation/metis. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/terrene-foundation/metis/main/.claude/skills/28-coc-reference/SKILL.mdgit 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/28-coc-reference)<a href="https://agentmods.dev/skills/terrene-foundation/metis/28-coc-reference"><img src="https://agentmods.dev/badge/skills/terrene-foundation/metis/28-coc-reference.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.00051 | $0.00683 |
| Opus 5 | $0.00026 | $0.00342 |
| Sonnet 5 | $0.00010 | $0.00137 |
| Haiku 4.5 | $0.00005 | $0.00068 |
Grade A, and why
coc-reference 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 4d 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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
COC Template Implementation Reference
How the COC five-layer architecture is implemented in the Kailash COC template repos. For COC spec/concepts (fault lines, value inversion, autonomous execution), see co-reference/coc-spec.md.
Implementation Inventory
| CO Layer | COC Artifact Type | Count | Purpose |
|---|---|---|---|
| L1 Intent | Agents | 30+ | Specialized domain experts |
| L2 Context | Skills + CLAUDE.md | 28+ dirs, 400+ files | Institutional knowledge library |
| L3 Guardrails | Rules + Hooks | 9 rules, 9 hooks | Deterministic enforcement |
| L4 Instructions | Commands | 20 commands | Phase-gated workflow |
| L5 Learning | Learning pipeline | observations + digest + codification | Knowledge compounding |
Layer 3: Defense in Depth
Critical rules have 5-8 independent enforcement layers:
Rule file (soft — AI interprets)
+ Hook script (hard — deterministic, exit code 2 blocks)
+ Anti-amnesia hook (re-injects every message, survives compression)
+ Code review by reviewer
+ Security review by security-reviewer
+ CI pipeline check
The anti-amnesia hook (user-prompt-rules-reminder.js) is the single most important mechanism — fires on every user message.
Layer 4: Seven-Phase Workflow
| Phase | Command | Quality Gate |
|---|---|---|
| Analysis | /analyze |
reviewer |
| Planning | /todos |
Human approval |
| Implementation | /implement |
reviewer + security-reviewer |
| Validation | /redteam |
reviewer |
| Knowledge | /codify |
gold-standards-validator |
| Release | /release |
Human approval |
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.
- 4d ago First seen · 68 lines · 51 tokens per session scan A 769945024121
coc-reference is a skill published in the GitHub repository terrene-foundation/metis (2 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 51 tokens to every session and 683 once invoked, about $0.0003 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-09-03.
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-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
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…