Borrowing it
Nothing to install: this file belongs to thunderkds/easy-ui-mcp. 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/thunderkds/easy-ui-mcp/main/.claude/skills/to-issues/SKILL.mdgit clone --depth 1 https://github.com/thunderkds/easy-ui-mcpWrote 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/thunderkds/easy-ui-mcp/to-issues)<a href="https://agentmods.dev/skills/thunderkds/easy-ui-mcp/to-issues"><img src="https://agentmods.dev/badge/skills/thunderkds/easy-ui-mcp/to-issues/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/thunderkds/easy-ui-mcp/to-issues"><img src="https://agentmods.dev/badge/skills/thunderkds/easy-ui-mcp/to-issues.svg" alt="Reviewed on agentmods" width="80" 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.00060 | $0.00746 |
| Opus 5.5 | $0.00024 | $0.00298 |
| Sonnet 5.5 | $0.00012 | $0.00149 |
| Haiku 4.5 | $0.00006 | $0.00075 |
Grade A, and why
to-issues 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 yesterday.
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 — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Role: Vertical-Slice Decomposer
You break a plan into independently-grabbable tasks using vertical slices (tracer bullets). This skill feeds Stage 2: its output becomes PROJECT_KANBAN.md rows and the tasks/TASK_GUIDE_Txxx.md files.
Karpathy Operational Commands (Specific Overrides)
- Simplicity First: Prefer many thin slices over few thick ones. Each slice delivers a narrow but COMPLETE path through every layer (schema, API, UI, tests).
- Goal-Driven Execution: Each slice must be demoable or verifiable on its own — define its acceptance criteria.
- Ask vs. Guess: Quiz the user on granularity and dependencies until they approve before generating guides.
Process
1. Gather context
Work from the approved Project Context Document, BRAINSTORMING_LOG.md direction, and PROJECT_SPEC.md. If the user passes a reference (issue/PRD/path), read it fully.
2. Explore the codebase (optional)
Understand the current state. Task titles/descriptions should use the project's domain vocabulary and respect ADRs in the area you touch.
3. Draft vertical slices
Break the plan into tracer-bullet tasks — thin vertical slices cutting through ALL layers end-to-end, NOT horizontal slices of one layer.
- Slices are HITL (need human interaction — architectural decision, design review) or AFK (implementable and mergeable without human interaction). Prefer AFK where possible.
- Each completed slice is demoable/verifiable on its own.
4. Quiz the user
Present a numbered list. For each slice show: Title, Type (HITL/AFK), Blocked by (dependencies), Complexity (C0–C3), Risk (Low/Med/High), Priority (P0–P2). Ask: Is the granularity right? Are the dependencies correct? Should any be merged/split? Iterate until approved.
5. Emit the task breakdown
For each approved slice, produce a task entry in dependency order (blockers first). This drives Stage 2's PROJECT_KANBAN.md rows and tasks/TASK_GUIDE_Txxx.md generation. Per-task body:
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.
- yesterday First seen · 53 lines · 60 tokens per session scan A 41c2c85ec8a9
to-issues is a skill published in the GitHub repository thunderkds/easy-ui-mcp (1 stars, last pushed today), licensed MIT. It adds 60 tokens to every session and 746 once invoked, about $0.0002 per session on Opus 5.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-10-30.
Other skills, from other repositories
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
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…
ring:mapping-feature-relationships
Mapping how features relate and phasing the work: categorizing PRD features, grouping them into domains, charting cross-feature journeys, dependencies, and integration points, and defining the binding Phases that plan.md mirrors one-to-one at Gate 7. Gate 2 of ring:planning-large-features; runs after…
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…