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.
git clone --depth 1 https://github.com/TimoBakx/ai-journaling-template-nlWrote 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-nl/journaling-regels)<a href="https://agentmods.dev/rules/timobakx/ai-journaling-template-nl/journaling-regels"><img src="https://agentmods.dev/badge/rules/timobakx/ai-journaling-template-nl/journaling-regels/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/rules/timobakx/ai-journaling-template-nl/journaling-regels"><img src="https://agentmods.dev/badge/rules/timobakx/ai-journaling-template-nl/journaling-regels.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00772 | $0.00772 |
| Opus 5 | $0.00386 | $0.00386 |
| Sonnet 5 | $0.00154 | $0.00154 |
| Haiku 4.5 | $0.00077 | $0.00077 |
Grade A, and why
journaling-regels 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 9d 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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
📝 journaling Regels - Dagelijkse Werkwijze
Doel Van Dagelijks Journallen
Dagelijkse journaling is beknopt en specifiek - wat gebeurde er, korte observaties, concrete feiten. Dit vormt het fundament voor diepere analyse tijdens evaluaties.
Dagelijkse Routine
- Project lang open houden - deze kennisbank blijft actief
- Dagelijkse chat sessies - samen journal bestand vullen
- Door de dag heen - verwerking en doorvragen wanneer nodig
- Einde dag - samenvatten en patronen checken
Template Structuur
Dagelijkse Template Bestand
Gebruik journal/daily-journal-template.md bij het maken van nieuwe dagelijkse journal bestanden.
Structuur Elementen
🎯 Gepland
- Simpele planning met emoji
- Geen uitgebreide energie/gevoel checks
- Taken kunnen project links bevatten:
- [ ] ([Project Naam](../../projecten/project.md)) taak
📝 Dagverloop - Gebeurtenissen
- Beknopte feiten zonder gedwongen substructuur of tijdstippen
- Geen tijdstippen - veel mensen switchen veel tussen projecten
- Directe project links in headers:
### ([Project](/link)) Activiteit - Lopende tekst i.p.v. bullet point structuren waar mogelijk
- Geen sub-sub kopjes die vetgedrukt zijn, maak er een lopend verhaal van.
- Wat gebeurde er echt? Feitelijke observaties per activiteit
🔍 Einde Dag - Reflectie
- Minimale reflectie sectie, ruimte voor samen invullen
- Zie
reflectie-regels.mdcvoor uitgebreide reflectie methodiek
📋 Taken voor Later
- Belangrijke taken die niet vandaag gebeuren
Template Design Principes
- Clean en praktisch - geen quotes, footers of overtollige structuur
- Directe project links in headers:
### ([Project](/link)) Activiteit - Inline cross-linking - geen aparte "Tags & Projecten" secties
- Echte subheaders i.p.v. dikgedrukte "nepheaders"
- Lopende tekst i.p.v. bullet point structuren waar mogelijk
Bestandsnaming & Locatie
- Templates in
/journal/- logischer dan aparte map - Dagelijkse bestanden:
[DAGNUMMER]-[dag]-[DATUM].md(bijv.1-maandag-2025-10-27.md) - Journal is "namespaced" door jaar en week:
journal/[JAAR]/[WEEKNUMMER]/
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.
- 9d ago First seen · 71 lines · 772 tokens per session scan A 87a72bd270c3
journaling-regels is a cursor rule published in the GitHub repository TimoBakx/ai-journaling-template-nl (10 stars, last pushed 9mo ago), licensed MIT. It adds 772 tokens to every session, about $0.0039 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
reflection-basic
Basic reflection format for Level 2 Simple Enhancement tasks.
cursor-fable-rules
Fable coding lifecycle discipline and situational awareness for Cursor.
git-workflow
Rules for git operations, commit strategy, and GitHub CLI usage.
feedback-enhanced
Rules for an interactive feedback system that lets users and an AI agent discuss complex development work in real time. It includes guidance for recording decisions, tracking progress and handling detailed inputs such as code and diagrams.
122-swift-development
122: Swift development workflow including TDD, refactoring, and performance optimization.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.