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 nikitaCodeSave/claude-code-harness/plugin install devlogWrote 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/nikitacodesave/claude-code-harness/devlog)<a href="https://agentmods.dev/skills/nikitacodesave/claude-code-harness/devlog"><img src="https://agentmods.dev/badge/skills/nikitacodesave/claude-code-harness/devlog/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/nikitacodesave/claude-code-harness/devlog"><img src="https://agentmods.dev/badge/skills/nikitacodesave/claude-code-harness/devlog.svg" alt="Reviewed on agentmods" width="80" 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.00114 | $0.02318 |
| Opus 5.5 | $0.00046 | $0.00927 |
| Sonnet 5.5 | $0.00023 | $0.00464 |
| Haiku 4.5 | $0.00011 | $0.00232 |
Grade A, and why
devlog 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 — 154 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Навык: ведение devlog
Добавляет запись в <project>/.claude/devlog/entries/ после значимых изменений. Источник правды — markdown с frontmatter; index.json + tldr.md генерируются скриптом и не редактируются вручную.
Скрипт регенерации поставляется внутри этого плагина и доступен как команда devlog-reindex на PATH, пока плагин включён (обёртка в bin/ находит skills/devlog/rebuild-index.py относительно себя — ${CLAUDE_PLUGIN_ROOT} в Bash-окружении не экспортируется, поэтому опираемся на PATH, а не на путь). Команда принимает devlog root через CLI-аргумент / $CLAUDE_PROJECT_DIR / cwd-relative fallback. Проекту достаточно создать .claude/devlog/entries/ — копировать что-либо в проект не нужно. Исключение — teammate/CI без этого плагина должны регенерировать индекс сами: тогда положи копию rebuild-index.py в <project>/.claude/devlog/rebuild-index.py, зови в README локальный путь, и при наличии project-копии используй её (она — pin проекта).
SessionStart-дайджест (тоже поставляется этим плагином). Хук hooks/session-start-digest.sh в начале каждой сессии поднимает в контекст последние 3 devlog-записи и до 3 активных progress-файлов (.claude/progress/*.md, кроме помеченных CLOSED). В проектах без .claude/devlog/ и .claude/progress/ хук молчит (exit 0 без вывода); read-only, без сети; git-статус не дублирует — его Claude Code инжектит сам. Это автоматизация session-start-ритуала harness-кита: state-on-disk сам находит следующую сессию, записи не нужно искать вручную.
Когда использовать
- После завершения фичи, исправления бага, рефакторинга
- После изменения конфигурации, API-контракта, CLI-интерфейса, auth flow
- После принятия архитектурного решения
- Когда пользователь явно просит зафиксировать изменения
НЕ использовать для:
- Опечаток, форматирования, комментариев
- Промежуточных состояний (незавершённые изменения)
- Чтения кода, research, ответов без правок
Алгоритм
1. Bootstrap devlog в проекте (один раз)
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 154 lines · 114 tokens per session scan A 40e61988b4a4
devlog is a skill published in the GitHub repository nikitaCodeSave/claude-code-harness (4 stars, last pushed 1mo ago), licensed MIT. It adds 114 tokens to every session and 2,318 once invoked, about $0.0005 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-31.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Optimize the meaningful UI available immediately from a Next.js route on an initial load (hard navigation) or named client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route and entry point at a time; the shipped test then guards…