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 mhylle/claude-skills-collection --skill tt-implement-plangit clone --depth 1 https://github.com/mhylle/claude-skills-collectionWrote 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/mhylle/claude-skills-collection/tt-implement-plan)<a href="https://agentmods.dev/skills/mhylle/claude-skills-collection/tt-implement-plan"><img src="https://agentmods.dev/badge/skills/mhylle/claude-skills-collection/tt-implement-plan/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/mhylle/claude-skills-collection/tt-implement-plan"><img src="https://agentmods.dev/badge/skills/mhylle/claude-skills-collection/tt-implement-plan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00243 | $0.04887 |
| Opus 5 | $0.00121 | $0.02443 |
| Sonnet 5 | $0.00049 | $0.00977 |
| Haiku 4.5 | $0.00024 | $0.00489 |
Grade A, and why
tt-implement-plan 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 7d 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.
How it starts
The opening of the file, as written. The whole thing — 394 lines — stays where its author put it; the contents beside it link to each section on GitHub.
tt-implement-plan
Tasktracker-native orchestrator that executes a plan stored as phase tasks. It runs phases one at a time, honours active-task / locked-body / insight-logging conventions, and delegates the actual code work to /tt-implement-phase (which in turn delegates to subagents).
How this differs from /implement-plan
/implement-plan |
/tt-implement-plan (this skill) |
|
|---|---|---|
| Plan source | docs/plans/*.md + task_list_id |
Phase tasks in tasktracker (no file) |
| Progress tracking | TaskCreate/TaskUpdate (built-in) |
tasktracker_updateTaskStatus + active-task heartbeats |
| Active task discipline | None | setActiveTask + startTimer / pauseActiveTask / stopTimer / clearActiveTask — required |
| Phase body updates | Free edit | Forbidden once children exist — write to sub-tasks |
| Insight capture | Ad-hoc / lessons.md | logDefect, logLearning, logFriction |
| Multi-session resume | CLAUDE_CODE_TASK_LIST_ID=... |
Built-in: active task persists across MCP restarts |
| Completion criterion | All checkboxes ticked | All phase tasks completed AND no in-progress sub-tasks |
If the plan came from /create-plan (file-based), use /implement-plan. If the plan lives in tasktracker, use this skill.
CRITICAL: Orchestrator pattern (kept from /implement-plan)
THIS SESSION IS A PLAN-LEVEL ORCHESTRATOR. IT NEVER IMPLEMENTS CODE DIRECTLY — it walks phases and delegates each to
/tt-implement-phase. That holds in every environment. What varies is one level down:/tt-implement-phasewrites code via subagents when a subagent-dispatch tool exists, or in-context itself when none does (its graceful-degradation mode). Either way, this session's job is unchanged — drive the plan, never the code.
tt-implement-plan (this session — PLAN ORCHESTRATOR)
│
│ ⛔ NEVER writes code ⛔ NEVER uses Write/Edit (in EVERY mode)
│ (creates files only via tasktracker MCP calls)
│
└── tt-implement-phase (per-phase executor)
│
├── orchestrated mode → Subagents write code / create files / run tests
└── in-context mode → tt-implement-phase does it directly (no subagent tool)
What ships with it
3 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.
- 7d ago Changed · +6 lines 193037adc581
- 11d ago First seen · 388 lines · 243 tokens per session scan A 4bd2286eea4f
tt-implement-plan is a skill published in the GitHub repository mhylle/claude-skills-collection (18 stars, last pushed 8d ago), licensed MIT. It adds 243 tokens to every session and 4,887 once invoked, about $0.0012 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-30.
Other skills, from other repositories
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.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
remove
Remove a deployed framework or addon from the current workspace.