playfab-mcp-server: Command for Claude Code

.claude/commands/speckit.tasks.md

speckit.tasks is a command for Claude Code from akiojin/playfab-mcp-server. It costs 31 tokens per session (1,449 once invoked), scanned A, a copy of speckit.tasks, MIT.

A command that creates an execution plan in tasks.md from available feature documents such as the specification and technical plan. The file lists implementation tasks in dependency order and groups them by user story.

In plain words
What is it for?
Use it after preparing feature documents to generate implementation tasks for each user story, including setup, data, API, and testing work when those documents provide it.
Why use it?
It converts design decisions into work that developers can carry out and track. It also accounts for available data models, API contracts, research, and test scenarios.

Command for Claude Code

Written for Claude Code: $ARGUMENTS substitution.

This is akiojin/playfab-mcp-server's own configuration. It tells Claude Code how to work on playfab-mcp-server itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything playfab-mcp-server configures →

Reuse

Borrowing it

Nothing to install: this file belongs to akiojin/playfab-mcp-server. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/akiojin/playfab-mcp-server/main/.claude/commands/speckit.tasks.md
Clone the repo
git clone --depth 1 https://github.com/akiojin/playfab-mcp-server

Made for: Claude Code.

Wrote 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.

agentmods badge for speckit.tasks

README.md
[![agentmods](https://agentmods.dev/badge/commands/akiojin/playfab-mcp-server/speckit.tasks.svg)](https://agentmods.dev/commands/akiojin/playfab-mcp-server/speckit.tasks)
Your own site
<a href="https://agentmods.dev/commands/akiojin/playfab-mcp-server/speckit.tasks"><img src="https://agentmods.dev/badge/commands/akiojin/playfab-mcp-server/speckit.tasks.svg" alt="Measured on agentmods" height="20"></a>
Per session 31 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,449 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 88% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00031 $0.01449
Opus 5 $0.00015 $0.00724
Sonnet 5 $0.00006 $0.00290
Haiku 4.5 $0.00003 $0.00145

Measured 8d ago against content hash e72e2a67d33d, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

speckit.tasks 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.

Origin

This is a copy

88% identical to speckit.tasks — 13 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.claude/commands/speckit.tasks.md · 129 lines

How it starts

The opening of the file, as written. The whole thing — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.

User Input

$ARGUMENTS

You MUST consider the user input before proceeding (if not empty).

Outline

  1. Setup: Run .specify/scripts/bash/check-prerequisites.sh --json from repo root and parse FEATURE_DIR and AVAILABLE_DOCS list. All paths must be absolute. For single quotes in args like "I'm Groot", use escape syntax: e.g 'I'''m Groot' (or double-quote if possible: "I'm Groot").

  2. Load design documents: Read from FEATURE_DIR:

    • Required: plan.md (tech stack, libraries, structure), spec.md (user stories with priorities)
    • Optional: data-model.md (entities), contracts/ (API endpoints), research.md (decisions), quickstart.md (test scenarios)
    • Note: Not all projects have all documents. Generate tasks based on what's available.
  3. Execute task generation workflow:

    • Load plan.md and extract tech stack, libraries, project structure
    • Load spec.md and extract user stories with their priorities (P1, P2, P3, etc.)
    • If data-model.md exists: Extract entities and map to user stories
    • If contracts/ exists: Map endpoints to user stories
    • If research.md exists: Extract decisions for setup tasks
    • Generate tasks organized by user story (see Task Generation Rules below)
    • Generate dependency graph showing user story completion order
    • Create parallel execution examples per user story
    • Validate task completeness (each user story has all needed tasks, independently testable)
  4. Generate tasks.md: Use .specify.specify/templates/tasks-template.md as structure, fill with:

    • Correct feature name from plan.md
    • Phase 1: Setup tasks (project initialization)
    • Phase 2: Foundational tasks (blocking prerequisites for all user stories)
    • Phase 3+: One phase per user story (in priority order from spec.md)
    • Each phase includes: story goal, independent test criteria, tests (if requested), implementation tasks
    • Final Phase: Polish & cross-cutting concerns
    • All tasks must follow the strict checklist format (see Task Generation Rules below)
    • Clear file paths for each task
    • Dependencies section showing story completion order
    • Parallel execution examples per story
    • Implementation strategy section (MVP first, incremental delivery)

Read the full file on GitHub · 129 lines

Changes

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.

  1. 8d ago First seen · 129 lines · 31 tokens per session scan A e72e2a67d33d

Subscribe to this mod's changes

speckit.tasks is a command published in the GitHub repository akiojin/playfab-mcp-server (3 stars, last pushed today), licensed MIT. It adds 31 tokens to every session and 1,449 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 88% identical to speckit.tasks, differing in 13 lines, and is treated as a copy.