Skip to content

Add tekimax-security to community catalog#2200

Open
kaman1 wants to merge 2 commits intogithub:mainfrom
kaman1:add-tekimax-security
Open

Add tekimax-security to community catalog#2200
kaman1 wants to merge 2 commits intogithub:mainfrom
kaman1:add-tekimax-security

Conversation

@kaman1
Copy link
Copy Markdown

@kaman1 kaman1 commented Apr 13, 2026

Adds tekimax-security (TEKIMAX Secure SDD) to the community catalog.

What it does

tekimax-security is a security-first extension that plugs into Spec Kit's hook system and adds security gates to the SDD lifecycle. It catches AI technical debt at the point where it's cheapest to fix — in the spec, before code exists.

Gate Phase Catches
Data Contract SPECIFY Unvetted sources, unprotected PII, undeclared schemas, hidden bias, drift
Threat Model DESIGN STRIDE coverage, unmitigated high/critical threats
Model Governance DESIGN Unpinned versions, missing rollback plans, no eval baselines
Guardrails SPECIFY/IMPLEMENT Inline prompts, missing input validation, no output redaction
Red Team VERIFY Automated adversarial scenarios executed against staging
Inline Content Scan IMPLEMENT Committed secrets, direct SDK imports outside the gateway layer

It provides 7 commands and 5 hooks wired into after_specify, after_plan, before_implement, after_implement, and before_analyze. It ships an automated red-team runner that parses scenarios and executes them against a staging endpoint with safety guards (refuses prod URLs, rate-limited, injects an X-Red-Team header), then classifies responses and writes a JSONL trace for audit.

The extension is stack-agnostic — it enforces the existence of security controls (AI gateway, guardrails, PII encryption, RBAC, schema validation) without requiring specific vendors.

Why this fills a gap

Spec Kit excels at turning specifications into code. The existing security-review extension in the catalog is a 3-command, 0-hook post-implementation code audit. tekimax-security is different: it's a lifecycle-wide gate system that enforces security controls at every SDD phase transition via hooks, and includes proactive STRIDE threat modeling, model governance gating, and an automated red-team runner.

Verification

  • extension.yml validates against the spec-kit schema
  • Installs cleanly via specify extension add --dev and registers all 7 commands
  • All commands appear in .claude/skills/speckit-tekimax-security-*
  • Gate-check script tested end-to-end (pass + block scenarios)
  • Post-impl audit script tested (catches inline prompts and committed secrets)
  • Red-team runner tested with scenario parsing and safety guards
  • .extensionignore excludes dev-only files
  • Cross-platform POSIX bash — tested on macOS and Linux
  • Apache-2.0 license included
  • SECURITY.md, CONTRIBUTING.md, CODE_OF_CONDUCT.md present

Links

Compatibility

Requires speckit_version >= 0.1.0. Tested against 0.6.2.

Contact

Happy to iterate on formatting, wording, or the catalog entry structure if anything's off. Thanks for shipping the extension API — it's genuinely a great surface to build on.

@kaman1 kaman1 requested a review from mnriem as a code owner April 13, 2026 09:17
@mnriem mnriem requested a review from Copilot April 13, 2026 13:35
@mnriem mnriem self-assigned this Apr 13, 2026
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Adds the TEKIMAX Secure SDD community extension to Spec Kit’s community catalog so it can be discovered/installed via the standard catalog flow.

Changes:

  • Adds a new tekimax-security entry to extensions/catalog.community.json with metadata (version, URLs, tags, hook/command counts).
  • Adds TEKIMAX Secure SDD to the Community Extensions table in the root README.md.
Show a summary per file
File Description
README.md Adds a new row advertising the TEKIMAX Secure SDD extension in the community extensions list.
extensions/catalog.community.json Registers the tekimax-security extension (metadata + compatibility requirements) in the community catalog.

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

Comment on lines +1785 to +1787
"stars": 0,
"created_at": "2026-04-13T07:00:00Z",
"updated_at": "2026-04-13T07:00:00Z"
Copy link

Copilot AI Apr 13, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

