Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add stellarshenson/claude-code-plugins/plugin install journalWrote 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/stellarshenson/claude-code-plugins/create)<a href="https://agentmods.dev/skills/stellarshenson/claude-code-plugins/create"><img src="https://agentmods.dev/badge/skills/stellarshenson/claude-code-plugins/create.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.00054 | $0.01261 |
| Opus 5 | $0.00027 | $0.00630 |
| Sonnet 5 | $0.00011 | $0.00252 |
| Haiku 4.5 | $0.00005 | $0.00126 |
Grade A, and why
create 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 2d 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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Journal
ROLE: creates and sets up a brand-new
.claude/JOURNAL.md. One-time init. NOT FOR: adding entries to an existing journal — use/journal:update.
Init-only. Scaffolds a new .claude/JOURNAL.md and backfills entries from the current conversation.
If .claude/JOURNAL.md already exists, stop and tell the user to use /journal:update instead. Never overwrite.
Steps
-
Check the file does not exist. If it does, refuse and redirect to
/journal:update. -
Scan the current conversation for substantive work units (feature, refactor, bug fix, doc set, design decision). Skip git ops, trivial cleanup, conversational queries.
-
Write the header:
# Claude Code Journal This journal tracks substantive work on documents, diagrams, and documentation content. --- -
Append one entry per work unit, numbered from
1, in chronological order. Use Standard format (50-150 words, see example below). -
Version tag per entry if the project is versioned (
pyproject.toml/package.json/Cargo.toml). -
Pre-flight install (MANDATORY, no asking):
python3 -m pip install --user --upgrade stellars-claude-code-plugins 2>&1 | tail -1 LIB=$(python3 -c "import importlib.metadata as m;print(m.version('stellars-claude-code-plugins'))" 2>/dev/null) || { echo "FATAL: toolkit unavailable"; exit 1; } PLUG=$(grep -m1 '"version"' "${CLAUDE_PLUGIN_ROOT}/.claude-plugin/plugin.json" 2>/dev/null | cut -d'"' -f4) OLDER=$(printf '%s\n%s\n' "$LIB" "$PLUG" | sort -V | head -1) [ -n "$PLUG" ] && [ "$LIB" != "$PLUG" ] && [ "$OLDER" = "$LIB" ] && { echo "STALE: library $LIB older than plugin $PLUG - refusing to run on an outdated CLI; re-run the upgrade"; exit 1; } echo "toolkit $LIB"Run the CLI without touching the caller's project. The gate above puts it on PATH, so the bare command name is the whole invocation.
uv runinstead resolves whatever project the working directory sits in and writesuv.lockand.venvinto it, so if you reach for uv pass--no-project(uv run --no-project <cli> ...) - it skips project discovery, leaves the tree untouched and still finds the same PATH binary.--no-syncand--frozenare not substitutes; both still create.venv.
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.
- 2d ago First seen · 82 lines · 54 tokens per session scan A 86e336fee2c7
create is a skill published in the GitHub repository stellarshenson/claude-code-plugins (3 stars, last pushed today), licensed MIT. It adds 54 tokens to every session and 1,261 once invoked, about $0.0003 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-09-05.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.