init-tech-stack

An interactive project setup command that helps choose a technology stack—the languages, frameworks, databases, and tools used to build a project—and writes the result to docs/tech-stack.md.

In plain words
What is it for?
Use it at the start of a web, mobile, backend, desktop, library, SDK, or full-stack project to collect basic project information and define its planned technology stack.
Why use it?
It turns project decisions into a recorded document, so the development setup and chosen technologies are clear to the team.

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/classmethod/tsumiki/init-tech-stack
Clone the repo
git clone --depth 1 https://github.com/classmethod/tsumiki
Per session 31 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 6,611 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.00031 $0.06611
Opus 5 $0.00015 $0.03306
Sonnet 5 $0.00006 $0.01322
Haiku 4.5 $0.00003 $0.00661

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

Security

Grade A, and why

init-tech-stack 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 2d 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.

legacy/commands/init-tech-stack.md · 619 lines

How it starts

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

init-tech-stack

目的

ユーザとのインタラクティブなやりとりを通じて、プロジェクトに最適な技術スタック定義を作成し、docs/tech-stack.md ファイルを生成します。

前提条件

  • プロジェクトルートディレクトリで実行
  • docs/ ディレクトリが存在する(なければ作成)

実行フロー

このコマンドは、AskUserQuestionツールを使用して段階的にヒアリングを行います。

Phase 1: プロジェクト基本情報の収集

まず、以下の3つの質問をAskUserQuestionツールで同時に提示してください:

AskUserQuestion({
  questions: [
    {
      question: "プロジェクトのタイプを教えてください",
      header: "プロジェクト",
      multiSelect: false,
      options: [
        { label: "Webアプリケーション", description: "ブラウザで動作するアプリケーション" },
        { label: "モバイルアプリ", description: "スマートフォン/タブレット向けアプリ" },
        { label: "API/バックエンド", description: "API提供がメインのサービス" },
        { label: "デスクトップアプリ", description: "PC向けネイティブアプリ" },
        { label: "ライブラリ/SDK", description: "他の開発者向けのツール" },
        { label: "フルスタック", description: "フロントエンドとバックエンドの両方" }
      ]
    },
    {
      question: "開発チームの規模を教えてください",
      header: "チーム規模",
      multiSelect: false,
      options: [
        { label: "個人開発", description: "1人で開発" },
        { label: "小規模チーム", description: "2-5人" },
        { label: "中規模チーム", description: "6-15人" },
        { label: "大規模チーム", description: "16人以上" }
      ]
    },
    {
      question: "予定している開発期間はどの程度ですか?",
      header: "開発期間",
      multiSelect: false,
      options: [
        { label: "プロトタイプ/MVP", description: "1-2ヶ月" },
        { label: "短期プロジェクト", description: "3-6ヶ月" },
        { label: "中期プロジェクト", description: "6ヶ月-1年" },
        { label: "長期プロジェクト", description: "1年以上" }
      ]
    }
  ]
})

Phase 2: 技術制約・要件の収集

次に、以下の3つの質問をAskUserQuestionツールで同時に提示してください:

AskUserQuestion({
  questions: [
    {
      question: "既存のシステムやデータベースとの連携はありますか?",
      header: "既存連携",
      multiSelect: false,
      options: [
        { label: "新規構築", description: "全て新しく作成" },
        { label: "既存DB連携", description: "既存データベースを使用" },
        { label: "既存API連携", description: "既存のAPIと連携" },
        { label: "レガシー移行", description: "既存システムからの移行" }
      ]
    },
    {
      question: "想定される負荷や性能要件を教えてください",
      header: "パフォーマンス",
      multiSelect: false,
      options: [
        { label: "軽負荷", description: "同時利用者数10人以下、レスポンス3秒以内" },
        { label: "中負荷", description: "同時利用者数100人程度、レスポンス1秒以内" },
        { label: "高負荷", description: "同時利用者数1000人以上、レスポンス0.5秒以内" },
        { label: "未定/不明", description: "まだ詳細は決まっていない" }
      ]
    },
    {
      question: "セキュリティの重要度を教えてください",
      header: "セキュリティ",
      multiSelect: false,
      options: [
        { label: "基本レベル", description: "一般的なWebセキュリティ対策" },
        { label: "高度", description: "個人情報取り扱い、金融系など" },
        { label: "エンタープライズ", description: "企業向け、コンプライアンス要件あり" },
        { label: "未定/不明", description: "まだ詳細は決まっていない" }
      ]
    }
  ]
})

Read the full file on GitHub · 619 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. 2d ago First seen · 619 lines · 31 tokens per session scan A d45e0dd7875d

Subscribe to this mod's changes

init-tech-stack is a command published in the GitHub repository classmethod/tsumiki (974 stars, last pushed 25d ago), licensed MIT. It adds 31 tokens to every session and 6,611 once invoked, about $0.0002 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.