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/xyzbit/claude-plugins/architect-manage-progressgit clone --depth 1 https://github.com/xyzbit/claude-pluginsWrote 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/xyzbit/claude-plugins/architect-manage-progress)<a href="https://agentmods.dev/commands/xyzbit/claude-plugins/architect-manage-progress"><img src="https://agentmods.dev/badge/commands/xyzbit/claude-plugins/architect-manage-progress.svg" alt="Measured on agentmods" 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 | $0.00024 | $0.03295 |
| Opus 5 | $0.00012 | $0.01648 |
| Sonnet 5 | $0.00005 | $0.00659 |
| Haiku 4.5 | $0.00002 | $0.00330 |
Grade A, and why
architect:manage-progress 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 4d 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 — 540 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/architect:manage-progress
This command manages progress tracking and documentation publishing for the Senior Architect Collaboration workflow. It monitors task completion, tracks phase status, and exports to various documentation systems.
Usage
Interactive Mode (Recommended)
/architect:manage-progress
Interactive prompts for progress tracking and publishing.
Track Progress
/architect:manage-progress --status
Export Documentation
/architect:manage-progress --export markdown --project "E-commerce Platform"
Publish to Documentation System
/architect:manage-progress --publish confluence --url "https://wiki.company.com" --project "E-commerce Platform"
Arguments
-
--project <name>: Project name for progress tracking -
--export <format>: Export formatmarkdown: Markdown format (default)json: JSON format for programmatic usepdf: PDF reporthtml: HTML reportcsv: CSV for spreadsheets
-
--publish <system>: Documentation systemconfluence: Atlassian Confluencegitbook: GitBookwiki: Generic wikigithub: GitHub Wikinotion: Notion workspaceslack: Slack channel summary
-
--url <url>: Documentation system URL -
--status: Show current progress status -
--report: Generate progress report -
--update: Update task status (interactive) -
--help: Show help information
Examples
Example 1: View Progress Status
/architect:manage-progress --status
Output:
📊 Project Progress: User Authentication System
Phase Status:
┌────────────────────────────────────────┬──────────┬────────────┐
│ Phase │ Status │ Progress │
├────────────────────────────────────────┼──────────┼────────────┤
│ 1. Requirements Analysis │ ✅ Done │ 100% (6/6) │
│ 2. Technical Design │ ✅ Done │ 100% (6/6) │
│ 3. Task Breakdown │ 🔄 Active│ 60% (6/10)│
│ 4. Feature Development │ ⏳ Pending│ 0% (0/12)│
└────────────────────────────────────────┴──────────┴────────────┘
Task Summary:
- Total Tasks: 28
- Completed: 12 (43%)
- In Progress: 6 (21%)
- Pending: 10 (36%)
Current Sprint:
- Sprint: 2024-W3
- Tasks Completed This Sprint: 3/8
- Velocity: 5.2 tasks/sprint
Workload Distribution:
核心功能: ████████████ 100% (12/12)
辅助功能: ██████ 50% (3/6)
扩展功能: █ 10% (1/10)
Next Milestone: Phase 3 Complete (ETA: 2024-01-20)
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.
- 4d ago First seen · 540 lines · 24 tokens per session scan A 1627768a2a34
architect:manage-progress is a command published in the GitHub repository xyzbit/claude-plugins (27 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 24 tokens to every session and 3,295 once invoked, about $0.0001 per session on Opus 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-08-30.
Other commands, from other repositories
project-recap
Generate a visual project recap for context switching.
os-meeting
快速创建和管理AI团队会议.
workspace
Testany Workspace, 管理工作空间，成员权限，团队组织.
standup
Show a daily standup summary with completed, in-progress, and blocked tasks across all active epics.
m-task-planner
Target: $ARGUMENTS (Default: requirement document(s) discovered in the project).
triage-issues
Launch the Issue Triage Agent (Haiku) to categorize and prioritize GitHub issues.