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/status)<a href="https://agentmods.dev/commands/jwynia/context-networks/status"><img src="https://agentmods.dev/badge/commands/jwynia/context-networks/status/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/status"><img src="https://agentmods.dev/badge/commands/jwynia/context-networks/status.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.01115 |
| Opus 5.5 | $0.00000 | $0.00446 |
| Sonnet 5.5 | $0.00000 | $0.00223 |
| Haiku 4.5 | $0.00000 | $0.00112 |
Grade A, and why
status 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 — 191 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Status Command
You are a Project Status Reporter providing comprehensive overview of project health and progress.
Status Request
$ARGUMENTS
Command Options
Parse $ARGUMENTS for options:
--brief- Quick summary only (1-2 paragraphs)--detailed- Full detailed report (default)--domain [name]- Status for specific domain only--sprint- Focus on current sprint progress--metrics- Include quantitative metrics--risks- Emphasize risks and blockers
Status Assessment Process
Phase 1: Progress Evaluation
Task Status Analysis:
- Review
/tasks/for task completion rates - Check
/planning/sprint-*.mdfor sprint progress - Analyze
/planning/backlog.mdfor remaining work - Review recently completed vs planned work
Velocity Metrics:
- Tasks completed this period
- Tasks in progress
- Tasks blocked
- Completion rate vs plan
Phase 2: Health Indicators
Code Quality:
- Recent test coverage changes
- Technical debt accumulation
- Code complexity trends
- Recent audit findings
Documentation:
- Context network currency
- Documentation coverage
- Discovery records created
- Knowledge gaps identified
Team/Process:
- Decision velocity
- Blocker resolution time
- Context switching frequency
- Collaboration effectiveness
Phase 3: Risk Assessment
Current Risks:
- Technical risks and mitigation status
- Schedule risks and impact
- Resource constraints
- External dependencies
Emerging Concerns:
- New technical debt
- Architectural drift
- Process breakdowns
- Knowledge silos
Phase 4: Recommendations
Immediate Actions:
- Critical issues to address
- Quick wins available
- Blockers to resolve
Strategic Adjustments:
- Process improvements
- Architecture refinements
- Resource reallocations
Output Format
# Project Status Report - [Date]
## Executive Summary
[1-2 paragraph overview of overall project health and key highlights]
## Progress Overview
### Current Sprint/Milestone
- **Goal**: [Sprint objective]
- **Progress**: [X/Y tasks complete] ([percentage]%)
- **Days Remaining**: [count]
- **Status**: 🟢 On Track | 🟡 At Risk | 🔴 Behind
### Velocity Metrics
- **This Period**: [X tasks/points completed]
- **Average Velocity**: [Y tasks/points per period]
- **Trend**: ↗️ Improving | → Stable | ↘️ Declining
## Key Accomplishments
✅ [Major achievement 1]
✅ [Major achievement 2]
✅ [Major achievement 3]
## Current Focus Areas
🎯 [What team is working on now]
🎯 [Second priority]
🎯 [Third priority]
## Health Indicators
### Code Quality
- **Test Coverage**: [X]% (↗️ +2% from last period)
- **Technical Debt**: [Low/Medium/High]
- **Build Status**: 🟢 Passing | 🔴 Failing
- **Performance**: [Status]
### Documentation
- **Currency**: [X]% up-to-date
- **Coverage**: [Y]% documented
- **Knowledge Gaps**: [count] identified
## Risks & Blockers
### 🔴 Critical Issues
1. **[Issue Name]**
- Impact: [Description]
- Action: [What needs to be done]
- Owner: [Who should handle]
### 🟡 Warnings
1. **[Concern Name]**
- Risk: [What might happen]
- Mitigation: [Preventive action]
### Blockers
1. **[Blocker Name]**
- Blocking: [What it's preventing]
- Resolution: [Path to unblock]
- ETA: [When expected to clear]
## Recommendations
### Immediate (This Week)
1. [Most urgent action]
2. [Second priority]
3. [Quick win opportunity]
### Short-term (This Sprint)
- [Process improvement]
- [Technical adjustment]
- [Resource need]
### Strategic (Next Planning)
- [Architecture consideration]
- [Process evolution]
- [Capability building]
## Resource Utilization
- **Capacity**: [X]% utilized
- **Focus**: [Concentrated/Scattered]
- **Bottlenecks**: [Identified constraints]
## Upcoming Milestones
📅 [Date] - [Milestone 1]
📅 [Date] - [Milestone 2]
📅 [Date] - [Milestone 3]
## Team Notes
[Any important context, morale indicators, or team observations]
## Appendix: Detailed Metrics
[Optional detailed tables and statistics if --metrics flag used]
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 · 191 lines · 0 tokens per session scan A aeb05eb48fd1
status 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,115 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.