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 agentmods add skills/w693847022/memory_service/do-fixnpx skills add w693847022/memory_service --skill do-fixgit clone --depth 1 https://github.com/w693847022/memory_serviceWrote 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/w693847022/memory_service/do-fix)<a href="https://agentmods.dev/skills/w693847022/memory_service/do-fix"><img src="https://agentmods.dev/badge/skills/w693847022/memory_service/do-fix.svg" alt="Measured on agentmods" 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 | $0.00010 | $0.00773 |
| Opus 5 | $0.00005 | $0.00387 |
| Sonnet 5 | $0.00002 | $0.00155 |
| Haiku 4.5 | $0.00001 | $0.00077 |
Grade A, and why
do-fix 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 4d 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
简短Bug修复技能
⚠️ 重要指令
DO NOT ENTER PLAN MODE - 此技能要求直接执行，不进入计划模式
所有memory_mcp的操作使用子代理来处理，减少主窗口上下文
使用示例
/skill do-fix "fix: 用户登录功能报错500"
流程概览
阶段1(项目确认) → 阶段2(问题澄清) → 阶段3(方案设计) → 阶段4(代码实现)
阶段 1: 项目确认
目标: 确认项目和创建fix记录
流程:
- 解析入参，提取Bug描述（去掉
fix:前缀） - 调用 ./project-confirmation.md 技能创建fix记录
Skill: project-confirmation, args: "<Bug描述>" - 获取
fix_id
输出:
fix_id: 修复IDproject_id: 项目ID
阶段 2: 问题澄清与确认
使用技能: requirement-confirmation
Skill: requirement-confirmation, args: "<fix_id>"
技能会完成:
- 问题澄清（多轮提问）
- 问题确认
- 创建note记录完整问题描述
- 更新development-log
输出:
confirmed_requirements: 确认的问题描述
阶段 3: 方案设计与选择
使用技能: solution-design
Skill: solution-design, args: "<fix_id>"
技能会完成:
- 方案设计（探索代码库并设计方案）
- 用户选择方案
- 方案详细规划
- 创建note记录完整方案
- 更新development-log
输出:
selected_solution: 选择的修复方案
阶段 4: 代码实现与测试
使用技能: code-implementation
Skill: code-implementation, args: "<fix_id>"
技能会完成:
- 代码实现
- 单元测试
- 整合测试
- 修复验证：确认bug确实被修复
- 复现问题（如可复现）
- 执行修复
- 验证修复（确认问题已解决）
- 更新development-log
输出:
implementation_result: 实现结果fix_verified: 修复验证结果
完成展示
fix:
- fix_id
- fix:summary
- fix:content
- fix:severity
- fix:status
note:
- note_id:summary (requirements)
- note_id:summary (implementation-plan)
- note_id:summary (development-log)
验证结果:
- fix_verified: <true|false>
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 4d ago First seen · 134 lines · 10 tokens per session scan A 74d54cfe1a98
do-fix is a skill published in the GitHub repository w693847022/memory_service (1 stars, last pushed 3mo ago), licensed MIT. It adds 10 tokens to every session and 773 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.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…