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 skills/ai-swiss/base/journalnpx skills add ai-swiss/base --skill journalgit clone --depth 1 https://github.com/ai-swiss/baseWrote 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/skills/ai-swiss/base/journal)<a href="https://agentmods.dev/skills/ai-swiss/base/journal"><img src="https://agentmods.dev/badge/skills/ai-swiss/base/journal.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.00029 | $0.00877 |
| Opus 5 | $0.00015 | $0.00439 |
| Sonnet 5 | $0.00006 | $0.00175 |
| Haiku 4.5 | $0.00003 | $0.00088 |
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 4d 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 — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Journal de session
Le journal est la mémoire externe de l'agent d'une conversation à l'autre. Sans lui, chaque session repart de zéro; avec lui, l'agent reprend là où il s'était arrêté.
Quand écrire une entrée
À la fin de chaque process (chaque workflow invocable), l'agent écrit une entrée de journal. C'est l'ultime étape de tout process.
Où écrire
Emplacement: .ai/journal/YYYY-MM-DD_description.md
Exemples:
.ai/journal/2026-04-20_configuration.md.ai/journal/2026-04-20_devis-favre.md.ai/journal/2026-04-21_devis-mueller.md
Si le dossier .ai/journal/ n'existe pas encore, le créer avant la première entrée.
Format d'une entrée
# Session : [titre descriptif]
Date : YYYY-MM-DD
Agent : [nom-agent]
Skill : /[nom-du-process]
## Ce qui a été fait
- [action concrète 1]
- [action concrète 2]
## Fichiers créés ou modifiés
- chemin/vers/fichier1.md
- chemin/vers/fichier2.json
## Décisions
- [DECISION: choix | raison]
## À suivre
- [A VALIDER: élément en attente de confirmation]
- [A COMPLETER: information manquante]
Règles
- Sections conditionnelles. N'inclure une section que si elle a du contenu. Jamais de section «Décisions» vide.
- Concis. Le journal est un aide-mémoire, pas un rapport. À session courte, entrée courte.
- Marqueurs dans le journal. Utiliser les marqueurs
[DECISION],[A VALIDER],[A COMPLETER]: le journal se prête ainsi à la recherche au même titre que les documents générés.
Reprise de session
Quand l'utilisateur revient après une interruption («on en était où?», «bonjour», ou simplement en reprenant le travail), l'agent:
- Lit les entrées récentes dans
.ai/journal/(les 2-3 dernières) - Résume l'état actuel: ce qui a été fait, ce qui reste à faire
- Propose la suite: traiter un
[A VALIDER], compléter un[A COMPLETER], ou commencer un nouveau process
Cette reprise vaut aussi en cours de session: si tu ne peux plus citer le chemin du process actif (après un résumé, ou loin dans une longue conversation), rouvre l'AGENT.md et le SKILL.md actifs plutôt que de te fier au contexte courant.
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.
- 4d ago First seen · 89 lines · 29 tokens per session scan A 193b28824aab
journal is a skill published in the GitHub repository ai-swiss/base (42 stars, last pushed today), licensed Apache-2.0. It adds 29 tokens to every session and 877 once invoked, about $0.0001 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 skills, from other repositories
achieving-cmmc-level-2-compliance
Prepare a defense-contractor environment for CMMC Level 2 certification: scope CUI and FCI, implement the 110 NIST SP 800-171 Rev 2 security requirements across 14 families, compute the SPRS score with the DoD Assessment Methodology, manage a compliant POA&M, and ready the organization for a C3PAO assessment. Use when…
escalation-governance
Assess whether to escalate models. Use when evaluating reasoning depth.
agt-policy-authoring
Create and validate a minimal AGT Copilot CLI policy tailored to the repository being inspected.
wallet-cli
Operate the TypeScript TRON wallet CLI for accounts, transfers, staking, governance, contracts, signing, chain queries, and password input with wallet-cli 4.12.0. Refuse wallet passwords in argv and require the supported stdin channel. For Java REPL requests, refuse that entry and offer the TypeScript one-shot CLI…
TRX Staking & SR Voting
Stake TRX, vote for Super Representatives, and claim voting rewards on TRON.
digital-native-governance-check
Assess Azure governance maturity for Digital Natives and startups. Detects the most common anti-patterns from the "Digital Natives on Azure" series: incomplete Service Health alerts, flat subscription topology without Management Groups, excessive RBAC (everyone is Owner), missing budget alerts, no Managed Identity…