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.
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 huytieu/COG-second-brain --skill meeting-transcriptgit 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/skills/huytieu/cog-second-brain/meeting-transcript)<a href="https://agentmods.dev/skills/huytieu/cog-second-brain/meeting-transcript"><img src="https://agentmods.dev/badge/skills/huytieu/cog-second-brain/meeting-transcript.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.00023 | $0.00111 |
| Opus 5 | $0.00012 | $0.00056 |
| Sonnet 5 | $0.00005 | $0.00022 |
| Haiku 4.5 | $0.00002 | $0.00011 |
Grade A, and why
meeting-transcript 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 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.
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.
What it actually says
Read .claude/skills/meeting-transcript/SKILL.md and execute it exactly as written — that file is the authoritative
playbook. Then follow .agents/rules/cog.md.
Antigravity substitution: where the playbook delegates to a .claude/agents/<name>
worker, invoke .agents/agents/<name>.md via invoke_subagent instead.
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 · 11 lines · 23 tokens per session scan A 52a186d373c4
meeting-transcript is a skill published in the GitHub repository huytieu/COG-second-brain (1,173 stars, last pushed 12d ago), licensed MIT. It adds 23 tokens to every session and 111 once invoked, about $0.0001 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-30.
Other skills, from other repositories
things-mac
Manage Things 3 via the things CLI on macOS (add/update projects+todos via URL scheme; read/search/list from the local Things database). Use when a user asks Otto to add a task to Things, list inbox/today/upcoming, search tasks, or inspect projects/areas/tags.
10-todo
Split the user prompt into independent todos and run one executor agent per todo in parallel, then report a minimal table. Use when the user says "todo" or asks to fan out a multi-part request into parallel implementations.
outlook-calendar
A skill for managing Microsoft Outlook and Microsoft 365 calendar events through a connected account.
hatch3r-cleanup
Repo-state cleanup pass — inventories accumulated hatch3r working state (plan files, workspace dirs, review telemetry, findings ledgers, learnings, handoffs, board staleness), asks once with per-category counts and estimated reclaim, dispatches each owned surface to its owning skill or CLI path, and prunes only the…
Automate Lark and Feishu docs, sheets, mail, calendar, meetings, and chat tasks from agents with Lark CLI
Operate Lark and Feishu work objects from one agent-ready CLI instead of stitching together separate APIs and browser flows.
run-feedback
Use when a run of a workflow, skill, command, or test produced errors or friction worth keeping, or when executing the end-of-run Retro Global Protocol — collect findings into the feedback inbox, triage them (defect / work-item / noise), and file defects into the known-issues ledger or work-items into the backlog. NOT…