Borrowing it
Nothing to install: this file belongs to hlalljie/agent-workflow-presets. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/hlalljie/agent-workflow-presets/main/.cursor/skills/phase-summary/SKILL.mdgit clone --depth 1 https://github.com/hlalljie/agent-workflow-presetsWrote 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/hlalljie/agent-workflow-presets/phase-summary)<a href="https://agentmods.dev/skills/hlalljie/agent-workflow-presets/phase-summary"><img src="https://agentmods.dev/badge/skills/hlalljie/agent-workflow-presets/phase-summary.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.1 | $0.00023 | $0.00300 |
| Opus 5 | $0.00012 | $0.00150 |
| Sonnet 5 | $0.00005 | $0.00060 |
| Haiku 4.5 | $0.00002 | $0.00030 |
Grade A, and why
phase-summary 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 8d 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
Phase Summary
When to use
At the end of every task loop, before proposing a commit. Never skip.
Output format
Print in the response (not just in the task file):
1-2 sentences describing what the phase delivered and why it matters.
| Check | How tested | Result |
|---|---|---|
| What was verified | unit test / tsc / API test / browser MCP / human |
PASS / FAIL |
If anything requires human verification, add:
Owner check (human):
- Specific thing to open or confirm
Then print: Ready to prepare commit proposal (y/n): and stop.
If owner says y → run the commit skill, which will propose the message and wait for a second approval before committing.
Rules
- "How tested" must be specific:
unit test,tsc --noEmit,API test,browser MCP, orhuman. Never leave it vague. - Keep the table short — one row per meaningful check, not one per file or function.
- If there is no human check needed, omit that section entirely. Do not write "none".
- Also write the summary into the
## Deliverablessection at the bottom of the task file.
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.
- 8d ago First seen · 37 lines · 23 tokens per session scan A cd751f38b595
phase-summary is a skill published in the GitHub repository hlalljie/agent-workflow-presets (2 stars, last pushed 2mo ago), licensed MIT. It adds 23 tokens to every session and 300 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-31.
Other skills, from other repositories
project
GitHub Issues as PLAN.md replacement — agents read/update them. Auto-invoke on issue-linked branches. Triggers "what's the plan", "project status", "sync with github", "close the issue".
pn-github-vertical-slices
Break a plan or PRD into tracer-bullet vertical slices and create GitHub Issues via GitHub MCP (official github/github-mcp-server). Dependencies first (AFK/HITL). Use after pn-writing-plans or pn-create-prd when work must ship as Issues.
git-advanced-workflows
Master advanced Git workflows including rebasing, cherry-picking, bisect, worktrees, and reflog to maintain clean history and recover from any situation. Use when managing complex Git histories, collaborating on feature branches, or troubleshooting repository issues.
workflow-patterns
Use this skill when implementing tasks according to Conductor's TDD workflow, handling phase checkpoints, managing git commits for tasks, or understanding the verification protocol.
block-no-verify-hook
Configure a PreToolUse hook to prevent AI agents from skipping git pre-commit hooks with --no-verify and other bypass flags. Use when setting up Claude Code projects that enforce commit quality gates.
work-unit-commits
Plan commits as reviewable work units. Trigger: implementation, commit splitting, chained PRs, or keeping tests and docs with code.