speckit.myext.myextcmd

A customized replacement for an extension command named myextcmd. It follows that command's normal workflow and adds compliance checks and audit-trail entries.

In plain words
What is it for?
Use it when the myext extension is installed and its command needs these custom rules. The file is a preset example that must be customized.
Why use it?
It lets a project apply extra review and record-keeping instructions whenever the original command is used.

Command

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.

agentmods
npx agentmods add commands/github/spec-kit/speckit.myext.myextcmd
Clone the repo
git clone --depth 1 https://github.com/github/spec-kit
Per session 11 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 164 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found 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 $0.00011 $0.00164
Opus 5 $0.00005 $0.00082
Sonnet 5 $0.00002 $0.00033
Haiku 4.5 $0.00001 $0.00016

Measured yesterday against content hash fa5c348453ac, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

speckit.myext.myextcmd 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.

presets/scaffold/commands/speckit.myext.myextcmd.md · 21 lines

What it actually says

You are following a customized version of the myext extension's myextcmd command.

When executing this command:

  1. Read the user's input from $ARGUMENTS
  2. Follow the standard myextcmd workflow
  3. Additionally, apply the following customizations from this preset:
    • Add compliance checks before proceeding
    • Include audit trail entries in the output

CUSTOMIZE: Replace the instructions above with your own. This file overrides the command that the "myext" extension provides. When this preset is installed, all agents (Claude, Gemini, Copilot, etc.) will use this version instead of the extension's original.

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. yesterday First seen · 21 lines · 11 tokens per session scan A fa5c348453ac

Subscribe to this mod's changes

speckit.myext.myextcmd is a command published in the GitHub repository github/spec-kit (132,298 stars, last pushed 3d ago), licensed MIT. It adds 11 tokens to every session and 164 once invoked, about $0.0001 per session on Opus 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-08-30.

Related

Other commands, from other repositories