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/metaspartan/cybara/bear-notesnpx skills add metaspartan/cybara --skill bear-notesgit clone --depth 1 https://github.com/metaspartan/cybaraWhat 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.00663 |
| Opus 5 | $0.00009 | $0.00331 |
| Sonnet 5 | $0.00003 | $0.00133 |
| Haiku 4.5 | $0.00002 | $0.00066 |
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
94% identical to bear-notes — 30 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 — 80 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 · 80 lines · 17 tokens per session scan A 7d7319906032
bear-notes is a skill published in the GitHub repository metaspartan/cybara (23 stars, last pushed 4d ago), licensed MIT. It adds 17 tokens to every session and 663 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 94% identical to bear-notes, differing in 30 lines, and is treated as a copy.
Other skills, from other repositories
gws-calendar
Google Calendar: Manage calendars and events.
discord
Use when you need to control Discord from Otto via the discord tool: send messages, react, post or upload stickers, upload emojis, run polls, manage threads/pins/search, create/edit/delete channels and categories, fetch permissions or member/role/channel info, set bot presence/activity, or handle moderation actions in…
tmux
Remote-control tmux sessions for interactive CLIs by sending keystrokes, capturing pane output, and managing terminal multiplexer windows. Enables parallel coding-agent orchestration, background process management, and REPL interaction via sockets. Use when the agent needs to launch, monitor, or coordinate…
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.
apple-reminders
Manage Apple Reminders via the remindctl CLI on macOS (list, add, edit, complete, delete). Supports lists, date filters, and JSON/plain output. Use when the user asks about reminders, todos, tasks, to-do lists, "remind me", scheduling tasks, checking what is due today, completing or deleting reminders, or managing…
apple-notes
Manage Apple Notes via the memo CLI on macOS (create, view, edit, delete, search, move, and export notes). Use when a user asks Otto to add a note, list notes, search notes, or manage note folders.