agentmods.dev

Skills-Agent: Skill for Claude Code

.agents/skills/enhance/SKILL.md

enhance is a skill for Claude Code, Codex from VoTruongDanh/Skills-Agent. It costs 61 tokens per session (792 once invoked), scanned A, original, MIT.

A guided process for improving existing software without changing what it is meant to do. It covers refactoring, performance, security, and user-interface improvements.

In plain words
What is it for?
Use it to improve speed, security, usability, backend code, database queries, or maintainability, with routing to the relevant specialist guidance.
Why use it?
It requires the agent to check project notes, identify the specific problem, and preserve expected behavior and tests while making changes.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: installed under .agents/ (shared by several agents).

This is VoTruongDanh/Skills-Agent's own configuration. It tells Claude Code and Codex how to work on Skills-Agent itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything Skills-Agent configures →

not rated 2repo changed 6d ago A scan 61 tokens original MIT
View source ↗ VoTruongDanh/Skills-Agent
Reuse

Borrowing it

Nothing to install: this file belongs to VoTruongDanh/Skills-Agent. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/VoTruongDanh/Skills-Agent/main/.agents/skills/enhance/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/VoTruongDanh/Skills-Agent

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for enhance

README.md
[![agentmods](https://agentmods.dev/badge/skills/votruongdanh/skills-agent/enhance/github.svg)](https://agentmods.dev/skills/votruongdanh/skills-agent/enhance)
Your own site
<a href="https://agentmods.dev/skills/votruongdanh/skills-agent/enhance"><img src="https://agentmods.dev/badge/skills/votruongdanh/skills-agent/enhance/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for enhance

Your own site · 80×15
<a href="https://agentmods.dev/skills/votruongdanh/skills-agent/enhance"><img src="https://agentmods.dev/badge/skills/votruongdanh/skills-agent/enhance.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 61 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 792 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00061 $0.00792
Opus 5 $0.00030 $0.00396
Sonnet 5 $0.00012 $0.00158
Haiku 4.5 $0.00006 $0.00079

Measured 6d ago against content hash 86dbc6ca3337, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, 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 6d 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.

.agents/skills/enhance/SKILL.md · 66 lines

How it starts

The opening of the file, as written. The whole thing — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Memory Protocol

START: Read .ai-memory.md from project root. Check past enhancements, known pain points, tech debt notes, performance baselines, and architecture decisions. END: Update .ai-memory.md using Memory Compaction Rules with: what changed, impact, tradeoffs, and remaining tech debt.

Goal

Improve an existing implementation without breaking working behavior.

Agent Routing

  • If enhancing performance → read .kiro/skills/agents/agents/performance-optimizer.md and apply its knowledge
  • If tightening security → read .kiro/skills/agents/agents/security-auditor.md and apply its knowledge
  • If improving UI/UX → read .kiro/skills/agents/agents/frontend-specialist.md and apply its knowledge
  • If refactoring backend/API → read .kiro/skills/agents/agents/backend-specialist.md and apply its knowledge
  • If improving database queries → read .kiro/skills/agents/agents/database-architect.md and apply its knowledge

Socratic Gate

Before enhancing, verify:

  1. What specific aspect needs improvement? (performance, security, UX, maintainability?)
  2. What is the current pain point or metric?
  3. Are there existing tests that must continue to pass? If any answer is unclear, ASK before proceeding.

Workflow

  1. Read Memory — Load .ai-memory.md for project context and past enhancement history.
  2. Understand the current state and pain points.
  3. Identify high-impact improvements in quality, maintainability, performance, reliability, or UX.
  4. Prioritize improvements by value versus effort.
  5. Implement or recommend the top changes.
  6. Explain tradeoffs and validation steps.
  7. Quality Gate — Read .kiro/skills/_scripts/checklist.md and verify enhancements don't break existing behavior.
  8. Update Memory — Save enhancement details and outcomes to .ai-memory.md.

Checklist

  • Current state documented
  • Pain points identified
  • Improvements prioritized by value/effort
  • Existing behavior preserved
  • Tradeoffs explained
  • Tests still passing
  • Memory file updated

Read the full file on GitHub · 66 lines

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. 6d ago Changed · +3 lines 86dbc6ca3337
  2. 11d ago First seen · 63 lines · 61 tokens per session scan A 338706404812

Subscribe to this mod's changes

enhance is a skill published in the GitHub repository VoTruongDanh/Skills-Agent (2 stars, last pushed 6d ago), licensed MIT. It adds 61 tokens to every session and 792 once invoked, about $0.0003 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.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens