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/geezerrrr/motive/bear-notesnpx skills add geezerrrr/motive --skill bear-notesgit clone --depth 1 https://github.com/geezerrrr/motiveWrote 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/geezerrrr/motive/bear-notes)<a href="https://agentmods.dev/skills/geezerrrr/motive/bear-notes"><img src="https://agentmods.dev/badge/skills/geezerrrr/motive/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.00703 |
| Opus 5 | $0.00009 | $0.00351 |
| Sonnet 5 | $0.00003 | $0.00141 |
| 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 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.
This is a copy
100% identical to bear-notes — 0 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.
- 4d ago First seen · 108 lines · 17 tokens per session scan A 956251b2fca2
bear-notes is a skill published in the GitHub repository geezerrrr/motive (117 stars, last pushed 6mo ago), licensed MIT. It adds 17 tokens to every session and 703 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to bear-notes, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
engram-rebuild
이미 설치된 engram 환경에 개발 변경을 적용한다. dev-rebuild.ps1 로 충분한지 INSTALL.ps1 전체를 돌려야 하는지 판단하고 실행한다. 트리거 — 재빌드, 리빌드, dev 변경 적용, 설치본에 반영, overlay 재시작, exe 갱신, "고친 거 확인하려면 뭐 돌려야 해", rebuild, redeploy.
orchestrate
Run Engram's Orchestrator-Planner-Coder-Servant workflow for multi-step development, refactors, or research-plus-implementation tasks that need an acceptance contract and independent verification. Trigger for "orchestrate", delegation requests, planning then implementation, or complex multi-step development. Do not…
engram-new-session
Skill "engram-new-session" from JJHbrams/Project-AMBER, covering engram 말풍선 — 새 세션 시작, 실행 절차 and 규칙.
dead-code-cleanup
Identifies and removes dead/orphaned code, tests, and Storybook stories — including trivial tests that check only obvious behavior or rare edge cases with no real value. Always validates that code is truly unused before deleting anything. Trigger on: "remove dead code", "clean up unused files", "delete orphaned…
issue-maintenance
Periodic and on-demand maintenance pass over a repo's open GitHub issue backlog. Re-labels miscategorized or unlabeled issues (bug/enhancement/question/invalid/duplicate) and bug lifecycle labels (needs-repro/needs-info) following the same decision logic as Anthropic's own dogfooded triage-issue command; re-scores…
visual-crawl
Crawls the running app at randomized breakpoints, screenshots visual issues, checks design token consistency, and tests interactive elements. Each run covers different ground by design. Trigger on: "visual QA", "audit the app visually", "screenshot all the pages", "check for visual regressions", "crawl the site for…