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-create-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-create-plan)<a href="https://agentmods.dev/skills/mhylle/claude-skills-collection/tt-create-plan"><img src="https://agentmods.dev/badge/skills/mhylle/claude-skills-collection/tt-create-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-create-plan"><img src="https://agentmods.dev/badge/skills/mhylle/claude-skills-collection/tt-create-plan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Memory Poisoning · line 265 Skill manipulates agent memory, state, or stored context. Memory corruption can alter personality, override safety rules, or cause unpredictable behavior.Fix: Protect agent memory and state from modification by untrusted content. Use read-only memory for critical instructions and validate all state changes.
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.00233 | $0.03913 |
| Opus 5 | $0.00117 | $0.01956 |
| Sonnet 5 | $0.00047 | $0.00783 |
| Haiku 4.5 | $0.00023 | $0.00391 |
Grade A, and why
tt-create-plan scanned grade A with 1 finding 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 11d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- Manual: hit endpoint with curl, confirm 200/401 contract. How it starts
The opening of the file, as written. The whole thing — 353 lines — stays where its author put it; the contents beside it link to each section on GitHub.
tt-create-plan
Tasktracker-native implementation planning. Walks the four lifecycle stages (brainstorm → requirements → architecture → plan) and lands the plan as phase tasks in tasktracker, with each task linked to the requirement it implements and architecture components registered for the structural pieces. No docs/plans/*.md file is written — the plan is the task tree.
How this differs from /create-plan
/create-plan |
/tt-create-plan (this skill) |
|
|---|---|---|
| Output | docs/plans/YYYY-MM-DD-*.md file + Tasks |
Phase tasks in tasktracker (no file) |
| Requirements | Free text under "Context" | First-class Requirement rows with AcceptanceCriterion |
| Architecture | Implicit, narrative | ArchitectureComponent + ArchitectureRelationship rows |
| Phase scaffolding | Hand-written checklists | createPhaseFromTemplate with rituals embedded |
| Phase body | Editable markdown | Locked once children exist (immutable scope contract) |
| Progress gate | TaskList | getProjectReadiness per lifecycle stage |
| Plan/spec separation | "checkboxes in markdown" | Spec on phase task, progress on sub-tasks |
If the user is not using tasktracker, use /create-plan instead.
Workflow
Step 0: Establish project + lifecycle context (MANDATORY)
1. tasktracker_listProjects({search: "<topic-keywords>"})
- Use the user's words. The most common failure mode is creating a
duplicate project because you couldn't find the existing one.
- If the user already had a /tt-brainstorm session, the project from
that session is the one to use.
2. tasktracker_getProjectReadiness({projectId})
- This 4-row table is the ground truth for "what stage are we in".
- If `brainstorm` is in-progress or not started, STOP and tell the
user — they probably want /tt-brainstorm first. Don't paper over
a missing brainstorm; the requirements end up shaky.
3. tasktracker_getPrinciples({projectId, includeGlobal: true})
- Surface conflicts before design, not after.
4. Find the first non-satisfied lifecycle phase task and
tasktracker_setActiveTask(<that-task-id>).
For a typical create-plan flow, this is the requirements-lifecycle
phase. setActiveTask folds principles + acceptance criteria + the
hierarchical requirement link into the digest you'll work from.
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.
- 11d ago First seen · 353 lines · 233 tokens per session scan A f86cece5ace8
tt-create-plan is a skill published in the GitHub repository mhylle/claude-skills-collection (18 stars, last pushed 8d ago), licensed MIT. It adds 233 tokens to every session and 3,913 once invoked, about $0.0012 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). 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.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.