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/aleksbuss/orchestra/bear-notesnpx skills add aleksbuss/orchestra --skill bear-notesgit clone --depth 1 https://github.com/aleksbuss/orchestraWrote 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/aleksbuss/orchestra/bear-notes)<a href="https://agentmods.dev/skills/aleksbuss/orchestra/bear-notes"><img src="https://agentmods.dev/badge/skills/aleksbuss/orchestra/bear-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.00017 | $0.00702 |
| Opus 5 | $0.00009 | $0.00351 |
| Sonnet 5 | $0.00003 | $0.00140 |
| Haiku 4.5 | $0.00002 | $0.00070 |
Grade A, and why
bear-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 3d 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.
This is a copy
97% identical to bear-notes — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bear Notes
Use grizzly to create, read, and manage notes in Bear on macOS.
Requirements
- Bear app installed and running
- For some operations (add-text, tags, open-note --selected), a Bear app token (stored in
~/.config/grizzly/token)
Getting a Bear Token
For operations that require a token (add-text, tags, open-note --selected), you need an authentication token:
- Open Bear → Help → API Token → Copy Token
- Save it:
echo "YOUR_TOKEN" > ~/.config/grizzly/token
Common Commands
Create a note
echo "Note content here" | grizzly create --title "My Note" --tag work
grizzly create --title "Quick Note" --tag inbox < /dev/null
Open/read a note by ID
grizzly open-note --id "NOTE_ID" --enable-callback --json
Append text to a note
echo "Additional content" | grizzly add-text --id "NOTE_ID" --mode append --token-file ~/.config/grizzly/token
List all tags
grizzly tags --enable-callback --json --token-file ~/.config/grizzly/token
Search notes (via open-tag)
grizzly open-tag --name "work" --enable-callback --json
Options
Common flags:
--dry-run— Preview the URL without executing--print-url— Show the x-callback-url--enable-callback— Wait for Bear's response (needed for reading data)--json— Output as JSON (when using callbacks)--token-file PATH— Path to Bear API token file
Configuration
Grizzly reads config from (in priority order):
- CLI flags
- Environment variables (
GRIZZLY_TOKEN_FILE,GRIZZLY_CALLBACK_URL,GRIZZLY_TIMEOUT) .grizzly.tomlin current directory~/.config/grizzly/config.toml
Example ~/.config/grizzly/config.toml:
token_file = "~/.config/grizzly/token"
callback_url = "http://127.0.0.1:42123/success"
timeout = "5s"
Notes
- Bear must be running for commands to work
- Note IDs are Bear's internal identifiers (visible in note info or via callbacks)
- Use
--enable-callbackwhen you need to read data back from Bear - Some operations require a valid token (add-text, tags, open-note --selected)
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.
- 3d ago First seen · 108 lines · 17 tokens per session scan A 3454de572c8a
bear-notes is a skill published in the GitHub repository aleksbuss/orchestra (2 stars, last pushed 6d ago), licensed MIT. It adds 17 tokens to every session and 702 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 97% identical to bear-notes, differing in 2 lines, and is treated as a copy.
Other skills, from other repositories
comm-agent-skill
Communication specialist for the OpenClaw multi-agent system. Use this skill when the task involves: drafting or sending emails, posting to Discord or other chat platforms, scheduling calendar events, sending notifications, or any outbound communication on behalf of the user. Always drafts before sending and requires…
configure-notifications
Configure notification integrations (Telegram, Discord, Slack) via natural language.
ai-slop-cleaner
Clean AI-generated code slop with a regression-safe, deletion-first workflow and optional reviewer-only mode.
prep
Session wrap-up. Update memories, check plans, review git state, check inbox, flag loose ends. Use before closing a session or compacting context.
inbox_check
Check aimail inbox status across AIPass branches.
content-calibrator
DNA 表现评估引擎——消费 published-track 的发布与互动数据,按量触发(每平台每 DNA 累积 ≥5 条成熟记录)评估 DNA 好坏,趋势优先(账号基线归一化 + 走向判定),产出评估报告与优化建议,经用户确认后回写 DNA。平台特有的归因方法由各平台专家包 review workflow 提供。发布记录与数据采集由 published-track 统一管理。.