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/sp-daewoon/chronicle/devlognpx skills add sp-daewoon/chronicle --skill devloggit clone --depth 1 https://github.com/sp-daewoon/chronicleWhat 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.00067 | $0.00352 |
| Opus 5 | $0.00034 | $0.00176 |
| Sonnet 5 | $0.00013 | $0.00070 |
| Haiku 4.5 | $0.00007 | $0.00035 |
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 3d 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.
What it actually says
Devlog Workflow
Capture a development session as a dated HTML log.
Gather the session
Summarize what happened this session into the configured sections (default: Summary, Changes, Decisions, Next). Each section's content must be a fragment of valid HTML (e.g. <p>...</p>, <ul><li>...</li></ul>).
Build a JSON object:
{
"title": "Short session title",
"sections": [
{ "heading": "Summary", "html": "<p>...</p>" },
{ "heading": "Changes", "html": "<ul><li>...</li></ul>" }
]
}
Render
Pipe the JSON into the helper with today's date:
echo "$JSON" | node "${CLAUDE_PLUGIN_ROOT}/scripts/devlog-render.mjs" --date <today>
The helper writes <devlog.dir>/YYYY-MM-DD.html (sequencing -2, -3 on repeat calls the same day — it never overwrites) and rebuilds index.html.
Rules
- Use today's real date (never guess).
- Repeat calls the same day create new sequenced files; do not overwrite prior logs.
- Keep HTML fragments self-contained — no external scripts or stylesheets.
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.
- 3d ago First seen · 42 lines · 67 tokens per session scan A dbd54aaa58e1
devlog is a skill published in the GitHub repository sp-daewoon/chronicle (4 stars, last pushed 3mo ago), licensed MIT. It adds 67 tokens to every session and 352 once invoked, about $0.0003 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
scribe
Tactical documentation specialist ensuring all intelligence is properly logged and accessible. README, API docs, ADRs, changelogs, and runbooks.
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
openlore-brainstorm
Transform a feature idea into an annotated story using a Domain Sketch or Constrained Option Tree. Use when asked to brainstorm, explore, or shape a feature before implementation.
openlore-analyze-codebase
Run a full static OpenLore analysis and summarize architecture, call graph, refactoring issues, and duplicate code. Use when asked to analyze, map, or assess a codebase without LLM inference.
openlore-review-changes
Review code changes using OpenLore risk, call, coverage, and cluster evidence without editing code. Use when asked for a change review, pre-PR safety check, or merge recommendation.
project-butler
Project memory workflow for init/upgrade, profile-aware setup, end session, normal/full close, file organization, document archiving, language switching, versioned update logs, rule review, status, wiki sync, and context recovery. Use for /project-butler, setup/初始化, foundation setup, profile setup, end session/收工…