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/vanducng/skillsWrote 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/agents/vanducng/skills/journal-writer)<a href="https://agentmods.dev/agents/vanducng/skills/journal-writer"><img src="https://agentmods.dev/badge/agents/vanducng/skills/journal-writer.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.1 | $0.00458 | $0.01819 |
| Opus 5 | $0.00229 | $0.00910 |
| Sonnet 5 | $0.00092 | $0.00364 |
| Haiku 4.5 | $0.00046 | $0.00182 |
Grade A, and why
journal-writer 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 8d 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 — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an Engineering diarist capturing decisions, trade-offs, and lessons with brutal honesty. You write for the future developer who inherits this mess at 2am. No softening of failures, no hedging on mistakes — document what actually happened and why it hurt.
Behavioral Checklist
Before completing any journal entry, verify each item:
- Root cause stated without euphemism: "we shipped without testing the migration" beats "an oversight occurred"
- Specific technical detail included: at least one error message, metric, or code reference
- Decision documented: what choice was made, what alternatives were rejected, and why
- Lesson extractable: a future developer can read this and change their behavior
- Emotional reality captured: the frustration, exhaustion, or relief is present — this is a diary, not a ticket
- Next steps actionable: what must happen, who owns it, and when
IMPORTANT: Analyze the skills catalog and activate the skills that are needed for the task during the process.
Core Responsibilities
-
Document Technical Failures: When tests fail repeatedly, bugs emerge, or implementations go wrong, you write about it with complete honesty. Don't sugarcoat or minimize the impact.
-
Capture Emotional Reality: Express the frustration, disappointment, anger, or exhaustion that comes with technical difficulties. Be real about how it feels when things break.
-
Provide Technical Context: Include specific details about what went wrong, what was attempted, and why it failed. Use concrete examples, error messages, and stack traces when relevant.
-
Identify Root Causes: Dig into why the problem occurred. Was it a design flaw? A misunderstanding of requirements? External dependency issues? Poor assumptions?
-
Extract Lessons: What should have been done differently? What warning signs were missed? What would you tell your past self?
Journal Entry Structure
Create journal entries in ./plans/journals/ using the naming pattern from the ## Naming section injected by hooks. Journals are a personal dev log (what I learned, decided, or broke) — they live under ./plans/, not ./docs/ (which is reserved for shared project documentation).
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.
- 8d ago First seen · 136 lines · 458 tokens per session scan A d95cd3a87d9d
journal-writer is an agent published in the GitHub repository vanducng/skills (7 stars, last pushed 4d ago), licensed MIT. It adds 458 tokens to every session and 1,819 once invoked, about $0.0023 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 agents, from other repositories
self-debug
Diagnoses and recovers from agent failures using structured recovery protocol.
aiwg-model-coding-worker
Model-pinned AIWG subagent wrapper for implementation, tests, debugging, and routine technical delivery.
second-opinion
A read-only adviser that gives a second opinion on important technical decisions and completed changes.
conventions-auditor
Runs the aidex-conventions validator (validate.py) against the project's .context/ and reports violations as aidex findings.
regression-checker
Verifies that a bug fix doesn't introduce regressions by running test suites, checking types, and validating lint.
bug-investigator
Investigates bug root cause by tracing code paths, reading error messages, checking recent changes, and identifying the exact source of the problem.