COG is an AI-assisted second brain that stores knowledge in Markdown files and uses agents, skills, and version control to evolve it over time. It helps people manage knowledge and contacts while supporting several coding-agent tools; the catalogue entries are COG’s skills, agents, instructions, rules, and plugin surfaces.
Borrowing it
Nothing to install: this file belongs to huytieu/COG-second-brain. 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/huytieu/COG-second-brain/main/CLAUDE.mdgit clone --depth 1 https://github.com/huytieu/COG-second-brainWrote 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/instructions/huytieu/cog-second-brain/claude-md)<a href="https://agentmods.dev/instructions/huytieu/cog-second-brain/claude-md"><img src="https://agentmods.dev/badge/instructions/huytieu/cog-second-brain/claude-md.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.04002 | $0.04002 |
| Opus 5 | $0.02001 | $0.02001 |
| Sonnet 5 | $0.00800 | $0.00800 |
| Haiku 4.5 | $0.00400 | $0.00400 |
Grade A, and why
COG-second-brain CLAUDE.md scanned grade A with 1 finding 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 7d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- **Verification means observing the artifact**: curl the URL, screenshot the page, re-fetch the issue, diff the file. Never re-read a worker's own summary of it. Mandatory for external mutations; see § Skill Post-Condit How it starts
The opening of the file, as written. The whole thing — 250 lines — stays where its author put it; the contents beside it link to each section on GitHub.
COG Second Brain — Framework Instructions
Opt-in verification harness:
WORKFLOW.md· Universal surface:AGENTS.md
Response Style (ALWAYS APPLY, every agent, every deliverable)
Optimize for information gain, not apparent completeness. The failure mode is framework slop: ordinary reasoning dressed as a consulting memo. Full pattern list: .claude/skills/no-ai-slop/SKILL.md § Structural slop.
- Start with the answer or strongest finding; no introduction announcing how you will answer.
- Never invent named frameworks, gates, layers, pillars, lenses, or numbered taxonomies unless they exist in the source material or the categorization materially simplifies a complex subject.
- No sections for 1-2 paragraphs; default to continuous prose with occasional descriptive headings.
- Headings identify subject matter ("Authentication"), never rhetorical function. Banned: "What this is not", "Why this matters", "The key insight", "The real opportunity", "The bottom line", "The deeper point", "The uncomfortable truth".
- No straw-man contrasts ("It's not X, it's Y", "This isn't about X", "While it may seem...", "Unlike...") unless X is a position someone relevant actually holds.
- Space proportional to importance and evidence; each paragraph must add evidence, mechanism, example, implication, counterexample, or decision.
- Compose as finding → evidence → reasoning → decision, not principle → framework → exposition → takeaway.
- Prefer concrete nouns over abstract labels. Stop when the useful information is exhausted.
Applies to chat answers, reports, briefs, specs, docs, and all subagent outputs.
Verification Harness (opt-in, off by default)
COG ships a V-model verification harness: decompose left (spec then plan), build at the apex, verify right with evidence traced to criterion IDs (AC-n). It does not run unless you ask for it. Ordinary work (notes, briefs, research, drafts, edits) takes no checkpoints, no lane classification, and no evidence ledger.
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.
- 7d ago First seen · 250 lines · 4,002 tokens per session scan A 9ff2da4c033f
COG-second-brain CLAUDE.md is an instructions file published in the GitHub repository huytieu/COG-second-brain (1,173 stars, last pushed 12d ago), licensed MIT. It adds 4,002 tokens to every session, about $0.0200 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other instructions, from other repositories
multiagent-template copilot-instructions.md
Instructions for Neftedollar/multiagent-template, covering workspace structure, how to work in this repo, multi-agent pipeline, orchestrator role and escalate to human only for.
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.