example

example is a command for Claude Code from loulanyue/spec-kit-zh. It costs 6 tokens per session (1,042 once invoked), scanned A, a copy of example, MIT.

An example command showing how a Spec Kit extension command can load settings, check requirements, and perform an action. Spec Kit is a toolkit for building software from written specifications.

In plain words
What is it for?
Use it when learning how to create or document commands for Spec Kit extensions.
Why use it?
It provides a template for understanding the parts a command may need, such as configuration, user input, and validation.

Command for Claude Code

Written for Claude Code: $ARGUMENTS substitution.

Good fit Use it when learning how to create or document commands for Spec Kit extensions.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/loulanyue/spec-kit-zh/example
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/loulanyue/spec-kit-zh

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 example

README.md
[![agentmods](https://agentmods.dev/badge/commands/loulanyue/spec-kit-zh/example/github.svg)](https://agentmods.dev/commands/loulanyue/spec-kit-zh/example)
Your own site
<a href="https://agentmods.dev/commands/loulanyue/spec-kit-zh/example"><img src="https://agentmods.dev/badge/commands/loulanyue/spec-kit-zh/example/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 example

Your own site · 80×15
<a href="https://agentmods.dev/commands/loulanyue/spec-kit-zh/example"><img src="https://agentmods.dev/badge/commands/loulanyue/spec-kit-zh/example.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 6 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,042 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.00006 $0.01042
Opus 5.5 $0.00002 $0.00417
Sonnet 5.5 $0.00001 $0.00208
Haiku 4.5 $0.00001 $0.00104

Measured 14d ago against content hash 4d23361bc7b3, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

example 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 14d 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 example — 0 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.

extensions/template/commands/example.md · 211 lines

How it starts

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

Example Command

This is an example command that demonstrates how to create commands for Spec Kit extensions.

Purpose

Describe what this command does and when to use it.

Prerequisites

List requirements before using this command:

  1. Prerequisite 1 (e.g., "MCP server configured")
  2. Prerequisite 2 (e.g., "Configuration file exists")
  3. Prerequisite 3 (e.g., "Valid API credentials")

User Input

$ARGUMENTS

Steps

Step 1: Load Configuration

Load extension configuration from the project:

``bash config_file=".specify/extensions/my-extension/my-extension-config.yml"

if [ ! -f "$config_file" ]; then echo "❌ Error: Configuration not found at $config_file" echo "Run 'specify extension add my-extension' to install and configure" exit 1 fi

Read configuration values

setting_value=$(yq eval '.settings.key' "$config_file")

Apply environment variable overrides

setting_value="${SPECKIT_MY_EXTENSION_KEY:-$setting_value}"

Validate configuration

if [ -z "$setting_value" ]; then echo "❌ Error: Configuration value not set" echo "Edit $config_file and set 'settings.key'" exit 1 fi

echo "📋 Configuration loaded: $setting_value" ``

Step 2: Perform Main Action

Describe what this step does:

``markdown Use MCP tools to perform the main action:

  • Tool: example-mcp-server example_tool
  • Parameters: { "key": "$setting_value" }

This calls the MCP server tool to execute the operation. ``

Step 3: Process Results

Process the results and provide output:

bash echo "" echo "✅ Command completed successfully!" echo "" echo "Results:" echo " • Item 1: Value" echo " • Item 2: Value" echo ""

Step 4: Save Output (Optional)

Save results to a file if needed:

``bash output_file=".specify/my-extension-output.json"

Read the full file on GitHub · 211 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. 14d ago Changed · -3 lines 4d23361bc7b3
  2. 1mo ago First seen · 214 lines · 6 tokens per session scan A 6d030ed86dfd

Subscribe to this mod's changes

example is a command published in the GitHub repository loulanyue/spec-kit-zh (337 stars, last pushed 13d ago), licensed MIT. It adds 6 tokens to every session and 1,042 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 95% identical to example, differing in 0 lines, and is treated as a copy.

Related

Other commands, from other repositories

ijfw-audit

Run the IJFW audit gate for the current workflow phase. Usage: /ijfw-audit [phase name].

FerroxLabs/ijfw · 28 tokens

ijfw-execute

Jump directly to the IJFW workflow Execute phase (Deep D4 / Quick Q3). Usage: /ijfw-execute [task or phase name].

FerroxLabs/ijfw · 36 tokens

ijfw-metrics

Show IJFW token / cost / session metrics over a time window. Reads .ijfw/metrics/sessions.jsonl via the ijfwmetrics MCP tool.

FerroxLabs/ijfw · 37 tokens

release-plan

Design a pre-deploy release and rollout strategy: pick the pattern (feature flag, canary, blue-green, or progressive delivery) by risk, then specify the exposure ramp, promotion metric and threshold, and rollback trigger. Designs the rollout, never executes it. Gated --godot-mobile and --godot-desktop modes plan a…

Mozurok/fhorja.dev · 0 tokens

code-locate

Locate code paths and line ranges for a described behavior: up to 10 candidates with HIGH/MEDIUM/LOW confidence and a search trail, plus a proposed SOURCEOFTRUTH.md update. Use when the first question is where one specific behavior lives and paths are unknown. Do not use when paths are explicit, the codebase is tiny…

Mozurok/fhorja.dev · 0 tokens

contract-signoff

Harden the current decision set into a normative source of truth with no residual ambiguity, saved in DECISIONS.md and TASKSTATE.md as reviewable edits. Use when decisions are resolved, the contract direction is stable, and wording needs hardening before planning or implementation. Do not use when major ambiguities…

Mozurok/fhorja.dev · 86 tokens