Skip to content

Rule Reference

SEC507lintai-ai-securitystablemarkdownwarn

AI markdown: shared gh repo create tool grant

AI-native markdown frontmatter grants `Bash(gh repo create:*)` tool access

Provider
lintai-ai-security
Surface
markdown
Scope
per_file
Tier
stable
Severity
warn
Confidence
high
Detection
structural
Remediation
message_only

Activation Model

Preset Membership

This rule is part of the builtin activation graph through these preset memberships.

Lifecycle

Stable Lifecycle Contract

State

stable_gated

Graduation rationale

Checks AI-native markdown frontmatter for exact GitHub repository creation authority through `allowed-tools`.

Deterministic signal basis

MarkdownSignals exact frontmatter string detection for `Bash(gh repo create:*)` in allowed-tools entries.

Malicious corpus
skill-gh-mutation-allowed-tools
Benign corpus
skill-gh-mutation-specific-safe
structured evidence required remediation reviewed
Canonical note

Structural stable rule intended as a high-precision check with deterministic evidence.

Nearby Signals

Related Rules

SEC507 / MD-GH-REPO-CREATE-ALLOWED-TOOLS

SEC507 flags AI-native markdown frontmatter when allowed-tools grants the exact token Bash(gh repo create:*).

Why It Matters

gh repo create provisions new remote repositories. Shared frontmatter should not quietly make repository creation a default capability for every agent that loads the file.

Trigger Shape

The rule triggers only when all of these are true:

  • the file is an AI-native markdown instruction surface
  • the path is not fixture-like
  • allowed-tools or allowed_tools contains the exact token Bash(gh repo create:*)

Clean Cases

These stay clean:

  • more specific read-only repo commands such as Bash(gh repo view:*)
  • frontmatter without Bash(gh repo create:*)
  • fixture-like examples under test or fixture paths

Example Trigger

yaml
allowed-tools:
  - Bash(gh repo create:*)
  - Read

Safer Example

yaml
allowed-tools:
  - Bash(gh repo view:*)
  - Read

How To Fix

Replace Bash(gh repo create:*) with a narrower reviewed command, or remove shared repository-creation authority from the frontmatter entirely.