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/go1c/lumioagent/before-you-codenpx skills add Go1c/LumioAgent --skill before-you-codegit clone --depth 1 https://github.com/Go1c/LumioAgentWrote 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/go1c/lumioagent/before-you-code)<a href="https://agentmods.dev/skills/go1c/lumioagent/before-you-code"><img src="https://agentmods.dev/badge/skills/go1c/lumioagent/before-you-code.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.00056 | $0.00596 |
| Opus 5 | $0.00028 | $0.00298 |
| Sonnet 5 | $0.00011 | $0.00119 |
| Haiku 4.5 | $0.00006 | $0.00060 |
Grade A, and why
before-you-code 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 3d 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
Before You Code（执行前协议）
动手前完成两件事：校准执行深度、加载相关上下文。项目约定与环境约束编码在 knowledge/ 与 skills/ 里，不在模型训练数据中——不读相关规范就动手，等于假设自己的默认行为恰好符合本项目约定。
何时使用
- 拿到任务卡，即将开始实现。
- 修改已有模块，但不确定该模块的规范或约定。
- 「我知道怎么做，直接开干」的冲动出现时——这正是需要先读一遍的信号。
操作步骤
第一步：按任务规模校准深度（快 > 稳 > 好）
| 任务规模 | 特征 | 读取深度 | 执行方式 |
|---|---|---|---|
| 小 | 改动 ≤ 1 个文件，逻辑独立 | 只读直接相关的 knowledge 文档 + 被改源文件 | 直接实现，一次完成 |
| 中 | 涉及 2–5 个文件，有跨模块影响 | 查 knowledge/README.md 导航，读全部相关文档与 Skill |
先列改动清单，再逐项实现 |
| 大 | 多模块、多步骤、有依赖关系 | — | 停下向主 loop 报告，建议用 task-breakdown 重新拆卡 |
低估规模是最常见的失误：涉及多模块就承认是「中」，不要当「小」处理。
第二步：加载上下文
按上表深度读取：相关 knowledge 文档（经 knowledge/README.md 导航定位）、本任务用得上的 Skill 的 SKILL.md、任务涉及的关键源文件（接口定义、被改模块的现有实现）。读完就用，不把读到的内容复述到回复里。
第三步：确认输出位置
改已有文件 → 定位到具体位置，最小化改动；新建文件 → 确认目录与命名约定。改动边界守 AGENTS.md「编码约定·不夹带」。
验证
- 已按任务规模选定读取深度，并读完对应的 knowledge / Skill / 源文件。
- 已确定输出位置与命名约定。
- 规模为「大」时已上报主 loop，没有硬撑。
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.
- 3d ago First seen · 41 lines · 56 tokens per session scan A 58051cfd1c25
before-you-code is a skill published in the GitHub repository Go1c/LumioAgent (20 stars, last pushed 1mo ago), licensed MIT. It adds 56 tokens to every session and 596 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-30.
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…