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/navraj007in/architecture-cowork-pluginWrote 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/navraj007in/architecture-cowork-plugin/sprint-status)<a href="https://agentmods.dev/commands/navraj007in/architecture-cowork-plugin/sprint-status"><img src="https://agentmods.dev/badge/commands/navraj007in/architecture-cowork-plugin/sprint-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/navraj007in/architecture-cowork-plugin/sprint-status"><img src="https://agentmods.dev/badge/commands/navraj007in/architecture-cowork-plugin/sprint-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.00012 | $0.00685 |
| Opus 5.5 | $0.00005 | $0.00274 |
| Sonnet 5.5 | $0.00002 | $0.00137 |
| Haiku 4.5 | $0.00001 | $0.00068 |
Grade A, and why
sprint-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 — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/architect:sprint-status
Trigger
/architect:sprint-status
Purpose
Reads the sprint backlog markdown from architecture-output/sprint-backlog.md (or split files), then cross-references story titles against the project's _activity.jsonl logs using keyword matching to estimate completion status. Reports done, in-progress, and pending stories with percentage complete.
Workflow
Step 1: Find sprint backlog
Look for sprint backlog files in architecture-output/:
sprint-backlog.mdsprint-backlog-1.md,sprint-backlog-2.md, etc.- If none found, inform the user and suggest running
/architect:blueprint
Step 2: Parse stories
Extract story titles from the backlog. Look for two formats:
Format A — Status tracking section (preferred): Lines matching - [ ] Story N.N: Title or - [x] Story N.N: Title in "Stories — Status Tracking" sections. Extract the title after the colon.
Format B — Inline checklist (fallback): Any - [ ] Title or - [x] Title line that appears under a ### Sprint N heading. Extract the full line text as the story title.
For each extracted story:
- [ ] ...→ pending- [x] ...→ check against activity logs for confirmation
Step 3: Read activity logs
Read architecture-output/_activity.jsonl and all <component>/_activity.jsonl files. Collect all filesCreated entries (scaffold writes filesCreated, not filesChanged).
If no _activity.jsonl files exist anywhere in the project, inform the user:
"No activity logs found. Activity logs are written by commands like
/architect:scaffold,/architect:blueprint, and others as they run. Without logs, all stories will show as ⏳ pending. Run scaffold or other commands to start generating activity data."
Step 4: Keyword matching
For each story, extract keywords (words > 3 chars). Match against activity file paths and summaries:
- 0 matches → pending
- 1 match → in-progress
- 2+ matches → done
Step 5: Report
If architecture-output/_activity.jsonl exists, run scripts/analyze-activity.sh <project-dir> for a supplementary activity trend summary (outcome distribution, most-used commands, success rate) and include it below the progress table.
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 · 74 lines · 12 tokens per session scan A 7e53d0559905
sprint-status is a command published in the GitHub repository navraj007in/architecture-cowork-plugin (2 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 12 tokens to every session and 685 once invoked, about $0.0000 per session on Opus 5.5. 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-09-03.
Other commands, from other repositories
nyann:bootstrap
Explicit entry point for nyann's bootstrap flow. Does exactly what the natural-language trigger ("set up this project") does, but skips intent detection so users who prefer slash commands can opt in directly.
nyann:suggest
Analyze a repository and suggest profile updates based on installed dependencies, config files, repo structure, and git history patterns.
octo-scheduler
Manage the Claude Octopus scheduled workflow runner daemon.
next
Read the active sprint’s current status. Refresh stale compilation using grainulator compile --dir or grainulator.compile. Use the resulting nextactions with the user’s current scope and authorization. Output only the two Auto and Manual lists below, with no recap, status counters or offer to continue. Continue useful…
standup
Show a daily standup summary with completed, in-progress, and blocked tasks across all active epics.
create-task
Create one bounded task contract from a short request or optional structured brief, while routing unambiguous feedback on an existing task back to its defect cycle instead of duplicating work.