agentmods.dev

enhance

A command for adding features or changing an existing application during ongoing development.

In plain words
What is it for?
Use it to add or update features such as dark mode, an admin panel, payments, or search in an existing app.
Why use it?
It checks the current project, plans affected files and dependencies, applies the changes, tests them, and updates the preview.

Command

2 5mo ago A scan 13 tokens original MIT
View the source file felipeslo/opencode-kit
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/felipeslo/opencode-kit/enhance
Clone the repo
git clone --depth 1 https://github.com/felipeslo/opencode-kit
Per session 13 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 377 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.00013 $0.00377
Opus 5 $0.00006 $0.00188
Sonnet 5 $0.00003 $0.00075
Haiku 4.5 $0.00001 $0.00038

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

Security

Grade A, and why

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

.opencode/commands/enhance.md · 74 lines

What it actually says

/enhance - Update Application

$ARGUMENTS

Task

This command adds features or makes updates to existing application.

Steps:

  1. Understand Current State

    • Load project state with python .opencode/scripts/session_manager.py info
    • Understand existing features, tech stack

  2. Plan Changes

    • Determine what will be added/changed
    • Detect affected files
    • Check dependencies

  3. Present Plan to User (for major changes)

    "To add admin panel:
- I'll create 15 new files
- Update 8 files
- Takes ~10 minutes

Should I start?"

  4. Apply

    • Call relevant agents
    • Make changes
    • Test

  5. Update Preview

    • Hot reload or restart

  6. Validate Changes (Optional)

    • Ask the user: "Deseja testar as alterações no browser com playwright-cli?"
    • If yes:
      • Use playwright-cli skill to open the app and navigate to the added/changed feature
      • Test the flow affected by the change
      • Check browser console for errors
      • Capture screenshots as evidence
      • Close the browser
    • If no: skip and finalize normally

Usage Examples

/enhance add dark mode
/enhance build admin panel
/enhance integrate payment system
/enhance add search feature
/enhance edit profile page
/enhance make responsive

Caution

  • Get approval for major changes
  • Warn on conflicting requests (e.g., "use Firebase" when project uses PostgreSQL)
  • Commit each change with git
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 · 74 lines · 13 tokens per session scan A f933863460a0

Subscribe to this mod's changes

enhance is a command published in the GitHub repository felipeslo/opencode-kit (2 stars, last pushed 5mo ago), licensed MIT. It adds 13 tokens to every session and 377 once invoked, about $0.0001 per session on Opus 5. 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.

Research
Related

Other commands, from other repositories

checklist

Generate a custom checklist for the current feature based on user requirements.

github/spec-kit · 13 tokens

clarify

Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.

github/spec-kit · 27 tokens

specify

Create or update the feature specification from a natural language feature description.

github/spec-kit · 13 tokens

analyze

Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.

github/spec-kit · 26 tokens

converge

Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.

github/spec-kit · 35 tokens

implement

Execute the implementation plan by processing and executing all tasks defined in tasks.md.

github/spec-kit · 14 tokens