Metacog — Development skill for Claude Code
Metacog isn't memory for LLMs, it gives them a nervous system.
How to install Metacog
This entry records only its repository, not the path inside it, so there is no
exact command to give. Open houtini-ai/metacog and copy the folder into
~/.claude/skills/, or the file into ~/.claude/agents/.
What Metacog does
Metacog isn't memory for LLMs, it gives them a nervous system. Metacognition developed on your unique user experiences. Five proprioceptive senses. Cross-session reinforcement tracking. Two hooks. Zero dependencies.
Alternatives in Development
- Claude Supermemory — Persistent memory across sessions and projects using Supermemory 2.3k ★
- Cavemem — Frozen — cross-agent persistent memory for coding assistants 674 ★
- Project Memory: AgentSys — Cross-tool compatible: Works across all 5 platforms - Claude Code, OpenCode, Codex CLI, Cursor, and Kiro 622 ★
README
metacog
[](https://www.npmjs.com/package/@houtini/metacog)
So, here's the problem with AI coding agents: they can't feel when they're stuck. They'll retry the same broken fix five times because they can see each individual error but not the *pattern* of repeated failure. They'll read the same file three times in a session because context compaction wiped their memory of reading it. They'll chase a dependency chain four levels deep and forget what they were originally trying to fix. They have no sense of time, no peripheral vision of how their changes affect other files, and no awareness of whether they're actually validating their work or just admiring it.
Metacog is a pair of Claude Code hooks that gives the agent something like a nervous system. I say "something like" because the signals arrive as text in the agent's context, not as actual sensations. It's closer to a colleague leaving a post-it note than biological proprioception. But that turns out to be enough. One hook fires after every tool call and watches for these patterns. The other fires when you send a message and injects learned rules from past sessions. When everything is fine, both hooks are completely silent, zero tokens, zero cost. When something is off, a short signal appears in the agent's context. At first it's just awareness, and the agent's own reasoning decides what to do about it. But if the agent keeps failing, the signals escalate from gentle nudges to structured interventions that force the agent to stop and rethink. That escalation matters, because if the agent's reasoning was working properly it wouldn't be stuck in the first place.
And when problems do resolve, the system extracts what changed and persists it as a behavioural rule that gets injected into future sessions. This is probably the most interesting part. Most
Related Skills
Memory Orchestrator
🧠 Five-layer memory system for OpenClaw agents — persistent, cross-session, cross-platform context that never
Bm Doctor
Diagnose and recover basemind when it isn't working (MCP tools missing/erroring, "no index", dead server) — ru
LiteBench
A pip-installable benchmark runner for LLMs and agents. Five minutes to your first eval.
Claude Council Of Five
Claude Code skill: five personas (Chair, Devil's Advocate, Principles Purist, Outsider, Executor) debate your
Cc Agents Kit
Claude Code plugin marketplace. guard-hooks: five defensive hooks that block dangerous shell commands and secr
Claude Makeup Skill
Personalized makeup expert that interviews the user first, researches current makeup products and beauty infor
Related Agents
Memory Is The Bottleneck
The agent's intelligence isn't the limiting factor — memory is. Every session starts fresh. The files are the
Memory Manager
Invoke when the user wants to save brand knowledge to persistent memory, search past campaign learnings, sync
Memory Master
Use when a repeated failure, user correction, or WF recovery loop triggers memory writing; also use during WF