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 MereWhiplash/engram-cogitator --skill onboardgit clone --depth 1 https://github.com/MereWhiplash/engram-cogitatorWrote 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/merewhiplash/engram-cogitator/onboard)<a href="https://agentmods.dev/skills/merewhiplash/engram-cogitator/onboard"><img src="https://agentmods.dev/badge/skills/merewhiplash/engram-cogitator/onboard/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/merewhiplash/engram-cogitator/onboard"><img src="https://agentmods.dev/badge/skills/merewhiplash/engram-cogitator/onboard.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.00043 | $0.00899 |
| Opus 5 | $0.00022 | $0.00449 |
| Sonnet 5 | $0.00009 | $0.00180 |
| Haiku 4.5 | $0.00004 | $0.00090 |
Grade A, and why
onboard 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 10d 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 — 141 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Onboard to Project
Pull institutional knowledge from EC to get context on an existing project.
Announce: "I'm using the onboard skill to pull project context from EC."
The Flow
Verify EC → Load Config → Pull Memories → Summarize → Ready
Step 1: Verify EC Connection
ec_search: test connection
If EC unavailable: Stop. Cannot onboard without EC.
Step 2: Load Project Configuration
ec_search: project config
Extract:
- Test command
- Lint command
- Build command
- Branch convention
If no config found:
"This project hasn't been initialized for cogitation. Want me to set it up?"
If yes → Use @cog-init
Step 3: Pull All Memories
Search each memory type:
ec_search: type:decision
ec_search: type:learning
ec_search: type:pattern
Step 3.5: Graphify Structural Recon (STRICT when enabled)
Read .cogitation/config.json. If graphify.enabled is true, structural recon is REQUIRED — do not skip it.
- Ensure a graph exists (the AST build needs no model, no API key):
test -f graphify-out/graph.json || graphify update . - Orient on structure:
graphify query "What are the main components and how do they connect?" --budget 800 - For specific symbols later, use
graphify query "..."/graphify explain "<symbol>".
The two sources are complementary: EC = decisions/gotchas/patterns; graphify = code structure/call-graph. Fold both into the briefing. If graphify.enabled is absent or false, skip this step entirely.
Step 4: Categorize and Summarize
Organize findings by area:
Architectural Decisions
List decisions with their rationale. Group by component/area.
Learnings (Gotchas & Workarounds)
List discovered issues and their solutions. Highlight anything that would be costly to rediscover.
Patterns (Conventions)
List established patterns and conventions specific to this project.
Step 5: Present Summary
Format as a briefing:
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.
- 10d ago First seen · 141 lines · 43 tokens per session scan A ab0b9fba870e
onboard is a skill published in the GitHub repository MereWhiplash/engram-cogitator (4 stars, last pushed 2mo ago), licensed MIT. It adds 43 tokens to every session and 899 once invoked, about $0.0002 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
media-ingest
Ingest video, audio, PDF, book, screenshot, and GitHub repo content into the brain. Multi-format handling with entity extraction and backlink propagation. Covers video-ingest, youtube-ingest, and book-ingest subtypes.
mem0-oss-to-platform
Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…
Cortex
Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…
memory
Use when the user asks to remember, recall, forget, update, search, or inspect durable OpenSquilla memory, including profile facts in USER.md and long-term notes in MEMORY.md or memory//.md.
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…
shellm
Reference for the shellm system — recursive LLM shell, identity management, memory, skills, trajectory, and all CLI tools. Use when working on shellm itself, debugging agent behavior, or understanding how the pieces fit together.