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 rules/hlalljie/agent-workflow-presets/phase-summarygit 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/rules/hlalljie/agent-workflow-presets/phase-summary)<a href="https://agentmods.dev/rules/hlalljie/agent-workflow-presets/phase-summary"><img src="https://agentmods.dev/badge/rules/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 | $0.00100 | $0.00100 |
| Opus 5 | $0.00050 | $0.00050 |
| Sonnet 5 | $0.00020 | $0.00020 |
| Haiku 4.5 | $0.00010 | $0.00010 |
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 3d 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
Before proposing a commit that closes out a task loop or phase, always run the phase-summary skill first. The summary must be printed in the response before the commit message appears.
Never jump straight to a commit proposal after finishing tasks — the owner must see what was done and how it was tested before approving a commit.
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.
- 3d ago First seen · 9 lines · 100 tokens per session scan A 18df0cc7db62
phase-summary is a cursor rule published in the GitHub repository hlalljie/agent-workflow-presets (2 stars, last pushed 1mo ago), licensed MIT. It adds 100 tokens to every session, about $0.0005 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 cursor rules, from other repositories
git-commit
Use this when the user asks for a git commit, commit message, or commit command.
git-authoring
Conventional Commit, pull-request, release-note, and PR-review conventions for this repository.
no-tool-contributors
Never add AI coding tools as contributors or co-authors.
commits
Commit message standards and conventions.
04-commit-style
Branch, commit, and PR conventions.
04-review-and-commit
Review, completion, and commit workflow.