currentfeature

A project command that archives the current feature document, updates release notes, and starts a fresh branch for the next feature.

In plain words
What is it for?
Naming a new branch, finding the latest merged pull request, moving the current feature document, updating release notes, and creating a new current-feature document.
Why use it?
It organizes the handoff between completed and upcoming work without requiring the developer to remember each repository step.

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

agentmods
npx agentmods add commands/mathaix/openclawmachines/currentfeature
Clone the repo
git clone --depth 1 https://github.com/mathaix/OpenClawMachines

Made for: Claude Code.

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 502 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00502
Opus 5 $0.00000 $0.00251
Sonnet 5 $0.00000 $0.00100
Haiku 4.5 $0.00000 $0.00050

Measured 2d ago against content hash b20cca184058, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

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

.claude/commands/currentfeature.md · 65 lines

What it actually says

Archive the current feature and start a new branch.

Instructions

  1. Ask for the new branch name:

    • Ask the user: "What should the new branch be named?"
    • Wait for their response. Store it as BRANCH_NAME.
  2. Switch to main and pull latest:

    git fetch origin && git checkout main && git pull origin main
    
  3. Find the last merged PR:

    gh pr list --state merged --limit 1 --json number,title
    
    • Extract the PR number as PR_NUM and title as PR_TITLE.
    • If no merged PRs found, ask the user for a PR number and title to use.
  4. Archive CurrentFeature.md:

    git mv docs/CurrentFeature.md docs/Feature_<PR_NUM>.md
    
    • If docs/CurrentFeature.md doesn't exist, skip this step and note it.
  5. Update RELEASE.md:

    • If docs/RELEASE.md doesn't exist, create it with this content:
      # Release Notes
      
      ## Features
      
    • Insert a new entry as the first item under ## Features:
      - **PR #<PR_NUM>**: <PR_TITLE> ([Feature_<PR_NUM>.md](Feature_<PR_NUM>.md))
      
    • Keep all existing entries below the new one.
  6. Create fresh CurrentFeature.md:

    • Write docs/CurrentFeature.md with just:
      # Current Feature: <BRANCH_NAME>
      
  7. Create the new branch from main (do NOT commit on main):

    git checkout -b <BRANCH_NAME>
    
  8. Commit the archive on the new branch:

    git add -A && git commit -m "docs: Archive Feature_<PR_NUM> and start <BRANCH_NAME>"
    
  9. Push the branch:

    git push -u origin <BRANCH_NAME>
    
  10. Report to the user:

    • Archived file: docs/Feature_<PR_NUM>.md
    • RELEASE.md entry added
    • New branch: <BRANCH_NAME> (checked out and pushed)
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. 2d ago First seen · 65 lines · 0 tokens per session scan A b20cca184058

Subscribe to this mod's changes

currentfeature is a command published in the GitHub repository mathaix/OpenClawMachines (57 stars, last pushed 1mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 502 tokens. 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-30.