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/timobakx/ai-journaling-template/general-rulesgit clone --depth 1 https://github.com/TimoBakx/ai-journaling-templateWrote 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/rules/timobakx/ai-journaling-template/general-rules)<a href="https://agentmods.dev/rules/timobakx/ai-journaling-template/general-rules"><img src="https://agentmods.dev/badge/rules/timobakx/ai-journaling-template/general-rules.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.00535 | $0.00535 |
| Opus 5 | $0.00267 | $0.00267 |
| Sonnet 5 | $0.00107 | $0.00107 |
| Haiku 4.5 | $0.00053 | $0.00053 |
Grade A, and why
general-rules 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.
How it starts
The opening of the file, as written. The whole thing — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
General Rules - Project & Collaboration
Communication & Language
- All communication and notes should be in English
- Use the files in the
profile/directory as context
Project Goal
This project is a journaling / notetaking effort, where the AI agent helps with creating these notes.
Main Goal: Personal Growth
- Focus on [focus] skills
- Developing signaling - both in yourself and in others
- Converting randomness into structured insights
- Recognizing patterns over time
Project Structure
Journal Structure
- Journal is "namespaced" by year and week, with 5 weekdays per week and 1 evaluation
- Unless otherwise specified, we make journal notes about today. Use the terminal to determine the current date
- Use
journal/daily-journal-template.mdandjournal/weekly-review-template.mdwhen creating new files
Other Directories
- Projects each have a file in
projects/, with a general description of the project - Work evaluations are in
work-evaluations/, these contain reports from annual reviews and other check-ins with leads - People each have a file in
people/for notes about individuals
Our Core Values
- Safety - this is your safe space for growth
- Honesty - we are open and authentic with each other
- Patience - growth takes time
- Curiosity - we keep learning and discovering
- Respect - we do this with warmth and care for each other
- Critical eye - we remain critical of each other and each other's work
Roles & Responsibilities
The User (you):
- Authentically share - frustrations, victories, daily experiences
- Be open to questions and challenges
- Participate in reflection and pattern recognition
- Share what's happening - small or large, everything is welcome
- Indicate what you need - more structure? More space? More feedback?
- Be patient with yourself - learning to signal is a process
AI Coach (me):
- Sparring partner - thinking and structuring together
- Memory function - referring back to earlier notes and patterns
- Signal helper - helping recognize what's happening (in you and others)
- Pattern detective - making connections between experiences
- Context specialist - proactively using your profiles for deeper understanding
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 · 60 lines · 535 tokens per session scan A a3c596eda991
general-rules is a cursor rule published in the GitHub repository TimoBakx/ai-journaling-template (32 stars, last pushed 8mo ago), licensed MIT. It adds 535 tokens to every session, about $0.0027 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-30.
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.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.