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/joaquimscosta/arkhe-claude-pluginsWrote 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/commands/joaquimscosta/arkhe-claude-plugins/diary)<a href="https://agentmods.dev/commands/joaquimscosta/arkhe-claude-plugins/diary"><img src="https://agentmods.dev/badge/commands/joaquimscosta/arkhe-claude-plugins/diary.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.00016 | $0.01012 |
| Opus 5 | $0.00008 | $0.00506 |
| Sonnet 5 | $0.00003 | $0.00202 |
| Haiku 4.5 | $0.00002 | $0.00101 |
Grade A, and why
diary 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 — 147 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/diary
This command creates a session diary entry to document development progress, decisions, and handoff context.
Usage
/diary
Creates a new diary entry for the current date, or updates the existing entry if one already exists for today.
Process
1. Determine File Path
- File naming:
/design-intent/diary/session-YYYY-MM-DD.md(e.g.,/design-intent/diary/session-2024-01-15.md) - Date format: Use current date in YYYY-MM-DD format
- Check existing: If file already exists for today, update it instead of creating new
2. Gather Session Information
Before creating the entry, collect information about:
- Session goals: What was planned for this session
- Accomplishments: What was actually built or completed
- Key decisions: Important choices made during implementation
- Current state: Where the project stands now
- Next priorities: What should happen in the next session
- Known issues: Problems that aren't blocking but need attention
3. Create Diary Entry
Use the template from /design-intent/diary/session-template.md
4. Content Guidelines
What We Built Section
Focus on concrete outcomes:
- ✅ "Built gallery component with 3-card responsive layout"
- ✅ "Implemented user authentication flow with mock data"
- ❌ "Worked on some components"
- ❌ "Made progress on the frontend"
Key Implementation Details
Document decisions and reasoning:
- Why specific approaches were chosen
- What alternatives were considered
- How constitution principles were applied
- Trade-offs made for prototype goals
Current State
Be specific about status:
- What functionality works end-to-end
- What's partially implemented
- What's blocked or needs attention
- Any integration points established
Tomorrow's Priorities
Make priorities actionable:
- ✅ "Add loading states to gallery cards"
- ✅ "Implement search functionality for user dashboard"
- ❌ "Continue working on UI"
- ❌ "Fix various issues"
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 · 147 lines · 16 tokens per session scan A d6292a57362e
diary is a command published in the GitHub repository joaquimscosta/arkhe-claude-plugins (21 stars, last pushed 24d ago), licensed MIT. It adds 16 tokens to every session and 1,012 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 commands, from other repositories
instinct
Manage instincts (confidence-based rules from session experience).
forge-compact-task
Compact context with dotforge-standardized hint that preserves decisions, files modified, pending TODOs, behaviors disabled, and last commit. Use at 80% context window instead of waiting for auto-compact.
learning
Meta-commands for capturing session insight back into the system.
cap
Shorthand for /forge capture — register a practice or insight in practices/inbox/.
forge-context-status
Report on current context window usage, cache health, and compaction recommendation. Read-only — does not compact.
export-closedloop-learnings
Exports pending ClosedLoop learnings to global location with deduplication.