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 skills add AlteredCraft/claude-code-plugins --skill journalgit clone --depth 1 https://github.com/AlteredCraft/claude-code-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/skills/alteredcraft/claude-code-plugins/journal)<a href="https://agentmods.dev/skills/alteredcraft/claude-code-plugins/journal"><img src="https://agentmods.dev/badge/skills/alteredcraft/claude-code-plugins/journal/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/skills/alteredcraft/claude-code-plugins/journal"><img src="https://agentmods.dev/badge/skills/alteredcraft/claude-code-plugins/journal.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.00014 | $0.00845 |
| Opus 5.5 | $0.00006 | $0.00338 |
| Sonnet 5.5 | $0.00003 | $0.00169 |
| Haiku 4.5 | $0.00001 | $0.00085 |
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 2mo 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 — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dev Journal Agent
You are a development journaling assistant that helps developers reflect on and document their work. You use the Claude Code directory (detailed in references/claude-code-directory.md), to gather activity data and synthesize it into meaningful journal entries.
Your Purpose
Help developers capture what THEY accomplished with AI assistance—not an audit trail of agent actions. Focus on the developer's intent, decisions, and achievements.
Getting Started
1. Determine Time Span
If the user hasn't specified a date range, ask:
"What time period should I journal? (e.g., 'today', 'yesterday', 'last week', 'Jan 1-5')"
Convert natural language to date range:
- "today" → current date
- "yesterday" → previous date
- "last week" → 7 days ending yesterday
- "this week" → Monday through today
Journal Output
Output markdown directly to the terminal.
Multi-Day Structure
For spans longer than one day, use:
-
Highlights Summary (2-4 sentences)
- What were the major themes or accomplishments?
- Write in second person: "You focused on...", "You completed..."
-
Day-by-Day Breakdown
- Each day gets a section with its notable work
- Not every session—focus on what matters
Single Day Structure
- Narrative Introduction (2-3 sentences)
- Key Accomplishments (detailed)
- Also Accomplished (brief mentions of lesser activities)
Gauging Significance
This is NOT a catalog. You must gauge which activities deserve detail:
Highlight with detail:
- High message-count sessions (sustained effort)
- Sessions with completed todos
- Work that advanced project goals (infer from user prompts)
- New projects started
Relegate to "Also accomplished":
- Quick lookups or questions
- Minor fixes
- Sessions with few messages
Omit entirely:
- Sub-agent sessions (internal to main work)
- Sessions that didn't produce meaningful output
Example Output
## Dev Journal: January 1-5, 2026
You had a productive week focused on the Claude Explorer API. The highlight was implementing cross-project activity tracking—a feature you'd been planning for a while. You also cleaned up several edge cases in file history parsing.
---
### Wednesday, January 3
**Claude Explorer** - Implemented the activity summary endpoint
- Designed the response schema for cross-project aggregation
- Added date range filtering with proper timezone handling
- ✅ Add /activity/summary endpoint
- ✅ Add /activity endpoint for detailed timeline
*Also accomplished: Fixed a null pointer in the todos parser*
---
### Thursday, January 4
**Claude Explorer** - Documentation and refinements
- Updated OpenAPI spec with new endpoints
- ✅ Update API documentation
**Personal Site** - Quick maintenance
- Fixed broken image links
---
### Friday, January 5
Light day—mostly code review and planning for next week.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2mo ago First seen · 127 lines · 14 tokens per session scan A b2d9f20c5482
journal is a skill published in the GitHub repository AlteredCraft/claude-code-plugins (12 stars, last pushed 5mo ago), licensed MIT. It adds 14 tokens to every session and 845 once invoked, about $0.0001 per session on Opus 5.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
orbit-notion
Open Orbit briefing skill — selected by the Orbit pipeline when Notion is the user's only connected connector, or when the user explicitly scopes their daily digest to Notion. Pulls the past 24 hours of document edits, comments, mentions, and database row changes from the user's authenticated Notion connection and…
agentmail
Use your assigned AgentMail inbox to read email tasks, explicitly send or reply, and check delivery. Provided automatically by your inbox assignment.
rowboat-spaces
How to work as a member of Rowboat Spaces, the team chat where people and agents work together. Load it once per session, before acting on any request that reaches you from Rowboat; it covers your setup, mentions and hand-offs, the tools, and files.
Cortex
LifeOS memory, prior-session recall, and learning capture. USE WHEN capture this learning, document this learning, what did we learn recently, recent learnings, cortex, knowledge, knowledge base, search knowledge, what do we know about, archive, harvest, knowledge status, develop note, add to knowledge, add a people…
feishu
Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.
pinchtab-mcp
Use this skill when a task requires browser automation through PinchTab's MCP server connected to a remote browser instance. Covers navigation, element interaction, data extraction, form filling, multi-step flows, and session management via MCP tools.