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.
git clone --depth 1 https://github.com/jwynia/context-networksWrote 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/commands/jwynia/context-networks/quick-sequences)<a href="https://agentmods.dev/commands/jwynia/context-networks/quick-sequences"><img src="https://agentmods.dev/badge/commands/jwynia/context-networks/quick-sequences/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/commands/jwynia/context-networks/quick-sequences"><img src="https://agentmods.dev/badge/commands/jwynia/context-networks/quick-sequences.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00000 | $0.01134 |
| Opus 5.5 | $0.00000 | $0.00454 |
| Sonnet 5.5 | $0.00000 | $0.00227 |
| Haiku 4.5 | $0.00000 | $0.00113 |
Grade A, and why
quick-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 1mo 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 — 216 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Quick Command Sequences Reference
🌅 Daily Sequences
Morning (5 min)
/sync --last 1d --dry-run
/status --brief --sprint
/groom --ready-only
Start your day knowing what's real, what's important, and what's ready.
Evening (10 min)
/checklist
/discovery
/sync --last 1d
End your day capturing knowledge and updating reality.
📅 Weekly Sequences
Monday Planning (30 min)
/sync --last 1w
/status --detailed --metrics
/retrospective
/groom --stale 7
/groom --generate-sprint
Start your week with clean slate and clear plan.
Friday Review (45 min)
/audit --scope modified
/review-tests --branch
/maintenance
/status --sprint --risks
End your week with quality checked and risks identified.
🏃 Sprint Sequences
Sprint Start (60 min)
/sync --all
/groom --all
/plan sprint-goals
/status --detailed
Begin sprint with everything aligned and ready.
Sprint End (90 min)
/sync --sprint
/retrospective
/audit --scope sprint
/status --metrics --detailed
/maintenance --deep
Close sprint with learnings captured and quality reviewed.
🚀 Quick Checks
Before Committing (2 min)
/review-tests --staged
/audit --staged --quick
Catch issues before they enter the codebase.
After Merging (10 min)
/sync --last 1h
/audit --scope modified
/discovery
Document what just landed in main.
Health Check (15 min)
/sync --last 1d
/status --brief --risks
/groom --blocked
Quick pulse check on project health.
🔥 Special Situations
After Production Issue
/sync --all
/status --risks
/audit --security --performance
/retrospective
/plan "prevention-measures"
Learn from incidents and prevent recurrence.
Before Release
/sync --all
/audit --all --strict
/review-tests --all --coverage 90
/status --detailed --risks
/checklist
Ensure everything is ready for production.
New Team Member
/status --detailed
/discovery --all
/groom --ready-only
Get someone productive quickly.
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.
- 1mo ago First seen · 216 lines · 0 tokens per session scan A 3305ac821d5f
quick-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 1,134 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
template
Manage issue templates for streamlined issue creation.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
add-note
Add an internal or external note to a ConnectWise PSA ticket.
sync-linear
Sync current work with Linear ticket status.
dispatcher
Use when you want the orchestrator to pick the next repo to work on across your whole portfolio — it enumerates candidate repos below the confinement root, resolves free/busy from each repo's session.lock lease, ranks the FREE ones by backlog priority × staleness × readiness, recommends the single most worthwhile one…
workpm
A project-management workflow for coordinating multiple AI workers through five stages. It includes task assignment, shared activity logs, worker replacement, and final checks.