feat(catalog): add Cost Tracker (cost) community extension

[Quratulain-bilal]

Summary

Adds a new community extension to the catalog: cost — Cost Tracker.

Track real LLM dollar cost across SDD workflows — per-feature budgets, per-integration comparison, and finance-ready exports. Token-analyzer counts tokens; this counts dollars, which is what finance, procurement, and engineering leads actually need to greenlight spec-driven development at scale.

Extension at a glance

• Repo: https://github.com/Quratulain-bilal/spec-kit-cost
• Release: v1.0.0 (tagged)
• License: MIT
• Commands (5): track, report, budget, compare, export
• Hooks: none — purely user-invoked
• Network: none — all data stays under .specify/cost/ locally
• Compatible with: every integration (claude, copilot, gemini, opencode, …)

Why this is useful

• Bundled pricing table covers Claude (Sonnet 4.6, Opus 4.7, Haiku 4.5), GPT-4o, and Gemini 2.5 Pro. Editable in cost-config.yml for negotiated rates.
• Append-only JSONL ledger — diff-friendly, recoverable from a partial last line.
• Budgets are versioned in config, so they are reviewed in PRs alongside other constraints.
• compare re-prices the same workload across all models, so teams can quantify the savings (or cost) of switching integrations before they switch.

Catalog checklist

• JSON valid (python -m json.tool)
• Description under 200 chars
• Required fields populated (name, id, description, author, version, download_url, repository, license, requires, provides, tags, created_at, updated_at)
• HTTPS repository and download URLs
• Tag v1.0.0 exists in the source repo
• updated_at bumped at the top level
• Alphabetical placement (after confluence, before diagram) — note: existing c* entries on main are not strictly alphabetized, so the new entry is placed where the alphabetical position falls within the current order rather than reordering pre-existing entries

Test plan

• Catalog JSON parses
• Tag v1.0.0 resolves and the download URL returns 200
• extension.yml validates against the extension schema
• All five command files render as valid markdown with frontmatter

Thanks for reviewing!

[kennedy-whytech]

Nice. There are some overlapping features between this and https://github.com/coderandhiker/spec-kit-token-analyzer ?

[Copilot]

Pull request overview

Adds the cost community extension to the extension discovery catalog so users can find the new Cost Tracker entry alongside other community-maintained extensions.

Changes:

• Adds a new "cost" entry in extensions/catalog.community.json with metadata, URLs, version, tags, and capability counts.
• Places the new entry in the alphabetized catalog near other co* extensions.
• Removes trailing whitespace from the final existing entry.

Show a summary per file

File	Description
extensions/catalog.community.json	Adds the new community extension catalog entry and a small formatting cleanup.

Copilot's findings

Tip

Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

• Files reviewed: 1/1 changed files
• Comments generated: 2

[mnriem]

Please address Copilot feedback

[Quratulain-bilal]

Both points addressed in 1d2a2f9:

• Added Cost Tracker row to the README community extensions table (between Confluence and DocGuard).
• Bumped top-level updated_at and the entry updated_at to 2026-05-04T00:00:00Z.

Let me know if anything else needs adjusting.

[Copilot]

Copilot's findings

Tip

Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

• Files reviewed: 2/2 changed files
• Comments generated: 2

[mnriem]

Please address Copilot feedback. Note the category addition is fine!

[Quratulain-bilal]

@mnriem! Addressed all four Copilot points in 4d6bd63:

1. Moved the cost entry after confluence so the c* block is alphabetized.
2. Bumped top-level updated_at to 2026-05-05T00:00:00Z per EXTENSION-PUBLISHING-GUIDE.md:204-205.
3. README row uses the documented visibility category (matching Token Consumption Analyzer) instead of
   analytics.
4. Replaced analytics tag with visibility in the catalog tags for consistency.

[Copilot]

Copilot's findings

Tip

Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

• Files reviewed: 2/2 changed files
• Comments generated: 1

[mnriem]

Please address Copilot feedback

[Copilot]

Copilot's findings

• Files reviewed: 2/2 changed files
• Comments generated: 1

[mnriem]

Thank you!