Borrowing it
Nothing to install: this file belongs to Peiiii/nextclaw. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Peiiii/nextclaw/master/.agents/wiki/skills/governance/nextclaw-iteration-log-governance/SKILL.mdgit clone --depth 1 https://github.com/Peiiii/nextclawWrote 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/peiiii/nextclaw/nextclaw-iteration-log-governance)<a href="https://agentmods.dev/skills/peiiii/nextclaw/nextclaw-iteration-log-governance"><img src="https://agentmods.dev/badge/skills/peiiii/nextclaw/nextclaw-iteration-log-governance/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/peiiii/nextclaw/nextclaw-iteration-log-governance"><img src="https://agentmods.dev/badge/skills/peiiii/nextclaw/nextclaw-iteration-log-governance.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00059 | $0.01205 |
| Opus 5 | $0.00030 | $0.00602 |
| Sonnet 5 | $0.00012 | $0.00241 |
| Haiku 4.5 | $0.00006 | $0.00120 |
Grade A, and why
nextclaw-iteration-log-governance 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.
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 — 150 lines — stays where its author put it; the contents beside it link to each section on GitHub.
NextClaw Iteration Log Governance
When To Use
Use this skill during the closing phase when a task may need docs/logs records.
Do not create an iteration directory at task start only for note-taking unless the user explicitly asks or the relevant iteration already exists.
Decision Rules
Create or update an iteration record when the work has independent delivery or traceability value:
- a commit or release batch is being closed,
- code/runtime changes span modules or a long-running delivery,
- an important root-cause fix or red-zone touch needs durable evidence,
- non-code content changed at large scale, such as governance/rule-system restructure,
- historical iteration records are being materially corrected or expanded,
- release or NPM package state must be recorded.
Do not automatically create an iteration record for:
- uncommitted local edits,
- a small isolated bugfix, test adjustment, style change or refactor with no red-zone/release significance,
- metadata, wording, index, thought, plan, design, PRD or discussion-doc updates,
- work that already belongs to an active related iteration and only needs a later batch-level update.
The user can explicitly request logging at any time. Otherwise, prefer one batch record over one record per task or correction.
Thought/design/plan/PRD documents normally belong under docs/thoughts, docs/plans, docs/designs, or docs/prd, not docs/logs.
Thought / Design / Plan Date Prefix
The iteration mechanism requires dated anchors and dotted role suffixes for thought, design, and plan deposits:
- files under
docs/thoughtsmust useYYYY-MM-DD-<topic>.thought.md, - files under
docs/designsmust useYYYY-MM-DD-<topic>.design.md, - files under
docs/plansmust useYYYY-MM-DD-<topic>.plan.md, - this rule applies even when the work does not need a
docs/logsiteration record.
Same-Batch Rule
If the work is a micro-adjustment, verification fix, or follow-up in the same problem domain and same closing window as the most recent related iteration, update that iteration README.md.
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.
- yesterday Changed · -12 lines d21d2e14b2c0
- 11d ago First seen · 162 lines · 59 tokens per session scan A da15066921eb
nextclaw-iteration-log-governance is a skill published in the GitHub repository Peiiii/nextclaw (256 stars, last pushed today), licensed MIT. It adds 59 tokens to every session and 1,205 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.
Other skills, from other repositories
openclaw-github-dedupe
Investigate a cluster of GitHub issues and PRs, determine canonical candidates, post duplicate/related status, preserve contributor credit, and execute cleanup actions. Supports autonomous mode for provided-link-only closeout, merge/fix follow-through, changelog, and post-merge issue/PR cleanup.
openclaw-pr-batch-sweep
Select, review, repair, validate, and land batches of up to 20 low-risk OpenClaw contributor pull requests using Vincent's maintainer preferences and bounded sub-agent lanes. Use for "next 20", broad contributor PR sweeps, merge-candidate mining, or continued PR-batch work where drafts, maintainer work, trivial…
tmux-lane-orchestrator
Manage one tmux agent lane from its matching ops pane, inspect live pane state and Codex logs on cold start, and produce concise manager summaries for OpenClaw and adjacent project work.
ghcrawl-cluster-operator
Use when inspecting a ghcrawl SQLite store, pulling GitHub issue/PR data, refreshing summaries, embeddings, and clusters, or extracting one cluster and its evidence through the ghcrawl CLI.
opik-optimizer
Optimize LLM prompts, tools, and agents in Opik using standardized optimizer workflows (prompt optimization, tool optimization, and parameter tuning), dataset/metric wiring, and result interpretation.
org-branch-cleanup
Audit and safely prune stale branches across a GitHub organization with immutable snapshots, conservative merged-PR classification, live SHA/protection/open-PR revalidation, resumable deletion ledgers, and post-delete verification. Use when a maintainer asks to clean up old, dead, merged, bot-created, or abandoned…