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.
git clone --depth 1 https://github.com/loulanyue/spec-kit-zhWrote 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.
[](https://agentmods.dev/commands/loulanyue/spec-kit-zh/speckit.myext.myextcmd)<a href="https://agentmods.dev/commands/loulanyue/spec-kit-zh/speckit.myext.myextcmd"><img src="https://agentmods.dev/badge/commands/loulanyue/spec-kit-zh/speckit.myext.myextcmd/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.
<a href="https://agentmods.dev/commands/loulanyue/spec-kit-zh/speckit.myext.myextcmd"><img src="https://agentmods.dev/badge/commands/loulanyue/spec-kit-zh/speckit.myext.myextcmd.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00011 | $0.00164 |
| Opus 5.5 | $0.00004 | $0.00066 |
| Sonnet 5.5 | $0.00002 | $0.00033 |
| Haiku 4.5 | $0.00001 | $0.00016 |
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 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.
This is a copy
100% identical to speckit.myext.myextcmd — 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.
What it actually says
You are following a customized version of the myext extension's myextcmd command.
When executing this command:
- Read the user's input from $ARGUMENTS
- Follow the standard myextcmd workflow
- 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.
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.
- 14d ago First seen · 21 lines · 11 tokens per session scan A fa5c348453ac
speckit.myext.myextcmd is a command published in the GitHub repository loulanyue/spec-kit-zh (337 stars, last pushed 13d ago), licensed MIT. It adds 11 tokens to every session and 164 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to speckit.myext.myextcmd, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
ijfw-status
Show IJFW state -- mode, routing, memory, recent activity, codebase index, settings. Use when you want the at-a-glance banner you'd otherwise get at session start.
team
Manage your project's agent team. Usage: /team [setup|list|add|remove|swap].
workflow
Start or resume the IJFW project workflow. Usage: /workflow [discover|plan|execute|verify|ship|status].
implementation-plan
Define an incremental plan for the active task as IMPLEMENTATIONPLAN.md plus a TASKSTATE.md update: smallest safe slices with scope, validation and exit criteria. No code is written. A --spec mode derives slices from a spec or PRD. A retrofit mode annotates in-progress plans so they can adopt implement-fleet. Do not…
slice-closure
Decide whether the current slice is ready to close, separating slice completion from task completion, and record the result in slice notes and TASKSTATE.md. Use when a slice was implemented, validated or reviewed and may be ready to close. Do not use before slice implementation, during planning, or for overall task…
task-close
Close a whole finished task: verify the spec done-conditions, set TASKSTATE.md to its final closed state, and move the folder from active/ to archive/. Use when all slices are closed, the work is merged or explicitly waived, and the task is ending. Do not use for one slice (use slice-closure), unfinished work…