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/aden-hive/hive/note-takingnpx skills add aden-hive/hive --skill note-takinggit clone --depth 1 https://github.com/aden-hive/hiveWrote 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/aden-hive/hive/note-taking)<a href="https://agentmods.dev/skills/aden-hive/hive/note-taking"><img src="https://agentmods.dev/badge/skills/aden-hive/hive/note-taking.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.00030 | $0.00280 |
| Opus 5 | $0.00015 | $0.00140 |
| Sonnet 5 | $0.00006 | $0.00056 |
| Haiku 4.5 | $0.00003 | $0.00028 |
Grade A, and why
hive.note-taking 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 4d 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
Operational Protocol: Structured Note-Taking
Maintain free-form working notes in shared buffer key _working_notes for data that you need to remember but that isn't captured by the colony task queue.
Do not duplicate the queue in here. Per-task goal, ordered steps, and SOP gates live in progress.db — use hive.colony-progress-tracker for those. These notes are for things the DB schema doesn't cover.
Update at these checkpoints:
- After receiving new information that changes how you plan to approach the current step
- Before any tool call that will produce substantial output you'll need to reference later
- When you make a non-obvious decision whose why would be lost if the tool call history gets pruned
Structure:
Key Decisions — decisions made and WHY
Working Data — intermediate results, extracted values (URLs, IDs, key snippets — not full pages)
Open Questions — uncertainties you plan to verify
Blockers — anything preventing progress that isn't already captured in tasks.last_error
Update incrementally — do not rewrite from scratch each time.
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.
- 4d ago First seen · 30 lines · 30 tokens per session scan A 476f7e41ac1a
hive.note-taking is a skill published in the GitHub repository aden-hive/hive (11,013 stars, last pushed 13d ago), licensed Apache-2.0. It adds 30 tokens to every session and 280 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-30.
Other skills, from other repositories
product-help
Use this skill when the user asks about my own features, configuration, or usage — installation, skills, Web UI, CLI, API config, memory, sessions, encryption, white-label, publishing, pricing, troubleshooting, or restarting the server. Do NOT trigger for general coding tasks unrelated to me.
team-builder-packaging
Use when generating or auditing a multi-role agent team package with orchestrator, PM Soul, Memory Curator, Policy Gate, workers, eval, QA, handoffs, and runtime adapters.
enhance-claude-memory
Use when improving CLAUDE.md or AGENTS.md project memory files.
persist-memory
Persist information to long-term memory at /.clacky/memories/. Use when the user asks you to remember/note something, or when reviewing a finished conversation for facts worth keeping. Handles file naming, topic merging, frontmatter, and size limits.
learn
Research any topic online and create learning guides. Use when user asks to 'learn about', 'research topic', 'create learning guide', 'build knowledge base', or 'study subject'.
recall-memory
Recall relevant long-term memories on demand. Given a topic or question, judges relevance from pre-loaded metadata, loads only relevant files, and returns a concise summary to the main agent.