writing-modpack-devlog

A record-keeping workflow for a modpack, a collection of game modifications managed together. It creates or updates a dated development log.

In plain words
What is it for?
Logging mod changes, conflict checks, crashes, missing assets, broken quests, releases, and decisions that should not be reconsidered.
Why use it?
It prevents important modpack decisions, investigations, and changes from being lost or forgotten by future maintainers.

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/hashgraph-online/awesome-codex-plugins/writing-modpack-devlog
Any agent
npx skills add hashgraph-online/awesome-codex-plugins --skill writing-modpack-devlog
Clone the repo
git clone --depth 1 https://github.com/hashgraph-online/awesome-codex-plugins

Made for: Claude Code, Codex.

Per session 68 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,249 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.00068 $0.02249
Opus 5 $0.00034 $0.01125
Sonnet 5 $0.00014 $0.00450
Haiku 4.5 $0.00007 $0.00225

Measured 3d ago against content hash 18bbdc0fce05, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

writing-modpack-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.

plugins/BB-84C/bgs-modding-superpowers/skills/writing-modpack-devlog/SKILL.md · 168 lines

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.

Overview

The modpack dev-log is the durable record of what the curator did to the modpack, in chronological order, with enough context for a future maintainer to understand why a change happened. This skill replaces the deleted templates/modpack/dev-log.md template by creating <project>/docs/dev-log.md at runtime, then appending entries as the modpack evolves.

When to Use

Use this skill when... Result
The user says "log this", "add to dev log", "record what I did", or "note this change" Append a dated entry to the project dev-log.
A mod was added, removed, replaced, upgraded, downgraded, patched, or moved in load order Record what changed and why.
A conflict-audit session finished Summarize the finding and link evidence from xedit-conflict-audit or xedit-automation output.
A CTD, freeze, missing asset, bad facegen, navmesh issue, or broken quest was investigated Preserve the investigation result, even if the fix is not final.
A modpack release was cut Add the curator-facing note and cross-link to writing-modpack-changelog.
The user made a manual decision that future agents must not re-litigate Record the decision, context, and evidence.

When NOT to Use

Do not use this skill when... Use instead
The user is preparing public release notes for players writing-modpack-changelog
The user asks for a one-off explanation without wanting a project record Answer directly.
The project root is unknown and the user refuses to identify it Stop after explaining what is missing.
The entry would expose private notes, credentials, or personal information Ask for a sanitized version first.
The request is to inspect or edit plugin records xedit-automation or xedit-conflict-audit first, then log the result.

Rules

Read the full file on GitHub · 168 lines

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. 3d ago First seen · 168 lines · 68 tokens per session scan A 18bbdc0fce05

Subscribe to this mod's changes

writing-modpack-devlog is a skill published in the GitHub repository hashgraph-online/awesome-codex-plugins (859 stars, last pushed 5d ago), licensed Apache-2.0. It adds 68 tokens to every session and 2,249 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-30.

Related

Other skills, from other repositories

search

Search 2500+ curated ChatGPT and LLM open-source repositories. Use when the user asks to find tools, libraries, or repos related to ChatGPT, LLMs, RAG, agents, langchain, NLP, AI development, or any open-source AI tooling.

taishi-i/awesome-ChatGPT-repositories · 57 tokens

graphics-api-hooking

Guide for graphics API interception, overlay rendering, and render-pipeline analysis across DirectX, OpenGL, and Vulkan. Use this skill when working with Present or SwapBuffers hooks, DXGI swap chains, shader or draw-call interception, screenshot-sensitive overlays, or graphics debugging in game security research.

gmh5225/awesome-game-security · 64 tokens

reverse-engineering-tools

Guide for reverse engineering protected games and anti-cheat components across user mode, kernel mode, and hypervisor-aware environments. Use this skill when analyzing drivers, IOCTL protocols, callback registration, injected-code artifacts, integrity checks, protected binaries, or debugging security-sensitive game…

gmh5225/awesome-game-security · 60 tokens

review-prs

Triage open PRs — screen from the diff, delegate the admission judgment to audit-the-list, then merge or close on GitHub. Fire when the maintainer asks to review PRs, process the PR queue, or judge whether a specific PR should be merged.

vinta/awesome-python · 58 tokens

game-feel

Add "juice" and game feel that makes actions satisfying — screen shake, hit-stop/freeze frames, tweened/eased motion, squash & stretch, knockback, and layered audio-visual feedback — as engine-neutral techniques that pair with the detected engine's tween, particle, and camera APIs. Use when the user mentions game…

gamedev-skills/awesome-gamedev-agent-skills · 116 tokens

audio-design

Implement game audio practice — bus/mixer architecture and gain in decibels, ducking (sidechain), adaptive/dynamic music via layering and re-sequencing, SFX variation, and beat synchronization. Engine-neutral. Use when the user mentions audio mixing, audio buses, adaptive/dynamic music, ducking, SFX variation, music…

gamedev-skills/awesome-gamedev-agent-skills · 81 tokens