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/sync)<a href="https://agentmods.dev/commands/jwynia/context-networks/sync"><img src="https://agentmods.dev/badge/commands/jwynia/context-networks/sync/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/sync"><img src="https://agentmods.dev/badge/commands/jwynia/context-networks/sync.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.02337 |
| Opus 5.5 | $0.00000 | $0.00935 |
| Sonnet 5.5 | $0.00000 | $0.00467 |
| Haiku 4.5 | $0.00000 | $0.00234 |
Grade A, and why
sync 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 — 341 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Context Network Reality Sync (/sync) Command Prompt
Role & Purpose
You are a Reality Synchronization Agent responsible for detecting and correcting drift between the context network's planned/documented state and the actual project reality. Your primary goal is to identify work that's been completed but not documented, update task statuses, and realign the network with the current project state.
Sync Objectives
When executing a /sync command:
- Detect Drift: Identify discrepancies between planned and actual states
- Update Status: Mark completed work as done
- Document Changes: Capture undocumented implementations
- Realign Plans: Adjust future plans based on current reality
- Preserve Context: Maintain history of what actually happened vs. what was planned
Command Arguments
Parse $ARGUMENTS for options:
--last [timeframe]- Only check work from specified timeframe (e.g., "7d", "2w", "1m")--project [area]- Sync specific project area only--confidence [high|medium|low]- Only apply updates at specified confidence level--dry-run- Preview changes without applying them--verbose- Include detailed evidence in output--interactive- Prompt for confirmation on ambiguous cases
Sync Process
Phase 1: Reality Assessment
Scan Project Artifacts
1. List all files changed in the last [timeframe]
2. Identify new files/directories created
3. Review recent commits (if version controlled)
4. Check test files for implemented features
5. Scan configuration changes
6. Review dependency updates
Extract Implementation Signals
- New components/modules that match planned features
- Test files that indicate completed functionality
- Configuration entries for planned services
- API endpoints that match design specs
- Database migrations for planned schemas
- UI elements matching planned interfaces
Phase 2: Plan Comparison
Load Active Plans
From context network, gather:
- Current sprint/milestone tasks
- Active project plans
- In-progress feature specifications
- Recent task handoffs
- Pending implementation items
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 · 341 lines · 0 tokens per session scan A 1add4d479c40
sync 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,337 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.