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 configgit 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/config)<a href="https://agentmods.dev/skills/merewhiplash/engram-cogitator/config"><img src="https://agentmods.dev/badge/skills/merewhiplash/engram-cogitator/config/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/config"><img src="https://agentmods.dev/badge/skills/merewhiplash/engram-cogitator/config.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.00045 | $0.01591 |
| Opus 5 | $0.00023 | $0.00796 |
| Sonnet 5 | $0.00009 | $0.00318 |
| Haiku 4.5 | $0.00005 | $0.00159 |
Grade A, and why
config 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 — 193 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Configure Cogitation
Cogitation reads config from two places:
- EC memory (
type: config) — commands and conventions: test/lint/build commands, branch convention. Managed in this skill's Steps 1–5. .cogitation/config.json(repo root, version-controlled) — feature toggles. Defaults are conservative (everything off). See "Feature toggles" below.
Announce: "I'm using the config skill to manage project settings."
The Flow
Load Current → Present → Modify → Save → Verify
Step 1: Load Current Configuration
ec_search:
query: project config
type: config
area: project
If no config found:
"No configuration found. Want to initialize cogitation for this project?"
If yes → Use @cog-init
Step 2: Present Current Settings
## Current Configuration
| Setting | Value |
|---------|-------|
| Test command | `pnpm test` |
| Lint command | `pnpm lint` |
| Build command | `pnpm build` |
| Branch convention | `feat/fix/chore` |
What would you like to change?
Step 3: Modify Settings
Use AskUserQuestion:
{
"questions": [{
"question": "Which setting do you want to modify?",
"header": "Setting",
"options": [
{ "label": "Test command", "description": "Command to run tests" },
{ "label": "Lint command", "description": "Command to check types/lint" },
{ "label": "Build command", "description": "Command to build project" },
{ "label": "Branch convention", "description": "How branches are named" }
],
"multiSelect": true
}]
}
For each selected setting, ask for the new value:
{
"questions": [{
"question": "What should the test command be?",
"header": "Test",
"options": [
{ "label": "pnpm test", "description": "pnpm package manager" },
{ "label": "npm test", "description": "npm package manager" },
{ "label": "go test ./...", "description": "Go testing" },
{ "label": "cargo test", "description": "Rust testing" }
],
"multiSelect": false
}]
}
What ships with it
1 file 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.
- 10d ago First seen · 193 lines · 45 tokens per session scan A 023a5120dc07
config is a skill published in the GitHub repository MereWhiplash/engram-cogitator (4 stars, last pushed 2mo ago), licensed MIT. It adds 45 tokens to every session and 1,591 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
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
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…