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/vinilana/dotcontext/commit-messagenpx skills add vinilana/dotcontext --skill commit-messagegit clone --depth 1 https://github.com/vinilana/dotcontextWhat 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 | $0.00012 | $0.01384 |
| Opus 5 | $0.00006 | $0.00692 |
| Sonnet 5 | $0.00002 | $0.00277 |
| Haiku 4.5 | $0.00001 | $0.00138 |
Grade A, and why
Commit Message 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 — 177 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Commit Message
Generate consistent, informative commit messages for the @dotcontext/cli project.
When to Use
- Committing code during the Execution (E) or Confirmation (C) phases
- After completing a feature, bug fix, or refactoring task
- When using the
plan({ action: 'commitPhase' })MCP tool to auto-commit phase outputs
Commit Format
This project follows Conventional Commits with scope detection:
<type>(<scope>): <description>
[optional body]
[optional footer]
Types
| Type | Use When |
|---|---|
feat |
Adding new functionality (new MCP tool, new generator, new CLI command) |
fix |
Fixing a bug (broken scaffold generation, incorrect path resolution) |
refactor |
Restructuring code without changing behavior (service extraction, gateway consolidation) |
docs |
Documentation only (README, CHANGELOG, .context/ content) |
test |
Adding or updating tests |
chore |
Build, tooling, dependency updates |
ci |
CI/CD configuration |
Scopes
Derive scope from the primary area of change:
| Scope | Directory/Area |
|---|---|
mcp |
src/services/mcp/ -- MCP server, gateway tools |
cli |
src/index.ts -- CLI commands, commander setup |
context |
src/services/ai/tools/, src/services/init/ -- MCP scaffold and semantic-context flows |
init |
src/services/init/ -- Scaffold initialization |
sync |
src/services/sync/, src/services/export/, src/services/import/ |
semantic |
src/services/semantic/ -- Tree-sitter, LSP, codebase analysis |
workflow |
src/workflow/, src/services/workflow/ -- PREVC phases, gates |
generators |
src/generators/ -- Doc, agent, plan, skill generators |
skills |
src/workflow/skills/, .context/skills/ |
agents |
src/generators/agents/, .context/agents/ |
plans |
src/generators/plans/, src/services/mcp/gateway/plan.ts, .context/plans/ |
i18n |
src/utils/i18n.ts -- Translations |
utils |
src/utils/ -- Frontmatter, git, CLI UI |
ai |
src/services/ai/ -- AI SDK, providers, tools |
types |
src/types/, src/types.ts -- Type definitions |
deps |
package.json -- Dependency changes |
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 · 177 lines · 12 tokens per session scan A 3fb44f4aa633
Commit Message is a skill published in the GitHub repository vinilana/dotcontext (560 stars, last pushed 1mo ago), licensed MIT. It adds 12 tokens to every session and 1,384 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…