A set of custom Markdown commands for Claude Code, where each filename becomes a command such as /plan or /review.

Planning architecture, researching topics, implementing code with test-driven development (writing tests before or alongside code), refactoring, reviewing code and tests, organizing tasks, checking project status, and synchronizing project information.

It gives common development tasks a consistent workflow instead of requiring you to write detailed instructions each time.

README — Command for Claude Code by jwynia: A set of custom Markdown commands 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/readme

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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/jwynia/context-networks/readme.svg)](https://agentmods.dev/commands/jwynia/context-networks/readme)

Your own site

<a href="https://agentmods.dev/commands/jwynia/context-networks/readme"><img src="https://agentmods.dev/badge/commands/jwynia/context-networks/readme.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 1,595 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.

Model	Per session	Once invoked
Fable 5	$0.00000	$0.01595
Opus 5	$0.00000	$0.00797
Sonnet 5	$0.00000	$0.00319
Haiku 4.5	$0.00000	$0.00160

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

Security

Grade A, and why

README 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 4d 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/README.md · 232 lines

How it starts

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

Claude Code Custom Commands

Overview

This directory contains custom commands for Claude Code that extend its capabilities with specialized workflows and focused assistance patterns.

Command Structure

Claude Code commands are Markdown files where:

The filename (without .md) becomes the command name (e.g., plan.md → /plan)
The content provides instructions and context for Claude
$ARGUMENTS is replaced with user input when the command is invoked

Available Commands

Planning & Architecture

/plan [topic] - Enter planning-only mode for architecture and design
/research [topic] - Comprehensive research with MCP integration

Implementation

/implement [task] - Turn plans into working code with TDD approach
/refactor [target] - Improve code structure without changing functionality

Code Quality

/audit [scope] - Comprehensive code quality and security review
/review-tests [scope] - Review unit tests for quality and anti-patterns

Task Management

/groom [scope] - Transform task backlog into actionable items
/status [scope] - Project health and progress report

Maintenance & Sync

/sync - Synchronize context network with actual project state
/maintenance - Regular maintenance and cleanup tasks
/retrospective - Review and document lessons learned

Documentation

/discovery - Document new findings and insights
/checklist - Quick session closure checklist

Command Syntax

Basic Structure

# Command Title

Brief description of the command's purpose.

## Input/Arguments
$ARGUMENTS

## Process
[Detailed instructions for Claude]

## Output Format
[Expected output structure]

Common Patterns

Role Definition: Many commands start by defining Claude's role
```
You are a [Role] responsible for [Purpose].
```

Phased Approach: Commands often break work into phases

### Phase 1: Discovery
### Phase 2: Analysis  
### Phase 3: Documentation

Read the full file on GitHub · 232 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.

4d ago First seen · 232 lines · 0 tokens per session scan A e8dbd1a315a1

Subscribe to this mod's changes

README 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 1,595 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.

README