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.
npx agentmods add agents/snowdreamtech/frp/speckit.git.featuregit clone --depth 1 https://github.com/snowdreamtech/frpWrote 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/agents/snowdreamtech/frp/speckit.git.feature)<a href="https://agentmods.dev/agents/snowdreamtech/frp/speckit.git.feature"><img src="https://agentmods.dev/badge/agents/snowdreamtech/frp/speckit.git.feature.svg" alt="Measured on agentmods" 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.00009 | $0.00764 |
| Opus 5 | $0.00005 | $0.00382 |
| Sonnet 5 | $0.00002 | $0.00153 |
| Haiku 4.5 | $0.00001 | $0.00076 |
Grade A, and why
speckit.git.feature 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.
Copies of this mod
6 near-identical copies found in the catalogue:
- speckit.git.feature — 100% identical, 6 lines differ
- speckit.git.feature — 100% identical, 6 lines differ
- speckit.git.feature — 100% identical, 6 lines differ
- speckit.git.feature — 100% identical, 6 lines differ
- speckit.git.feature — 100% identical, 0 lines differ
- speckit.git.feature — 100% identical, 6 lines differ
How it starts
The opening of the file, as written. The whole thing — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Feature Branch
Create and switch to a new git feature branch for the given specification. This command handles branch creation only — the spec directory and files are created by the core /speckit.specify workflow.
User Input
$ARGUMENTS
You MUST consider the user input before proceeding (if not empty).
Environment Variable Override
If the user explicitly provided GIT_BRANCH_NAME (e.g., via environment variable, argument, or in their request), pass it through to the script by setting the GIT_BRANCH_NAME environment variable before invoking the script. When GIT_BRANCH_NAME is set:
- The script uses the exact value as the branch name, bypassing all prefix/suffix generation
--short-name,--number, and--timestampflags are ignoredFEATURE_NUMis extracted from the name if it starts with a numeric prefix, otherwise set to the full branch name
Prerequisites
- Verify Git is available by running
git rev-parse --is-inside-work-tree 2>/dev/null - If Git is not available, warn the user and skip branch creation
Branch Numbering Mode
Determine the branch numbering strategy by checking configuration in this order:
- Check
.specify/extensions/git/git-config.ymlforbranch_numberingvalue - Check
.specify/init-options.jsonforbranch_numberingvalue (backward compatibility) - Default to
sequentialif neither exists
Execution
Generate a concise short name (2-4 words) for the branch:
- Analyze the feature description and extract the most meaningful keywords
- Use action-noun format when possible (e.g., "add-user-auth", "fix-payment-bug")
- Preserve technical terms and acronyms (OAuth2, API, JWT, etc.)
Run the appropriate script based on your platform:
- Bash:
.specify/extensions/git/scripts/bash/create-new-feature.sh --json --short-name "<short-name>" "<feature description>" - Bash (timestamp):
.specify/extensions/git/scripts/bash/create-new-feature.sh --json --timestamp --short-name "<short-name>" "<feature description>" - PowerShell:
.specify/extensions/git/scripts/powershell/create-new-feature.ps1 -Json -ShortName "<short-name>" "<feature description>" - PowerShell (timestamp):
.specify/extensions/git/scripts/powershell/create-new-feature.ps1 -Json -Timestamp -ShortName "<short-name>" "<feature description>"
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.
- yesterday First seen · 76 lines · 9 tokens per session scan A d70dee326189
speckit.git.feature is an agent published in the GitHub repository snowdreamtech/frp (908 stars, last pushed 5d ago), licensed MIT. It adds 9 tokens to every session and 764 once invoked, about $0.0000 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-09-05.
Other agents, from other repositories
agent-request-queue
一次 Agent 运行可能包含多次模型调用、知识库检索、工具执行和文件操作。为了避免同一对话同时修改同一份上下文，Yuxi 把“收到请求”和“开始运行”分成两个阶段，并为每个线程维护 FIFO 队列。.
env_var_migration.fr
Ce tracker résume les bascules de variables d'environnement liées à la production qui ont fait surface par docs/source/agents/envvarinventory.{json,md} et la migration prévue chemin vers irohaconfig (ou portée explicite de développement/test uniquement).
env_var_migration.pt
Este rastreador resume as alternâncias de variáveis de ambiente voltadas para a produção por docs/source/agents/envvarinventory.{json,md} e a migração pretendida caminho para irohaconfig (ou escopo explícito de desenvolvimento/somente teste).
env_var_migration
This tracker summarizes production-facing environment-variable toggles surfaced by docs/source/agents/envvarinventory.{json,md} and the intended migration path into irohaconfig (or explicit dev/test-only scoping).
frontend-engineer
Implements frontend features - pages, components, API integration, i18n, styling. Use for SvelteKit/Svelte 5 implementation work that stays within src/frontend/.
missing_docs_inventory.fr
Généré par scripts/inventorymissingdocs.py. Ne modifiez pas manuellement ; exécutez le script après avoir touché les caisses pour actualiser l'inventaire.