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 agentmods add skills/human-agent-society/coral/create-notesnpx skills add Human-Agent-Society/CORAL --skill create-notesgit clone --depth 1 https://github.com/Human-Agent-Society/CORALWrote 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/human-agent-society/coral/create-notes)<a href="https://agentmods.dev/skills/human-agent-society/coral/create-notes"><img src="https://agentmods.dev/badge/skills/human-agent-society/coral/create-notes.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 | $0.00217 | $0.05499 |
| Opus 5 | $0.00109 | $0.02750 |
| Sonnet 5 | $0.00043 | $0.01100 |
| Haiku 4.5 | $0.00022 | $0.00550 |
Grade A, and why
create-notes 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 5d 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 — 374 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Notes
A good note answers three questions a future agent will actually ask:
- What did you do, and what happened? (concrete numbers, not adjectives)
- Why did it happen that way? (the mechanism, not just the result)
- What should I do — or not do — given this? (ordered next steps + things you tried that failed)
A bad note is a wall of headings with empty bodies, or a final-design pitch with no record of the alternatives you rejected. The bad pattern shows up enough that this skill exists to prevent it.
When to Use
Each heartbeat that produces a note corresponds to one variant. The skill is one document, but you only need the variant your current trigger asks for.
| Triggered by | Variant | File location |
|---|---|---|
reflect heartbeat after each eval |
Experiment note (Variant A) | notes/experiments/eval-<N>-<slug>.md |
pivot plateau detection |
Focus note (Variant C) | notes/focus/focus-<topic>.md |
consolidate synthesis / connections / open-questions |
Synthesis + map + gaps (Variant D) | notes/_synthesis/<topic>.md, notes/_connections.md, notes/_open-questions.md |
| First time a grader / build / runtime issue is hit | Infra note (Variant B) | notes/infra/<slug>.md (or notes/<slug>.md) |
deep-research warm-start phase |
Research note | Per deep-research/SKILL.md (not duplicated here) |
If you are about to Write any file under notes/, stop and use this skill first — even if the prompt did not say "write a note."
Notes Directory Layout
The directory structure is owned by organize-files. Do not invent new top-level subdirectories; place new content in the right existing one:
notes/
├── index.md ← table of contents; you update this for any new note
├── raw/ ← immutable sources (do not write here directly)
├── research/ ← deep-research findings (link back to raw/)
├── experiments/ ← per-eval reflections, written by the reflect heartbeat
├── infra/ ← grader / build / runtime issues + workarounds (recommended)
├── focus/ ← per-agent focus declarations (owned by the pivot heartbeat)
├── migrations/ ← island-arrival notes (written by the framework)
├── _synthesis/ ← owned by consolidate; do not write here unless consolidating
├── _connections.md ← owned by consolidate
├── _open-questions.md ← owned by consolidate
└── _organization-log.md ← append-only audit log; only organize-files writes here
What ships with it
5 files 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.
- 5d ago First seen · 374 lines · 217 tokens per session scan A d7dfa394e941
create-notes is a skill published in the GitHub repository Human-Agent-Society/CORAL (951 stars, last pushed 5d ago), licensed Apache-2.0. It adds 217 tokens to every session and 5,499 once invoked, about $0.0011 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
handoff
Write a compact, decision-ready handoff so the next session (or the user) can continue without reconstructing the current one. Use when the session is ending, context is running low, the user asks for a handoff / "pass the baton" / "hand off", or a long-running operation needs a durable state checkpoint.
autocontext-consumer
Use when an agent needs to USE knowledge Autocontext already produced - find which scenarios have knowledge, read the playbook and lessons for one, understand the on-disk file and folder layout, and move knowledge between checkouts. Host-agnostic; requires only the autoctx CLI and the filesystem.
incident-alert-tickets
Read and record root causes in the Linear incident-alert knowledge base. Use before and after investigating a named Datadog monitor, incident.io alert or incident, or on-call page to find or record root causes.
linear-context-handover
Use Linear as the org's memory: reconstruct a feature's history before touching it, and leave the reasoning behind finished work in the ticket description so the next agent inherits it. Use when starting work on an existing feature, when planning multi-PR work, and always when wrapping up — "what happened to this…
learn-from-history
审计近期对话历史，提炼重复失败、成功模式、稳定规则和 skill 改进。用户要求总结历史对话、 回顾近期 agent 表现、从历史中学习或寻找可自动化改进时使用。.
omega-memory
Persistent memory for AI coding agents. Teaches agents how to use OMEGA's MCP tools for storing decisions, querying context, coordinating multi-agent workflows, and resuming tasks across sessions.