A feature-development workflow for giving each task an isolated Git worktree, which is a separate working copy of a repository. It can run development servers, provide local web addresses, show task status, send changes through review, and merge them into the main branch.

Use it to create task workspaces across one or more repositories, manage local servers and ports, review changes, handle pull-request feedback, and merge completed work.

It keeps unfinished work separated between tasks and organizes the path from a feature branch to a reviewed pull request and merge.

feature — Plugin by fivol

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 fivol/claude-make-better

agentmods

npx agentmods add plugins/fivol/claude-make-better/feature

Clone the repo

git clone --depth 1 https://github.com/fivol/claude-make-better

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

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

plugins/feature/.claude-plugin/plugin.json · 12 lines

What it actually says

{
  "name": "feature",
  "description": "Give every task its own isolated working copy — git worktree per repo, optional unique port, detached dev servers, pretty *.localhost URLs and a live admin dashboard — then ship it through a review gate into a PR and merge it. Four composable skills (workspace, ship, pr-feedback, merge) plus an impartial review gate, all config-driven via .claude/feature/config.json.",
  "version": "1.1.0",
  "author": {
    "name": "fivol",
    "url": "https://github.com/fivol"
  },
  "homepage": "https://github.com/fivol/claude-make-better/tree/main/plugins/feature",
  "license": "MIT"
}

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.

2d ago First seen · 12 lines scan A c8685fccbd3d

Subscribe to this mod's changes

feature is a plugin published in the GitHub repository fivol/claude-make-better (5 stars, last pushed 21d 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.

Analytics and metrics Code review Git and workflow

feature

Getting it into your agent

Grade A, and why

Nothing flagged

What it actually says

What this file has done since we first saw it

Other plugins, from other repositories

humanizer

nextjs

nextjs

claude-plugins-official

knowledge-work-plugins

ecc