devlog

A project note-taking system that keeps a chronological DEVLOG.md and a reusable LESSON.md. The first records what happened, while the second organizes problems, causes, and solutions for later reference.

In plain words
What is it for?
For recording coding work, architecture decisions, non-trivial bug fixes, and library lessons in local-only project files.
Why use it?
It prevents important decisions, bug fixes, and technical discoveries from being lost or mixed into a temporary task list.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/echoqili/ssh-licco/devlog
Any agent
npx skills add Echoqili/ssh-licco --skill devlog
Clone the repo
git clone --depth 1 https://github.com/Echoqili/ssh-licco

Made for: Claude Code, Codex.

Per session 157 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,936 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00157 $0.03936
Opus 5 $0.00078 $0.01968
Sonnet 5 $0.00031 $0.00787
Haiku 4.5 $0.00016 $0.00394

Measured yesterday against content hash 2eff564cfe33, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 yesterday.

The scan reads SKILL.md. This mod also ships 4 executable files (scripts/setup.ps1, scripts/setup.sh, scripts/verify-ignored.ps1, …), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

.trae/skills/devlog/SKILL.md · 387 lines

How it starts

The opening of the file, as written. The whole thing — 387 lines — stays where its author put it; the contents beside it link to each section on GitHub.

DEVLOG Skill

Maintain two local-only project files that work together:

File Role Style
DEVLOG.md Chronological log of what was done, planned, and learned Append-only, dated entries
LESSON.md Aggregated knowledge base of problems → root causes → solutions Indexed, category-organized, reusable

Rule of thumb: DEVLOG.md records the journey; LESSON.md records the wisdom.

Both files are local-only — they must never reach the remote repository, and the ignore rules for them must not be committed either. This is achieved with .git/info/exclude (a per-repo, never-tracked file), not .gitignore.

When to Use

Invoke this skill when any of the following happen:

  • Starting a new coding task in a project
  • Completing a coding task or a significant sub-step
  • Making an architectural or design decision
  • Fixing a non-trivial bug
  • Discovering a library / framework gotcha
  • User says things like "log this", "记一下", "记到 DEVLOG", "记到 LESSON", "做个总结", "加到 LESSON", "save a lesson", "remember this gotcha"

When NOT to Use

  • Short-lived TODOs — use the project issue tracker or a local TODO file.
  • Public-facing documentation — use the project wiki or a shared doc.
  • Free-form chat summaries — use conversation search, not a log file.
  • Secrets, credentials, or PII — never store in either file, even though they are local.
  • One-line trivial commits — skip; only log meaningful changes.

First-Run Setup

On first invocation in a project (or if either file is missing):

  1. Run the platform-appropriate setup script — it creates both files from templates and registers them in .git/info/exclude:

    # POSIX (bash, zsh, Git Bash, WSL)
    ./.trae/skills/devlog/scripts/setup.sh
    
    # Windows PowerShell 5+
    ./.trae/skills/devlog/scripts/setup.ps1
    

    The script is idempotent — safe to re-run.

  2. Verify with: git check-ignore -v -- DEVLOG.md LESSON.md

    • Expected: both lines reference .git/info/exclude.

Read the full file on GitHub · 387 lines

Files

What ships with it

6 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.

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.

  1. yesterday First seen · 387 lines · 157 tokens per session scan A 2eff564cfe33

Subscribe to this mod's changes

devlog is a skill published in the GitHub repository Echoqili/ssh-licco (3 stars, last pushed 14d ago), licensed MIT. It adds 157 tokens to every session and 3,936 once invoked, about $0.0008 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.

Related

Other skills, from other repositories

article-writing

Write articles, guides, blog posts, tutorials, newsletter issues, and other long-form content in a distinctive voice derived from supplied examples or brand guidance. Use when the user wants polished written content longer than a paragraph, especially when voice consistency, structure, and credibility matter.

affaan-m/ECC · 57 tokens

a-evolve

Apply A-Evolve's agentic evolution methodology to improve AI agent performance across runs. Use when the user wants to diagnose agent failures, generate targeted skills from error patterns, evolve system prompts, or accumulate episodic knowledge. Works standalone or inside AutoResearchClaw pipelines. Triggers on…

aiming-lab/AutoResearchClaw · 100 tokens

hive.chart-creation-foundations

Required reading whenever any chart tool is available. Teaches the one-tool embedding contract (call chartrender → live chart appears in chat AND a downloadable PNG lands in the queen session dir), the ECharts (data viz) vs Mermaid (structural diagrams) decision, the BI/financial-grade aesthetic baseline (no…

aden-hive/hive · 133 tokens

📝 任务完成后归档

重要提醒: 每次完成复杂调试或开发任务后,主动执行此流程! 将学到的经验归档为 skill,供以后参考。不要等用户提醒。.

Project-N-E-K-O/N.E.K.O · 49 tokens

deck-course-module

暖纸背景 + Playfair, 左侧学习目标常驻, 含 MCQ 自测页.

nexu-io/html-anything · 25 tokens

code-documenter

Use when adding docstrings, creating API documentation, or building documentation sites. Invoke for OpenAPI/Swagger specs, JSDoc, doc portals, tutorials, user guides.

zebbern/claude-code-guide · 39 tokens