extensions/EXTENSION-PUBLISHING-GUIDE.md specifies that when updating extensions/catalog.community.json you must bump the file’s top-level updated_at to the current time (and use a current timestamp for the entry’s created_at/updated_at) (see guide around lines 202-205). The catalog header updated_at is still 2026-04-10T17:00:00Z, which is now older than this newly added entry’s updated_at, so consumers relying on the header won’t see the catalog as freshly updated.

Copilot uses AI. Check for mistakes.
Christian Kaman added 2 commits April 13, 2026 09:00
Adds an entry for TEKIMAX Secure SDD, a security-first extension
that wires threat modeling (STRIDE), data contracts, AI guardrails,
model governance, automated red teaming, and post-implementation
audit into Spec Kit's hook system.

- 7 slash commands across SPECIFY / DESIGN / IMPLEMENT / VERIFY
- 5 phase hooks: after_specify, after_plan, before_implement,
  after_implement, before_analyze
- Apache-2.0 licensed
- Repository: https://github.com/TEKIMAX/speckit-security
Updates the existing catalog entry to reflect the v0.2.2 release:

- version 0.2.0 -> 0.2.2
- download_url repointed at the v0.2.2 archive
- provides.commands 7 -> 8 (new install-rules command)
- description updated to mention the new install-rules capability
  which writes to the spec-kit constitution and agent context files
- updated_at timestamp refreshed
@kaman1 kaman1 force-pushed the add-tekimax-security branch from 5d71cfb to e7646be Compare April 13, 2026 14:06
@kaman1
Copy link
Copy Markdown
Author

kaman1 commented Apr 13, 2026

Refreshed the catalog entry to reflect the v0.2.2 release:

  • version 0.2.0 → 0.2.2
  • download_url repointed at the v0.2.2 archive
  • provides.commands 7 → 8 (new install-rules command that writes the rules into the spec-kit constitution and agent context file so they bind the AI agent at runtime)
  • description updated accordingly

Also rebased onto current main to stay in sync. The PR remains a pure single-entry addition to catalog.community.json with no other changes.

Repo: https://github.com/TEKIMAX/speckit-security
Release: https://github.com/TEKIMAX/speckit-security/releases/tag/v0.2.2

Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Adds the TEKIMAX Secure SDD extension (tekimax-security) to Spec Kit’s community extension listings, making it discoverable via the community catalog and README table.

Changes:

  • Added a new tekimax-security entry to extensions/catalog.community.json with metadata (version, URLs, tags, provides, requirements).
  • Added TEKIMAX Secure SDD to the Community Extensions table in README.md.
Show a summary per file
File Description
README.md Adds TEKIMAX Secure SDD to the community extensions table for discoverability.
extensions/catalog.community.json Registers tekimax-security in the community catalog with install metadata and capabilities.

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

Comment on lines +1783 to +1787
"verified": false,
"downloads": 0,
"stars": 0,
"created_at": "2026-04-13T07:00:00Z",
"updated_at": "2026-04-13T08:30:00Z"
Copy link

Copilot AI Apr 13, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Per the Extension Publishing Guide, new catalog entries should use the current timestamp for both created_at and updated_at, and the catalog’s top-level updated_at should be bumped to the current time when editing the file. This entry uses fixed times and the file’s top-level updated_at (near the top of the JSON) wasn’t updated in this PR.

Copilot uses AI. Check for mistakes.
Comment on lines +1757 to +1761
"description": "Adds security gates to the SDD lifecycle — STRIDE threat modeling, data contracts, AI guardrails, model governance, automated red team, and post-implementation audit. Eight commands wired into five Spec Kit hooks. Rules can be installed into the project constitution and agent context files so they bind the AI agent at runtime.",
"author": "Christian Kaman (TEKIMAX)",
"version": "0.2.2",
"download_url": "https://github.com/TEKIMAX/speckit-security/archive/refs/tags/v0.2.2.zip",
"repository": "https://github.com/TEKIMAX/speckit-security",
Copy link

Copilot AI Apr 13, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The PR description states the extension ships 7 commands and links to release v0.2.0, but the catalog entry says provides.commands: 8 / “Eight commands …” and sets version/download_url to 0.2.2. Please reconcile these so the PR description and catalog metadata consistently reflect the same release and command count.

Copilot uses AI. Check for mistakes.
Copy link
Copy Markdown
Collaborator

@mnriem mnriem left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please address Copilot feedback. If not applicable, please explain why

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants