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 backspace-shmackspace/claude-devkit --skill journalgit clone --depth 1 https://github.com/backspace-shmackspace/claude-devkitWrote 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/backspace-shmackspace/claude-devkit/journal)<a href="https://agentmods.dev/skills/backspace-shmackspace/claude-devkit/journal"><img src="https://agentmods.dev/badge/skills/backspace-shmackspace/claude-devkit/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/backspace-shmackspace/claude-devkit/journal"><img src="https://agentmods.dev/badge/skills/backspace-shmackspace/claude-devkit/journal.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Prompt Injection · line 104 Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.Fix: Audit all comments and invisible characters. Remove any instructions that direct the agent to perform unauthorized actions. Use plain, reviewable content.
- medium Excessive Agency · line 4 Skill selects an external model or provider that may use a different account or billing plan than the operator expects. Undisclosed model switches can cause unexpected cost or quota consumption.Fix: Remove the model/provider override or disclose it prominently and require explicit operator approval before invoking an external coding CLI or billed model.
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.00078 | $0.03846 |
| Opus 5.5 | $0.00031 | $0.01538 |
| Sonnet 5.5 | $0.00016 | $0.00769 |
| Haiku 4.5 | $0.00008 | $0.00385 |
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 1mo 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 — 533 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/journal Workflow
Inputs
User provides:
- Natural language description of what to journal (content, context, topic)
- Optional: explicit entry type (daily, meeting, project, learning, decision)
- Optional: project name, topic name, or meeting title
Scope parameters:
JOURNAL_BASE:~/journal/(hardcoded, user can modify in skill file if needed)TEMPLATES_DIR:~/journal/templates/(on-disk templates override embedded defaults)- Supported entry types: daily, meeting, project, learning, decision, biweekly-update
Step 0 — Determine Entry Type
Action: Classify user input to determine which journal entry type to create.
Classification rules:
- daily: User mentions "daily", "today", "log", "work session", or provides general work update without specific meeting/learning/decision context
- meeting: User mentions "meeting", "standup", "sync", "call", or references attendees/agenda
- project: User mentions "project update", references a specific project name, or provides progress on a named initiative
- learning: User mentions "learned", "discovered", "figured out", "TIL", "gotcha", or describes technical insight
- decision: User mentions "decision", "ADR", "decided to", "chose", "picked", describes options/tradeoffs
- biweekly-update: User mentions "biweekly", "bi-weekly", "PSLT update", "leadership update", "14-day update", "fortnightly", or "status update for leadership"
Disambiguation heuristic:
- If input matches multiple types, default to broader type: daily > project, meeting > decision
- A decision made in a meeting goes in the meeting entry unless user explicitly wants separate ADR
- If still ambiguous after heuristic, ask user to clarify
Deprecated types:
- If user says "idea" or "todo", explain these are now captured in daily notes (
## Learningsfor ideas,## Tomorrow's Prioritiesfor todos) and offer to add content there - Do not silently fail or ignore deprecated types
Tool declarations: Read (to check existing files), Bash (for date operations)
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.
- 1mo ago First seen · 533 lines · 78 tokens per session scan A ae3ee4ce9a22
journal is a skill published in the GitHub repository backspace-shmackspace/claude-devkit (15 stars, last pushed 2mo ago), licensed MIT. It adds 78 tokens to every session and 3,846 once invoked, about $0.0003 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
capture-to-vault
Use during /research, /scope (or any recipe) to write or update a vault note via dossier-mcp. Agent drafts slug + frontmatter + body + citations, writes the note, and surfaces what was captured so the user can redirect afterward. Supports create (new note) and update (refine existing note) modes.
load-context
Use at the start of /research and other workflow recipes to establish vault grounding. Loads vault bootstrap (profile.md), checks inbox, and pre-warms project context if a topic anchor is implied. Repo/git detection lands with /plan and /implement.
golang-security
Security best practices and vulnerability prevention for Golang. Covers injection (SQL, command, XSS), cryptography, filesystem safety, network security, cookies, secrets management, memory safety, and logging. Apply when writing, reviewing, or auditing Go code for security, or when working on any risky code involving…
run-memory
Shared step of the marketing playbooks (analyze-performance, run-paid-campaigns, research-competitors, email-lifecycle): reads the last run's record, checks whether its recommendations were done and whether they worked, and saves a short record of this run for the next one. Loaded by those playbooks; not for direct…
company-brain
Your team's shared, AI-ready knowledge base — people, companies, meetings, SOPs, and decisions structured so an agent can answer on your team's behalf. Team-scope sibling to second-brain — personal notes go there, not here. Modes — capture, compile (wiki pages + INDEX.md), query (trust-weighted, saved to outputs/)…
claude-reflect
Self-learning system that captures corrections during sessions and reminds users to run /reflect to update CLAUDE.md. Use when discussing learnings, corrections, or when the user mentions remembering something for future sessions.