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 Hadi99K/AGENT_SKILLS --skill wrap-phasegit clone --depth 1 https://github.com/Hadi99K/AGENT_SKILLSWrote 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/hadi99k/agent_skills/wrap-phase)<a href="https://agentmods.dev/skills/hadi99k/agent_skills/wrap-phase"><img src="https://agentmods.dev/badge/skills/hadi99k/agent_skills/wrap-phase.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.00024 | $0.00395 |
| Opus 5 | $0.00012 | $0.00198 |
| Sonnet 5 | $0.00005 | $0.00079 |
| Haiku 4.5 | $0.00002 | $0.00040 |
Grade A, and why
wrap-phase 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
What I do
- Read
AGENT_SYNC.mdto understand the completed work. - Add a Phase Summary highlighting everything built and key technical fixes.
- Clean the Handoff Log by deleting all older conversations and keeping ONLY the single most recent log.
- Clear completed tasks from the Session Task Board.
- Update the Current Phase status to reflect completion.
- Stage, commit, and push the
AGENT_SYNC.mdfile automatically.
When to use me
Use this when the user asks to "wrap up the phase", "wrap the phase", or "clean up AGENT_SYNC".
Execution Steps
When invoked, execute the following steps without needing further confirmation:
- Analyze: Read
AGENT_SYNC.mdto grasp all recent sub-tasks and the handoff logs. - Summarize: Create a clear
## 📖 Phase Summary: [Feature Name]section under the task board summarizing the accomplishments. - Clean: Remove all
[x]completed items from## 📋 Session Task Board. Replace them with a note like "All completed." - Purge: Delete all older handoff messages under
## 💬 Handoff & Discussion LogEXCEPT for the single most recent one. - Update State: Change the "Current Phase" in the state section to indicate completion (e.g., "[Phase Name] Complete ✅").
- Save & Commit: Write the updated file to disk, then use
bashto run:git add AGENT_SYNC.md && git commit -m "docs: wrap phase - clean agent sync and add phase summary" && git push
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 · 33 lines · 24 tokens per session scan A 2d3cdff8acf2
wrap-phase is a skill published in the GitHub repository Hadi99K/AGENT_SKILLS (2 stars, last pushed 4mo ago), licensed MIT. It adds 24 tokens to every session and 395 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
audit-trail
Full traceability from PRD to code commit through the CCPM spec-driven pipeline.
issue-tracking
Track beads as git-backed issues with persistent attribution, supporting Gas Town's bead lifecycle and convoy progress monitoring.
friction-log
File contributor or agent papercuts as GitHub issues labeled friction, or investigate those issues as the daily friction-log Cloud Agent. Use when you hit repo friction, when asked to log friction, or when spawned to resolve open friction issues.
split-and-ship
Execute an approved split plan, shipping each change group separately as its own branch and PR or as sequential commits on the current branch. Use when the user asks to "split and ship", "ship the split plan", "create separate PRs", or "split changes into branches".
to-tickets
A workflow for turning a written plan or specification into separate GitHub issues, with each issue covering one independently finishable piece of work.
git-workflow
Branching strategies, conventional commits, PR templates, and merge vs rebase guidance. Activate when starting features, creating PRs, or managing releases.