A workspace command for showing or managing notes connected to a project workspace. A workspace is a separate working area for a repository, and the notes can include references and metadata.

Use it to display a workspace's README, metadata, referenced files, file details, or open its notes directory in MarkText.

It gathers workspace notes and related files from the configured notes location instead of making you find them yourself.

notes — Command by mdsakalu

Install

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.

agentmods

npx agentmods add commands/mdsakalu/agent-plugins/notes

Clone the repo

git clone --depth 1 https://github.com/mdsakalu/agent-plugins

Per session 5 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 527 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

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.00005	$0.00527
Opus 5	$0.00003	$0.00264
Sonnet 5	$0.00001	$0.00105
Haiku 4.5	$0.00001	$0.00053

Measured yesterday against content hash dfb0e15cc253, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

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 yesterday.

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.

workspace/commands/notes.md · 46 lines

What it actually says

Show or manage workspace notes.

Resolve the metarepo path by reading ~/.claude/workspace-config.json and expanding ~ to $HOME.

The user's request: $ARGUMENTS

Steps

Read ~/.claude/workspace-config.json to get the metarepo path. Expand ~ to $HOME.
Determine which workspace's notes to show:
- If <repo>/<workspace> specified, use it
- If just <workspace>, search across repos
- If no argument, infer from cwd (match */repos/<repo>/<workspace>*)
- If unable to determine, list workspaces and ask
Locate the notes directory at <metarepo>/notes/<repo>/<workspace>/.
If the notes directory exists:
- Read and display README.md in full
- Read and display workspace.json (references, metadata)
- List all other files in the notes directory with sizes and modification dates
- If the user asked about a specific file, read and display it
Open the notes directory in MarkText:
```
~/Applications/marktext.app/Contents/MacOS/marktext <notes-dir>/
```
Run this in the background (append & and disown) so it doesn't block.
If the notes directory does not exist:
- Inform the user
- Offer to create it with README.md from ${CLAUDE_PLUGIN_ROOT}/templates/workspace-readme.md
If the user asks to edit notes:
- Edit the requested file using the Edit tool
- Or create a new file in the notes directory
Notes are also accessible via the .notes symlink inside the workspace directory.

Important

Always resolve metarepo from ~/.claude/workspace-config.json, never hardcode paths.
Notes are git-tracked at <metarepo>/notes/<repo>/<workspace>/.
Notes persist even after workspace retirement — they are the historical record.
The .notes symlink in each workspace points to the notes directory.
workspace.json in the notes directory is the source of truth for metadata and references.

Changes

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.

yesterday First seen · 46 lines · 5 tokens per session scan A dfb0e15cc253

Subscribe to this mod's changes

notes is a command published in the GitHub repository mdsakalu/agent-plugins (4 stars, last pushed 2mo ago), licensed MIT. It adds 5 tokens to every session and 527 once invoked, about $0.0000 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.

Productivity Writing and docs

notes

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

What it actually says

Steps

Important

What this file has done since we first saw it

Other commands, from other repositories

checklist

clarify

specify

analyze

converge

implement