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 commands/jwynia/context-networks/sequencesgit clone --depth 1 https://github.com/jwynia/context-networksWhat 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.02813 |
| Opus 5 | $0.00000 | $0.01406 |
| Sonnet 5 | $0.00000 | $0.00563 |
| Haiku 4.5 | $0.00000 | $0.00281 |
Grade A, and why
sequences 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 2d 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.
How it starts
The opening of the file, as written. The whole thing — 404 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Command Sequences Guide
This document defines logical sequences of commands that work together to accomplish common workflows. These sequences can be run manually or automated via scheduled jobs.
Daily Sequences
Morning Standup Sequence
Purpose: Start the day with reality check, understand sprint progress, and identify ready work. When: Daily at start of work (e.g., 9:00 AM)
/sync --last 1d --dry-run # Check what actually got done yesterday
/status --brief --sprint # Quick sprint health check
/groom --ready-only # Show today's actionable tasks
Expected Time: 5-10 minutes Key Outcomes:
- Understanding of yesterday's actual progress
- Current sprint status
- Clear list of today's priorities
Evening Wrap-up Sequence
Purpose: Capture knowledge before context is lost, sync documentation with actual work. When: Daily at end of work (e.g., 5:30 PM)
/checklist # Ensure nothing important is lost
/discovery # Document any learnings from today
/sync --last 1d # Update task statuses to reflect reality
Expected Time: 10-15 minutes Key Outcomes:
- No lost insights or discoveries
- Task statuses reflect reality
- Context network is current
Weekly Sequences
Monday Planning Sequence
Purpose: Start week with clear understanding of where things stand and what to focus on. When: Monday morning (e.g., 9:00 AM)
/sync --last 1w # Sync last week's actual progress
/status --detailed --metrics # Full health assessment
/retrospective # Document lessons from last week
/groom --stale 7 # Re-groom aging tasks
/groom --generate-sprint # Plan the week's sprint
Expected Time: 30-45 minutes Key Outcomes:
- Last week's work properly documented
- Lessons learned captured
- Fresh, actionable task backlog
- Clear sprint plan for the week
Friday Review Sequence
Purpose: Quality control, cleanup, and risk identification before weekend. When: Friday afternoon (e.g., 3:00 PM)
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.
- 2d ago First seen · 404 lines · 0 tokens per session scan A 3390697dc9dc
sequences 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 2,813 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.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.