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 SisyphusSQ/harness-template --skill project-plan-archivegit clone --depth 1 https://github.com/SisyphusSQ/harness-templateWrote 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/sisyphussq/harness-template/project-plan-archive)<a href="https://agentmods.dev/skills/sisyphussq/harness-template/project-plan-archive"><img src="https://agentmods.dev/badge/skills/sisyphussq/harness-template/project-plan-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/sisyphussq/harness-template/project-plan-archive"><img src="https://agentmods.dev/badge/skills/sisyphussq/harness-template/project-plan-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.00041 | $0.00529 |
| Opus 5.5 | $0.00016 | $0.00212 |
| Sonnet 5.5 | $0.00008 | $0.00106 |
| Haiku 4.5 | $0.00004 | $0.00053 |
Grade A, and why
project-plan-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 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.
What it actually says
计划归档
读取工作项目的 AGENTS.md、.agents/PLANS.md 和候选计划。用户当前请求与已有授权优先，不重复请求已获得的归档授权。
把 SKILL_ROOT 设置为本次读取的 SKILL.md 所在绝对目录；共享插件与仓库副本都从这个位置调用脚本，--repo 指向工作项目。
python3 "$SKILL_ROOT/scripts/project_plan_archive.py" inspect --repo "$PWD" --json
python3 "$SKILL_ROOT/scripts/project_plan_archive.py" archive --repo "$PWD" --done-issue APP-123 --json
python3 "$SKILL_ROOT/scripts/project_plan_archive.py" archive --repo "$PWD" --done-issue APP-123 --write --json
先核对 Issue provider 的完成证据，再传 --done-issue。当前字段是 issue_id；已有 execution_issue/master_issue 仍可读取，优先顺序为 issue_id、execution_issue、master_issue。
没有 Issue 的计划默认进入 skipped_missing_issue。只有已经从用户指令或计划结果核实完成时，使用具体相对路径：
python3 "$SKILL_ROOT/scripts/project_plan_archive.py" archive --repo "$PWD" \
--done-plan .agents/plans/2026-09-12-example.md --json
预览后在已有授权范围内添加 --write 执行，不因 dry-run 再增加审批。--done-plan 不能绕过已有 Issue 的完成要求。
边界
- 只处理 .agents/plans/ 根级带日期的 Markdown；模板、示例、未完成和无法核实的计划保留。
- 目标为 .agents/plans/completed/<ISO周>/<原文件名>，目标已存在时跳过。
- 精确修复 Git 跟踪文本及本地 state/runs Markdown 中的旧路径；不改二进制或越界符号链接。
- 脚本不连接或修改 Issue 系统；Git 引用清单无法读取时停止，不能宣称引用已全部修复。
- 写入后核对实际移动和引用结果；仅运行改动需要的检查，交付收尾复用已有验证。
What ships with it
2 files 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.
- 1mo ago Changed · -28 lines · -8 tokens per session 25ba91688620
- 2mo ago First seen · 64 lines · 49 tokens per session scan A d1f9491837e9
project-plan-archive is a skill published in the GitHub repository SisyphusSQ/harness-template (11 stars, last pushed 1mo ago), licensed MIT. It adds 41 tokens to every session and 529 once invoked, about $0.0002 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-08-30.
Other skills, from other repositories
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…
remove
Remove a deployed framework or addon from the current workspace.