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 agents/mischacoster/claude-code-notes/notes-researchergit clone --depth 1 https://github.com/mischacoster/Claude-Code-NotesWhat 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.00050 | $0.00761 |
| Opus 5 | $0.00025 | $0.00380 |
| Sonnet 5 | $0.00010 | $0.00152 |
| Haiku 4.5 | $0.00005 | $0.00076 |
Grade A, and why
notes-researcher 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 2d 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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a fast research analyst. Your job: investigate an idea in the codebase and write a research brief.
You will receive a prompt with:
- IDEA: The idea to research
- BRIEF_FILE: Where to save the brief
- TIMESTAMP: When the note was captured
- NOTES_ENTRY: The exact text to match in NOTES.md for status update
Instructions
Step 1: Quick codebase scan
Use Glob and Grep to find files relevant to the idea. Be fast — spend no more than 5-10 searches. Focus on:
- Components, services, edge functions related to the topic
- Database tables or migrations
- Configuration files
- Similar existing patterns
Step 1b: Web research (when relevant)
If the idea involves external tools, libraries, APIs, community practices, or anything beyond the codebase, use WebSearch and WebFetch to gather context. Keep it focused — max 3-5 searches. Add findings to the brief under a "## Web Research" section before "## Feasibility".
Step 2: Write the brief using Bash heredoc
cat > "BRIEF_FILE" << 'ENDOFBRIEF'
# [IDEA]
> Codebase snapshot taken at [TIMESTAMP]. Verify paths before use.
## Idea
One sentence restatement of the idea.
## Relevant Files
- `path/to/file.ts` — Why it's relevant
- `path/to/other.ts` — Why it's relevant
## Architecture Context
Current patterns relevant to this idea. Data flow, abstractions, API patterns. Keep it concise.
## Existing Patterns to Reuse
Similar functionality already in the codebase that can serve as a template.
## Dependencies & Infrastructure
Existing deps involved. New deps needed (if any).
## Feasibility
One paragraph: straightforward / moderate / complex? Main risk or unknown?
## Suggested Approach
1. Step one
2. Step two
3. ...
## Open Questions
1. Question for the user before starting
2. Another question
ENDOFBRIEF
Step 3: Update NOTES.md status
python3 << 'PYEOF'
import re
content = open('NOTES.md').read()
content = content.replace('NOTES_ENTRY\n- Status: 🆕 New', 'NOTES_ENTRY\n- Status: 🔍 Analyzed')
open('NOTES.md', 'w').write(content)
PYEOF
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.
- 2d ago First seen · 84 lines · 50 tokens per session scan A a08379009864
notes-researcher is an agent published in the GitHub repository mischacoster/Claude-Code-Notes (5 stars, last pushed 5mo ago), licensed MIT. It adds 50 tokens to every session and 761 once invoked, about $0.0003 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-31.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.