beat

A software-development workflow that uses BDD, or behavior-driven development, with Gherkin feature files written as readable examples of how software should behave.

In plain words
What is it for?
Defining features in Gherkin and following a feature-driven, behavior-focused development process.
Why use it?
It turns expected user-visible behavior into feature files that guide development and testing.

Plugin for Claude Code

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.

Claude Code
/plugin marketplace add kirkchen/beat
agentmods
npx agentmods add plugins/kirkchen/beat/marketplace
Clone the repo
git clone --depth 1 https://github.com/kirkchen/beat

Made for: Claude Code.

Per session not measured What this adds to a session before it is invoked.
When invoked not measured Not applicable: nothing here is loaded into a session.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Security

Grade A, and why

beat 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.

.claude-plugin/marketplace.json · 19 lines

What it actually says

{
  "name": "beat",
  "owner": {
    "name": "Kirk Chen"
  },
  "metadata": {
    "description": "Agent-driven BDD workflow plugin for Claude Code"
  },
  "plugins": [
    {
      "name": "beat",
      "source": "./",
      "description": "Agent-driven BDD workflow using Gherkin feature files",
      "category": "workflow",
      "tags": ["bdd", "gherkin", "tdd", "feature-driven", "behavior-driven"]
    }
  ]
}
Files

What ships with it

1 file beside marketplace.json in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. yesterday First seen · 19 lines scan A ed07d095fd04

Subscribe to this mod's changes

beat is a plugin published in the GitHub repository kirkchen/beat (7 stars, last pushed 2mo ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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-31.