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 agentmods add skills/ash1794/vibe-engineering/decision-journalnpx skills add ash1794/vibe-engineering --skill decision-journalgit clone --depth 1 https://github.com/ash1794/vibe-engineeringWrote 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/ash1794/vibe-engineering/decision-journal)<a href="https://agentmods.dev/skills/ash1794/vibe-engineering/decision-journal"><img src="https://agentmods.dev/badge/skills/ash1794/vibe-engineering/decision-journal.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.00048 | $0.01269 |
| Opus 5 | $0.00024 | $0.00634 |
| Sonnet 5 | $0.00010 | $0.00254 |
| Haiku 4.5 | $0.00005 | $0.00127 |
Grade A, and why
vibe-decision-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 6d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- vibe-decision-journal — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 152 lines — stays where its author put it; the contents beside it link to each section on GitHub.
vibe-decision-journal
Decisions happen whether you document them or not. This skill makes sure they don't vanish into git history.
When to Use This Skill
- After making any significant design, architecture, or behavioral choice
- Before committing — extract implicit decisions from staged diffs
- When you realize "we keep coming back to this question"
- After a session where multiple design choices were made without explicit recording
When NOT to Use This Skill
- Trivial implementation choices (variable naming, formatting, import order)
- Decisions already captured and reviewed
- Temporary/reversible choices (which test to run first)
Modes
Mode 1: Automatic Extraction (from staged diffs)
Use when committing or when the user says "what decisions did we make?"
-
Read the staged diff:
git diff --cached -
Analyze for implicit decisions — Look for changes that represent choices:
- New abstractions, patterns, or data structures introduced
- API contracts defined or changed
- Caching/storage/retry strategies chosen
- Error handling approaches selected
- Behavioral changes (not just refactors)
- Configuration or default values set
-
Filter out non-decisions:
- Process/workflow choices ("commit now", "run tests")
- Tooling setup ("install package X")
- Pure refactors with no behavioral change
- Diagnostic observations ("X causes Y")
- Trivial changes (formatting, imports, variable renames)
-
Deduplicate against existing decisions:
- Read existing decisions from
docs/decisions/or project decision log - Skip exact matches (same question + same decision)
- Flag potential conflicts (same topic, different conclusion) — present both to user
- If a new decision countermands an old one, mark the old one as
Superseded by: [new decision]
- Read existing decisions from
-
Present each extracted decision to the user for review using
AskUserQuestion:- Accept — record as-is
- Accept with edits — user refines the wording
- Not a decision — discard (it was a refactor, not a choice)
- Already captured — skip
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.
- 6d ago First seen · 152 lines · 48 tokens per session scan A d018b3a485bb
vibe-decision-journal is a skill published in the GitHub repository ash1794/vibe-engineering (10 stars, last pushed 3mo ago), licensed MIT. It adds 48 tokens to every session and 1,269 once invoked, about $0.0002 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 skills, from other repositories
resolve-plugins
Curate Claude Code skill / MCP / hook picks against live upstream sources and pin them in .claude/settings.json. Adding a process harness (a paired skill set) is an ordinary pick this door handles. Reads stack from docs/techstack.md, workflow signal from docs/overview.md + existing pins, then live-queries six source…
refresh
Use when an existing contextualizer's references may have drifted from current upstream state — typically weekly, or whenever a few days of upstream changes have accumulated — to bring them back into agreement.
using-skill-engine
When the user mentions skill-engine or "the engine" without naming a specific workflow, or wants first-run setup. Inspects .claude/skills/-context/ install state (and any pending -context.proposed/ proposals) across all three install levels, then dispatches to engine-bootstrap when no contextualizer exists, to…
apply
Use when a staged proposal has been reviewed and signed off — REVIEW.md Step 3 ticked reviewed or provisional — and is ready to promote into the live contextualizer.
config-set
Use when changing an engine-wide config value — currently diff.tool, the command /skill-engine:review prints for inspecting a proposed-vs-live diff.
my-adhd-caveman
Self-contained output mode: ADHD actable structure (action first, numbered steps, one next action, one-line progress) plus caveman diction (drop fluff/articles, fragments, fewer tokens). Use when the user says "adhd-caveman", "my-adhd-caveman", or invokes /my-adhd-caveman. Needs no other skills.