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/documentationnpx skills add vinilana/dotcontext --skill documentationgit 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.00007 | $0.01271 |
| Opus 5 | $0.00003 | $0.00635 |
| Sonnet 5 | $0.00001 | $0.00254 |
| Haiku 4.5 | $0.00001 | $0.00127 |
Grade A, and why
Documentation 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 — 168 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Documentation
Guidelines for creating and maintaining documentation in the @dotcontext/cli project.
When to Use
- Planning phase (P): Writing PRDs, tech specs, or architecture docs in
.context/plans/ - Confirmation phase (C): Updating project docs after feature completion
- Filling scaffold documentation files in
.context/docs/ - Updating the README, CHANGELOG, or CONTRIBUTING guides
- Writing or updating
.context/content (docs, agents, skills, plans)
Documentation Locations
| Location | Purpose | Format |
|---|---|---|
.context/docs/ |
Project knowledge base (generated scaffolds) | Markdown with YAML frontmatter |
.context/agents/ |
AI agent playbooks | Markdown with YAML frontmatter |
.context/skills/ |
On-demand expertise guides | Markdown with YAML frontmatter |
.context/plans/ |
Feature plans and tracking | Markdown with YAML frontmatter |
README.md |
Public-facing project overview | Standard Markdown |
CHANGELOG.md |
Version history (Keep a Changelog format) | Standard Markdown |
CONTRIBUTING.md |
Contributor guidelines | Standard Markdown |
AGENTS.md |
Agent knowledge base reference | Standard Markdown |
CLAUDE.md |
Claude-specific project instructions | Standard Markdown |
Instructions
Updating Scaffold Documentation (.context/docs/)
Scaffold docs use v2 frontmatter:
---
type: documentation
name: Project Overview
description: High-level project summary
category: core
generated: 2026-03-18
status: filled
scaffoldVersion: "2.0.0"
---
Core docs in this project:
project-overview.md-- Technology stack, entry points, getting starteddevelopment-workflow.md-- Branching, CI, contributing processtesting-strategy.md-- Jest config, test types, quality gatestooling.md-- CLI scripts, dev commands, IDE setupcodebase-map.json-- Auto-generated semantic analysis output
When updating, preserve the frontmatter and set status: filled.
Writing Agent Playbooks (.context/agents/)
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 · 168 lines · 7 tokens per session scan A 6a6eac0bf3bf
Documentation is a skill published in the GitHub repository vinilana/dotcontext (561 stars, last pushed 1mo ago), licensed MIT. It adds 7 tokens to every session and 1,271 once invoked, about $0.0000 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…