speckit.tinyspec

speckit.tinyspec is a command for Claude Code from opsmill/infrahub-mcp. It costs 16 tokens per session (938 once invoked), scanned A, a copy of speckit.tinyspec.tinyspec, Apache-2.0.

A lightweight specification command that puts the context, requirements, implementation plan, and tasks for a small change into one file.

In plain words
What is it for?
Use it for a focused feature, bug fix, interface tweak, configuration change, or small refactor affecting a few files.
Why use it?
It adds enough structure to clarify a small task without the overhead of a full software-design process.

Command for Claude Code

Written for Claude Code: $ARGUMENTS substitution.

Good fit Use it for a focused feature, bug fix, interface tweak, configuration change, or small refactor affecting a few files.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/opsmill/infrahub-mcp/speckit.tinyspec
Install

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.

Clone the repo
git clone --depth 1 https://github.com/opsmill/infrahub-mcp

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

README.md
[![agentmods](https://agentmods.dev/badge/commands/opsmill/infrahub-mcp/speckit.tinyspec/github.svg)](https://agentmods.dev/commands/opsmill/infrahub-mcp/speckit.tinyspec)
Your own site
<a href="https://agentmods.dev/commands/opsmill/infrahub-mcp/speckit.tinyspec"><img src="https://agentmods.dev/badge/commands/opsmill/infrahub-mcp/speckit.tinyspec/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.

agentmods 80×15 button for speckit.tinyspec

Your own site · 80×15
<a href="https://agentmods.dev/commands/opsmill/infrahub-mcp/speckit.tinyspec"><img src="https://agentmods.dev/badge/commands/opsmill/infrahub-mcp/speckit.tinyspec.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 16 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 938 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 95% 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.00016 $0.00938
Opus 5 $0.00008 $0.00469
Sonnet 5 $0.00003 $0.00188
Haiku 4.5 $0.00002 $0.00094

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

Security

Grade A, and why

speckit.tinyspec 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 5d 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

95% identical to speckit.tinyspec.tinyspec — 7 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.

.specify/extensions/tinyspec/commands/speckit.tinyspec.md · 109 lines

How it starts

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

TinySpec

Generate a single lightweight specification file for small tasks that don't warrant the full SDD workflow. Combines context, requirements, implementation plan, and tasks into one concise document — minimal overhead, maximum clarity.

User Input

$ARGUMENTS

You MUST consider the user input before proceeding (if not empty). The user describes the small change they want to make (e.g., "add a logout button to the navbar", "fix the date format in the invoice PDF", "add input validation to the signup form").

Prerequisites

  1. Verify a spec-kit project exists by checking for .specify/ directory
  2. Verify git is available and the project is a git repository
  3. Verify the user has described the change (if not, ask what they want to build)

Outline

  1. Assess scope: Quickly evaluate whether this task is appropriate for tinyspec:

    • Good fit: Single feature, bug fix, UI tweak, config change, small refactor — anything that touches 1-5 files and takes under ~1 hour
    • Bad fit: Multi-module features, architectural changes, new services, database schema redesigns — recommend full /speckit.specify instead
    • If the task seems too large, warn the user and suggest the full workflow
  2. Identify affected files: Scan the codebase to determine:

    • Which files will be modified (list them explicitly)
    • Which files provide context (imports, types, related components)
    • Which test files will need updates
  3. Generate tinyspec file: Create a single file at specs/tiny/{feature-name}.md with this structure:

    # TinySpec: {Title}
    
    **Branch**: {current-branch or new-branch-name}
    **Date**: {YYYY-MM-DD}
    **Status**: draft
    **Complexity**: small
    
    ## What
    
    {1-3 sentence description of what this change does and why}
    
    ## Context
    
    | File | Role |
    |------|------|
    | `src/components/Navbar.tsx` | Will be modified — add logout button |
    | `src/hooks/useAuth.ts` | Context — provides logout function |
    | `src/components/Navbar.test.tsx` | Will be modified — add test for logout |
    
    ## Requirements
    
    1. {Requirement 1 — clear, testable}
    2. {Requirement 2}
    3. {Requirement 3}
    
    ## Plan
    
    1. {Step 1 — what to change and where}
    2. {Step 2}
    3. {Step 3}
    
    ## Tasks
    
    - [ ] {Task 1}
    - [ ] {Task 2}
    - [ ] {Task 3}
    - [ ] {Test task}
    
    ## Done When
    
    - [ ] All tasks checked off
    - [ ] Tests pass
    - [ ] No lint errors
    

Read the full file on GitHub · 109 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. 5d ago First seen · 109 lines · 16 tokens per session scan A 0ce1cd033ff7

Subscribe to this mod's changes

speckit.tinyspec is a command published in the GitHub repository opsmill/infrahub-mcp (10 stars, last pushed 2d ago), licensed Apache-2.0. It adds 16 tokens to every session and 938 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 95% identical to speckit.tinyspec.tinyspec, differing in 7 lines, and is treated as a copy.