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.
npx skills add muyen/vibe-to-prod --skill continuous-improvementgit clone --depth 1 https://github.com/muyen/vibe-to-prodWrote 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.
[](https://agentmods.dev/skills/muyen/vibe-to-prod/continuous-improvement)<a href="https://agentmods.dev/skills/muyen/vibe-to-prod/continuous-improvement"><img src="https://agentmods.dev/badge/skills/muyen/vibe-to-prod/continuous-improvement/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.
<a href="https://agentmods.dev/skills/muyen/vibe-to-prod/continuous-improvement"><img src="https://agentmods.dev/badge/skills/muyen/vibe-to-prod/continuous-improvement.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00029 | $0.00509 |
| Opus 5.5 | $0.00012 | $0.00204 |
| Sonnet 5.5 | $0.00006 | $0.00102 |
| Haiku 4.5 | $0.00003 | $0.00051 |
Grade A, and why
continuous-improvement 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 12d 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.
What it actually says
Continuous Improvement
After completing a task, briefly reflect and capture learnings.
When to Activate
- Task just completed
- Same mistake made twice
- User asks "what did I learn" or "retrospective"
- Complex process was difficult or slow
Reflect (30 seconds)
Ask yourself:
- What worked well?
- What was difficult or slow?
- What's missing (automation, docs, tools)?
Capture
| Learning Type | Action |
|---|---|
| Pattern/gotcha | Store in Memory MCP |
| Missing automation | Create issue/TODO |
| Repeated mistake | Update .claude/rules/ |
| Complex process | Create .claude/skills/ |
Memory Pattern
When storing a learning in Memory MCP:
mcp__memory__create_entities({
entities: [{
name: "Learning_TOPIC",
entityType: "development_learning",
observations: [
"Context: What was happening",
"Learning: What was learned",
"Application: How to apply it"
]
}]
})
Improvement Actions
| Issue | Solution |
|---|---|
| Same mistake twice | Add rule to .claude/rules/ |
| Manual process > 5 min | Create skill or hook |
| New tool/pattern | Store in Memory MCP |
| Missing documentation | Update docs |
Rule Addition Example
When you make the same mistake twice:
- Identify the pattern
- Create or update a rule file:
# .claude/rules/my-rules.md
---
paths: relevant/path/**
description: Rules for this area
---
## Critical Rules
| Rule | Why |
|------|-----|
| Don't do X | Because Y happens |
Skill Addition Example
When a process is complex and repeated:
- Create skill directory:
.claude/skills/my-skill/ - Create SKILL.md:
# .claude/skills/my-skill/SKILL.md
---
name: my-skill
description: When this skill should activate
---
# My Skill
## When to Activate
[Trigger conditions]
## Process
[Steps to follow]
Run /improve-claude-config for major configuration updates.
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.
- 12d ago First seen · 105 lines · 29 tokens per session scan A 5706a27c3836
continuous-improvement is a skill published in the GitHub repository muyen/vibe-to-prod (34 stars, last pushed 6mo ago), licensed MIT. It adds 29 tokens to every session and 509 once invoked, about $0.0001 per session on Opus 5.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-10-04.
Other skills, from other repositories
beads
Use when working in a repository that uses bd or Beads for durable project task tracking, issue dependencies, blocker management, multi-session handoff, or shared work memory. Trigger when the user asks to find ready work, claim or close tasks, create follow-up work, inspect blockers, recover project context, or…
mempalace-task
Create, hand off, claim, execute, and close agent tasks through the MemPalace logstream. Use when the user wants to delegate work, prepare a ready-to-paste task for another agent, receive a MemPalace task id, or explicitly launch a supported headless agent in controlled mode.
create-stories
Break one epic into implementable stories embedding TR-ID, ADR guidance, acceptance criteria. Reads the control manifest. After /create-epics.
team-qa
Orchestrate the QA team through a full testing cycle — qa-lead strategy and test plan, qa-tester case writing, execution, sign-off.
release-checklist
Pre-release checklist — build verification, certification requirements, store metadata, launch readiness.
day-one-patch
Day-one launch patch — focused fix for known issues found after gold master. Mini-sprint with QA gate and rollback.