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 skills add papperrollinggery/zhijuan-codex-agency-chief-of-staf --skill agency-discuss-plan-execute-progress-archivegit clone --depth 1 https://github.com/papperrollinggery/zhijuan-codex-agency-chief-of-stafWrote 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/skills/papperrollinggery/zhijuan-codex-agency-chief-of-staf/agency-discuss-plan-execute-progress-archive)<a href="https://agentmods.dev/skills/papperrollinggery/zhijuan-codex-agency-chief-of-staf/agency-discuss-plan-execute-progress-archive"><img src="https://agentmods.dev/badge/skills/papperrollinggery/zhijuan-codex-agency-chief-of-staf/agency-discuss-plan-execute-progress-archive/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/skills/papperrollinggery/zhijuan-codex-agency-chief-of-staf/agency-discuss-plan-execute-progress-archive"><img src="https://agentmods.dev/badge/skills/papperrollinggery/zhijuan-codex-agency-chief-of-staf/agency-discuss-plan-execute-progress-archive.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.00038 | $0.00370 |
| Opus 5 | $0.00019 | $0.00185 |
| Sonnet 5 | $0.00008 | $0.00074 |
| Haiku 4.5 | $0.00004 | $0.00037 |
Grade A, and why
agency-discuss-plan-execute-progress-archive 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 5d 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.
What it actually says
Agency Project Lifecycle Discovery Bridge
This is a discovery-only bridge for hosts that trim Skill descriptions or later-sorted Skill names from a large catalog.
Match the requested action, not isolated words. Asking for a team or progress alone does not authorize a new Task/Thread, persistent plan, or archive. A request to analyze and finish work continues through execution; only an explicit discussion-only or plan-only boundary stops at that phase.
For a matched lifecycle request, make the phase status the first user-visible line before any other commentary, explanation, tool call, or lookup. In Discussion the exact line is 任务已接管｜需求讨论中. If the host requires a Skill-use notice, put it after that line in the same message; never send a separate notice first. Do not inspect a source task, conversation history, memory, project files, or Git merely because the host supplied a delegation envelope; unless the user explicitly requests current material, treat missing context as the one open question.
When the request genuinely needs a staged project lifecycle, read ../agency-chief-of-staff/SKILL.md completely once and follow that canonical Skill. The canonical Skill owns every lifecycle decision and user-visible status. Do not invoke this bridge again from the canonical flow.
Do not use this bridge for ordinary questions, one-line translation, a simple code edit, an explicit single-file fix, a valid AGENCY_WORKER packet, a mere mention of thread or release readiness, or maintenance of the Agency Chief of Staff source repository.
Do not create plans, files, tasks, Agents, or Threads from this bridge itself.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 5d ago Changed · +2 lines d5a1b20c97c1
- 7d ago Changed · -195 tokens per session ffd11ae38159
- 12d ago First seen · 17 lines · 233 tokens per session scan A 7b1d2c2a1b75
agency-discuss-plan-execute-progress-archive is a skill published in the GitHub repository papperrollinggery/zhijuan-codex-agency-chief-of-staf (2 stars, last pushed 7d ago), licensed MIT. It adds 38 tokens to every session and 370 once invoked, about $0.0002 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-31.
Other skills, from other repositories
kanban-orchestrator
Kanban orchestrator: decompose, route, verify. No executing.
studio-goal-progress
Use when a KIT-managed Codex or Hermes Goal needs evidence-backed percentage, ETA range, live read-only progress views, or portable append-only progress recovery.
simply-pm
Use when you are spawned as the PM of a simply harness project and your brief references a .simply/LEDGER.md work ledger or this skill. Grants fleet authority, routing doctrine, safe worker lifecycle, and the signal protocol back to the auditor.
prewalk
Use when the user wants a coding task executed with a strong planner model first and a faster/cheaper executor model after the first successful implementation edit.
project-engineering-strategy
Use when a software project needs durable cross-session governance for formal documents, WBS or tracker coordination, worktree delivery boundaries, evidence and acceptance states, handoffs, or architecture and design-document control.
team-dispatch
Turns a plan phase into a PhaseSpec v1 and dispatches it to a specialist subagent via the Agent tool. Subagent reads files itself, returns a structured result, the result is logged into progress.md. Markdown is the shared state; no in-memory shared store across agents.