checklist

checklist is a command for Claude Code from jwynia/context-networks. It costs 0 tokens per session (345 once invoked), scanned A, original, MIT.

A checklist for closing a coding session and recording important work in a project's context network. A context network is a set of linked notes that preserves discoveries, decisions, task status, and code locations.

In plain words
What is it for?
Use it before ending work to check task records, discovery notes, architecture decisions, implementation notes, links between components, and unresolved items.
Why use it?
It reduces the chance that useful findings, architectural decisions, follow-up items, or navigation links disappear when the session ends.

Command for Claude Code

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 commands/jwynia/context-networks/checklist
Clone the repo
git clone --depth 1 https://github.com/jwynia/context-networks

Made for: Claude Code.

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

agentmods badge for checklist

README.md
[![agentmods](https://agentmods.dev/badge/commands/jwynia/context-networks/checklist.svg)](https://agentmods.dev/commands/jwynia/context-networks/checklist)
Your own site
<a href="https://agentmods.dev/commands/jwynia/context-networks/checklist"><img src="https://agentmods.dev/badge/commands/jwynia/context-networks/checklist.svg" alt="Measured on agentmods" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 345 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.00000 $0.00345
Opus 5 $0.00000 $0.00172
Sonnet 5 $0.00000 $0.00069
Haiku 4.5 $0.00000 $0.00034

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

Security

Grade A, and why

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

.claude/commands/checklist.md · 35 lines

What it actually says

Quick Session Closure Checklist

We're about to close this session and lose anything not captured that we might need later. Are all of the following done?

Context Network Task Management

  • Context network task entry exists and is updated with current status
  • Task discoveries documented in /discoveries/records/YYYY-MM-DD-###.md
  • All architectural decisions are documented (with ADRs if significant)
  • Implementation approach is recorded

Discovery Layer Updates

  • Discovery records created for all insights meeting trigger criteria (see /discoveries/triggers.md)
  • Location indexes updated with any new component/feature locations found
  • Learning paths updated if understanding evolved significantly
  • Code exploration insights captured with file paths and line numbers

Relationship & Navigation

  • Discovered relationships are mapped between components/concepts
  • Navigation hubs updated if new paths discovered
  • Bidirectional links established where appropriate

Quality & Boundaries

  • Follow-up items are noted in appropriate sections
  • No planning documents exist outside the context network
  • All documents follow size limits (flag documents >300 lines)
  • Obsolete content archived (not just deleted)

Discovery Triggers Met?

Review /discoveries/triggers.md - did any of these happen without documentation?

  • Spent >5 minutes figuring out how something works
  • Read >3 files to understand one feature
  • Found "I know I saw this somewhere" moments
  • Discovered why something was designed a certain way

$ARGUMENTS

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 · 35 lines · 0 tokens per session scan A be79caab1ebc

Subscribe to this mod's changes

checklist is a command published in the GitHub repository jwynia/context-networks (24 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 345 tokens. 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.