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 rules/neryams/workspace-docs-mcp/journalgit clone --depth 1 https://github.com/neryams/workspace-docs-mcpWhat 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.00382 | $0.00382 |
| Opus 5 | $0.00191 | $0.00191 |
| Sonnet 5 | $0.00076 | $0.00076 |
| Haiku 4.5 | $0.00038 | $0.00038 |
Grade A, and why
journal 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.
What it actually says
Team journal (journal-rag MCP)
This workspace has a journal MCP server named journal (configured in .cursor/mcp.json). It searches and writes markdown journal files under docs/journal/ (or paths in journal-rag.config.json).
Valid tool names only:
search_journal— semantic + keyword search (param:query, optionalk)list_entries— browse all entries (optionalfilter)get_entry— read one file by path (param:path)write_entry— create a new entry (title,content)search_regex— exact/symbol lookup (param:pattern, optionalk)
When to use the journal
- Before starting a non-trivial task:
search_journalfor past decisions, failed approaches, and preferences. - During work: if you hit a reusable insight, gotcha, or architectural decision, note it for a journal entry at the end.
- After completing meaningful work:
write_entryto capture what worked, what failed, and why — so future sessions benefit. - Use
search_regexwhen you need exact identifiers, file paths, or symbols that semantic search might miss.
Writing entries
Use write_entry with full markdown content starting with # Title. Good things to capture:
- Technical insights and debugging lessons
- Architectural decisions and their rationale
- User preferences and communication patterns
- Approaches that failed and why (avoid repeating them)
Keep entries concise and factual. The journal is team-visible markdown in git, not a private feelings log.
Scope discipline
Do not fix unrelated issues you notice during a task — document them in a journal entry instead (or mention them to the user).
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 · 36 lines · 382 tokens per session scan A 4ff5779bc08e
journal is a cursor rule published in the GitHub repository neryams/workspace-docs-mcp (0 stars, last pushed 13d ago), licensed MIT. It adds 382 tokens to every session, about $0.0019 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 cursor rules, from other repositories
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
typescript
Changes to these high-fan-out internals can affect every message, delta, element, or rerun. Keep work in them minimal, and benchmark changes with representative stress-test apps.
coolify-ai-docs
Master reference to all Coolify AI documentation in .ai/ directory.
python_lib
Tips and guidelines specific to the development of the Streamlit Python library, not applicable to scripts and e2e tests.
specs
This directory contains product and tech specs for Streamlit features.