agent-library: Command for Claude Code

.gemini/commands/speckit/speckit.plan.toml

speckit.plan is a command for Claude Code, Gemini CLI from bl1nk-bot/agent-library. It costs 0 tokens per session (767 once invoked), scanned A, a copy of speckit.plan, CC0-1.0.

A command that creates a technical implementation plan from a feature specification and the project's engineering rules. The plan covers the technology choices, structure, design decisions, and checks needed before coding.

In plain words
What is it for?
Use it after writing a feature specification and before creating tasks or starting implementation.
Why use it?
It turns requirements into a concrete build approach and highlights unknowns or rule violations early. This gives implementation work a defined technical direction.

Command for Claude CodeGemini CLI

Written for Claude Code and Gemini CLI: $ARGUMENTS substitution, but also installed under .gemini/.

This is bl1nk-bot/agent-library's own configuration. It tells Claude Code and Gemini CLI how to work on agent-library 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 agent-library configures →

Reuse

Borrowing it

Nothing to install: this file belongs to bl1nk-bot/agent-library. 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/bl1nk-bot/agent-library/main/.gemini/commands/speckit/speckit.plan.toml
Clone the repo
git clone --depth 1 https://github.com/bl1nk-bot/agent-library

Made for: Claude Code, Gemini CLI.

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

README.md
[![agentmods](https://agentmods.dev/badge/commands/bl1nk-bot/agent-library/speckit.plan.svg)](https://agentmods.dev/commands/bl1nk-bot/agent-library/speckit.plan)
Your own site
<a href="https://agentmods.dev/commands/bl1nk-bot/agent-library/speckit.plan"><img src="https://agentmods.dev/badge/commands/bl1nk-bot/agent-library/speckit.plan.svg" alt="Measured on agentmods" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 767 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 89% 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.00000 $0.00767
Opus 5 $0.00000 $0.00383
Sonnet 5 $0.00000 $0.00153
Haiku 4.5 $0.00000 $0.00077

Measured 2d ago against content hash 324e2b3edc2f, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

speckit.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 2d 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

89% identical to speckit.plan — 8 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.

.gemini/commands/speckit/speckit.plan.toml · 94 lines

How it starts

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

description = "Execute the implementation planning workflow using the plan template to generate design artifacts."

prompt = """

description: Execute the implementation planning workflow using the plan template to generate design artifacts. handoffs:

  • label: Create Tasks agent: speckit.tasks prompt: Break the plan into tasks send: true
  • label: Create Checklist agent: speckit.checklist prompt: Create a checklist for the following domain...

User Input

$ARGUMENTS

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

Outline

  1. Setup: Run .specify/scripts/powershell/setup-plan.ps1 -Json from repo root and parse JSON for FEATURE_SPEC, IMPL_PLAN, SPECS_DIR, BRANCH. 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 context: Read FEATURE_SPEC and .specify/memory/constitution.md. Load IMPL_PLAN template (already copied).

  3. Execute plan workflow: Follow the structure in IMPL_PLAN template to:

    • Fill Technical Context (mark unknowns as "NEEDS CLARIFICATION")
    • Fill Constitution Check section from constitution
    • Evaluate gates (ERROR if violations unjustified)
    • Phase 0: Generate research.md (resolve all NEEDS CLARIFICATION)
    • Phase 1: Generate data-model.md, contracts/, quickstart.md
    • Phase 1: Update agent context by running the agent script
    • Re-evaluate Constitution Check post-design
  4. Stop and report: Command ends after Phase 2 planning. Report branch, IMPL_PLAN path, and generated artifacts.

Phases

Phase 0: Outline & Research

  1. Extract unknowns from Technical Context above:

    • For each NEEDS CLARIFICATION → research task
    • For each dependency → best practices task
    • For each integration → patterns task
  2. Generate and dispatch research agents:

    For each unknown in Technical Context:
      Task: "Research {unknown} for {feature context}"
    For each technology choice:
      Task: "Find best practices for {tech} in {domain}"
    

Read the full file on GitHub · 94 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. 2d ago First seen · 94 lines · 0 tokens per session scan A 324e2b3edc2f

Subscribe to this mod's changes

speckit.plan is a command published in the GitHub repository bl1nk-bot/agent-library (2 stars, last pushed 2d ago), licensed CC0-1.0. It costs nothing until one of its globs matches a file; then it loads 767 tokens. A static security scan graded it A with 0 findings. It is 89% identical to speckit.plan, differing in 8 lines, and is treated as a copy.